Named Pipes problem

We have just installed SQL server on a Win 2003 server. We are getting the
following error message when we try to use it from the 2003 machine.
A connection was successfully established with the server, but then an error
occurred during the login process. (Provider: Named Pipes. Provider error
0 -
No process is on the other end of the Pipe.)
I am a networking guy and I don't know much about SQL (I just set up the
server) The Database guy is asking me for advice.
Next time you ask a question here, mention wich version of SQL youre using.
Check this article.
http://error.codebetter.com/blogs/sahil.malik/archive/2005/11/05/134318.aspx
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"pogo" wrote:

> We have just installed SQL server on a Win 2003 server. We are getting the
> following error message when we try to use it from the 2003 machine.
> A connection was successfully established with the server, but then an error
> occurred during the login process. (Provider: Named Pipes. Provider error
> 0 -
> No process is on the other end of the Pipe.)
> I am a networking guy and I don't know much about SQL (I just set up the
> server) The Database guy is asking me for advice.
>
>
|||Sorry, Version is 2005 standard. Thanks for the info I'll try it.
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:5460A768-4DF6-4671-BFF2-BE2384F462D9@.microsoft.com...[vbcol=seagreen]
> Next time you ask a question here, mention wich version of SQL youre
> using.
> Check this article.
> http://error.codebetter.com/blogs/sahil.malik/archive/2005/11/05/134318.aspx
>
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "pogo" wrote:
|||Books Online also describes this error in the topic: "Troubleshooting: No
Process is on the Other End of the Pipe"
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"pogo" <xx@.xx.com> wrote in message
news:uT9RyDZYHHA.408@.TK2MSFTNGP04.phx.gbl...
> Sorry, Version is 2005 standard. Thanks for the info I'll try it.
>
> "Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote
> in message news:5460A768-4DF6-4671-BFF2-BE2384F462D9@.microsoft.com...
>
sql

Named Pipes problem

We have just installed SQL server on a Win 2003 server. We are getting the
following error message when we try to use it from the 2003 machine.
A connection was successfully established with the server, but then an error
occurred during the login process. (Provider: Named Pipes. Provider error
0 -
No process is on the other end of the Pipe.)
I am a networking guy and I don't know much about SQL (I just set up the
server) The Database guy is asking me for advice.Next time you ask a question here, mention wich version of SQL youre using.
Check this article.
http://error.codebetter.com/blogs/s.../05/134318.aspx
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL
"pogo" wrote:

> We have just installed SQL server on a Win 2003 server. We are getting the
> following error message when we try to use it from the 2003 machine.
> A connection was successfully established with the server, but then an err
or
> occurred during the login process. (Provider: Named Pipes. Provider error
> 0 -
> No process is on the other end of the Pipe.)
> I am a networking guy and I don't know much about SQL (I just set up the
> server) The Database guy is asking me for advice.
>
>|||Sorry, Version is 2005 standard. Thanks for the info I'll try it.
"Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote in
message news:5460A768-4DF6-4671-BFF2-BE2384F462D9@.microsoft.com...[vbcol=seagreen]
> Next time you ask a question here, mention wich version of SQL youre
> using.
> Check this article.
> [url]http://error.codebetter.com/blogs/sahil.malik/archive/2005/11/05/134318.aspx[/ur
l]
>
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL
>
>
> "pogo" wrote:
>|||Books Online also describes this error in the topic: "Troubleshooting: No
Process is on the Other End of the Pipe"
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"pogo" <xx@.xx.com> wrote in message
news:uT9RyDZYHHA.408@.TK2MSFTNGP04.phx.gbl...
> Sorry, Version is 2005 standard. Thanks for the info I'll try it.
>
> "Hate_orphaned_users" <Hateorphanedusers@.discussions.microsoft.com> wrote
> in message news:5460A768-4DF6-4671-BFF2-BE2384F462D9@.microsoft.com...
>

Mysterious login failure error message in log-shipping

Hi I posted this a few days ago in SQL Server Security forum and at Raul Garcia's suggestion (thanks Raul for your help), I post my question here again to see whether I can be lucky enough to find a super guru to help me out.

I get the following error messages in the sql server error log

Source Logon

Message
Error: 18456, Severity: 14, State: 11.

and

Source Logon

Message
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 185.23.11.33]
(note: 185.23.11.33 is the ip addr of the source server, i.e. node 1 in the two node clustered environment)

The scenario is: We set up log-shipping (LS) between a clustered sql server system (source server) and a stand-alone sql server box (target server). (SQL Server 2K5 EE + SP1 and OS is Win2K3 + SP1), and LS goes very well, but on the target server, we found the above-mentioned error messages. The messages seem in synchronization with Log shipping because we setup log shipping cycle at 10 minutes (from 12:00:00 am to 11:59:00pm), and I can see every 10 minutes, for example at 12:10:00am, the login failure errors occur in the target server's sql server error log, and then not appear until 12:20:00am.

BTW: the two servers are in the same domain.

Thanks in advance for your help ...

Jeff

Very much a case of delegation problem in linked server. Please take a look at Nan Tu's blog for an excellent info.
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx|||

Thanks oj, you are my hero...

I believe it is true as I can find there is a linked server on my source server that points to the target server, where the error message is logged. But just curious why SQL Server automatically set up a linked server for log shipping.

|||Logshipping is functional through linked server. It's by design.

If you use built-in logshipping, the wizard will create the linked server for you. If you set up log shipping by hand (when you run on Standard edition), you will have to setup the linked server yourself.

Mysterious login failure error message in log-shipping

Hi I posted this a few days ago in SQL Server Security forum and at Raul Garcia's suggestion (thanks Raul for your help), I post my question here again to see whether I can be lucky enough to find a super guru to help me out.

I get the following error messages in the sql server error log

Source Logon

Message
Error: 18456, Severity: 14, State: 11.

and

Source Logon

Message
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 185.23.11.33]
(note: 185.23.11.33 is the ip addr of the source server, i.e. node 1 in the two node clustered environment)

The scenario is: We set up log-shipping (LS) between a clustered sql server system (source server) and a stand-alone sql server box (target server). (SQL Server 2K5 EE + SP1 and OS is Win2K3 + SP1), and LS goes very well, but on the target server, we found the above-mentioned error messages. The messages seem in synchronization with Log shipping because we setup log shipping cycle at 10 minutes (from 12:00:00 am to 11:59:00pm), and I can see every 10 minutes, for example at 12:10:00am, the login failure errors occur in the target server's sql server error log, and then not appear until 12:20:00am.

BTW: the two servers are in the same domain.

Thanks in advance for your help ...

Jeff

Very much a case of delegation problem in linked server. Please take a look at Nan Tu's blog for an excellent info.
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx|||

Thanks oj, you are my hero...

I believe it is true as I can find there is a linked server on my source server that points to the target server, where the error message is logged. But just curious why SQL Server automatically set up a linked server for log shipping.

|||Logshipping is functional through linked server. It's by design.

If you use built-in logshipping, the wizard will create the linked server for you. If you set up log shipping by hand (when you run on Standard edition), you will have to setup the linked server yourself.

Mysterious login error message

I get the following error messages in the sql server error log

Source Logon

Message
Error: 18456, Severity: 14, State: 11.

and

Source Logon

Message
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 185.23.11.33]

The scenario is: We set up log-shipping (LS) between a clustered sql server system (source server) and a stand-alone sql server box (target server). (SQL Server 2K5 EE + SP1), and LS goes very well, but on the target server, we found the above-mentioned error messages.
BTW: the two servers are in the same domain.

Did I miss something in configuration?

Thanks in advance for your help..

Jeff

It looks like a delegation problem. Most likely the credentials from a 3rd machine (most likely the client) are used to connect to the source SQL Server are being used to connect to the target SQL Server. If this is the case, the following articles will hopefully help you to fix it:

Security Account Delegation http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp

Specifying Credential and Connection Information http://msdn2.microsoft.com/en-us/library/ms160330.aspx

Let us know if this information helped.

-Raul Garcia

SDE/T

SQL Server Engine

|||

Hi Raul,

I do not think we have a 3rd machine/application to connect to the source server / or the target server. Actually, we setup both source server and target server (in our log-shipping scenario) to use the same domain account as SQL Server service and sql server agent service startup account.

For the 1st reference link you mentioned, i.e. Security Account Delegation http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_2gmm.asp our environment is Win 2K3 EE + SP1 (64 bit) and SQL Server 2K5 EE + SP1 (64bit), so it seems unapplicable here.

Personally I believe it is has something to do with the log-shipping, because we setup log shipping cycle at 10 minutes (from 12:00:00 am to 11:59:00pm), and I can see every 10 minutes, for example at 12:10:00am, the login failure errors occur in the target server's sql server error log, and then not appear until 12:20:00am.

Do you have some other thoughts regarding this?

Thanks a lot for your help, which is greatly appreciated...

BTW, in the error message

Message
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. [CLIENT: 185.23.11.33]
Here [CLIENT: 185.23.11.33] is the ip address of our source server (node 1 in two clustered server environment)

|||

Unfortunately I cannot think of any other reason why you would get this particular error message; hopefully somebody else may have a better answer. Another option could be to post your question on the SQL Server Database Engine forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1), hopefully there we may find somebody with more knowledge on log-shipping who may be able to answer your question.

-Raul Garcia

SDE/T

SQL Server Engine

|||With the help from MVP oj, I finally figured it out. The error appeared because a linked server (on the source) was created by the Log-shipping wizard ( but I still do not understand why Log-shipping needs a linked server), and after configured the linked server by giving a remote user with password, the error disappears.

Mysterious Error Message

I keep getting Timeout Expired with {call sp_MSget_repl_commands(8, ?, 0,
7500000)} in the error detail when attempting to replicate a 9.2gb database
over a wan link. The replication is transactional and other smaller test
databases replicate just fine. Any clue as to what this means?
Chris,
you could
(a) set the LoginTimeout to 0 and QueryTimeout to 0 which will mean that the
agent will not timeout
or
(b) compress the snapshot files (WINRAR or latest winzip), transfer the
file, uncompress it, then use the alternative snapshot location.
or
(c) transfer a backup and then do a noinit initialization.
Rgds,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

MySql

I am setting up a message board on my home windows 2000 server with IIS. I installed PHP and got that to work and now i need to set up a mysql database. How do i go about doing that, i installed the mysql software but im stuck from there.Hello,

after installation you can access every object in the MySQL. Normally the server starts automatically. If you want to create a database or access your datas (create table and so on) use AlligatorSQL at http://www.alligatorsql.com/download/alligator.zip

AlligatorSQL supports also MSSQL7 and SQL2000 databases.

Hope that helps otherwise describe your problem with more details.

Regards

Manfred Peter
(Alligator Company GmbH)
http://www.alligatorsql.com

MY SQL server can not connect with my PC

HI

I have a peoblem when I make connect the SQL server with my PC

and this message apper

{

cannot connect to PC.......\SQLEXPRESS

Additional information:

An error has occurred while establishing a connection to the serves . When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connection.( provider: SQL Network Interface , error:26 - Error locating

Server/ Instance Specified) ( Microsoft SQL Server )

}

can you help me pleas .....

You need to explicitly enable remote connections for SQL Express since they are off by default. You can enable them during install using the DISABLENETWORKPROTOCOLS flag:

(From template.ini)

;--
; The DISABLENETWORKPROTOCOLS switch is used to disable network protocol for SQL Server instance.
; Set DISABLENETWORKPROTOCOLS = 0; for Shared Memory= On, Named Pipe= On, TCP= On
; Set DISABLENETWORKPROTOCOLS = 1; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= Off
; Set DISABLENETWORKPROTOCOLS = 2; for Shared Memory= On, Named Pipe= Off (Local Only), TCP= On

; Note: DISABLENETWORKPROTOCOLS if not specified has the following defaults.
; Default value for SQL Server Express/Evaluation/Developer: DISABLENETWORKPROTOCOLS =1
; Default value for Enterprise/Standard /Workgroup: DISABLENETWORKPROTOCOLS =2

or after install using TSQL or following this blog:

http://support.microsoft.com/kb/914277

Thanks,
Sam Lester (MSFT)

|||

I have been struggling with this for about a week now. For some reason today when I searched I found this thread relatively quickly, and this reply held the solution.

For me, it was the single line of text "Turn on the SQL Server Browser Service." that solved the problem.

SQL Server Browser Service was not running on my server. I had to use the SQL Server Surface Area Configuration Tool to enable and start the SQL Server Browser Service. As soon as that worked, I had no problems.

Thanks.

Jim Sparks

my SQL cant open window when installation

Is there anyone can help me to run window when after done with installation, i wana open but i got message" this installation package could not be opened. verify that the package exists and that you can access it. or contact the application vedor to verify that this is a valid Windows Installer package"
My comp is running w/ Win home XP.
thanks

I have installed the Eval Enterprise edition in XP home but I think you can only install personal edition in XP home, so I would check the edition you are installing. Hope this helps.