Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: An error has occurred while establishing a connection to the server. 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 connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: An error has occurred while establishing a connection to the server. 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 connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider, error: 40 - Could not open a connection To SQL Server

I am trying to setup a notification service sample (from Joel Webb's book) for SQL server 2000 and notification service 2.0.

When i run nscontrol create at the cmd prompt, i am getting the following error:

Notification Services failed to retrieve the SQL Server edition.

SqlServerError:
Source: .Net SqlClient Data Provider
Number: 53
State: 0
Class: 20
Server:
Message: An error has occurred while establishing a connection to the server. 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 connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL
Server)
Procedure:
Line Number: 0

Any help on how this could be resolved would be really appreciated.

Thanks,

Nirmala

Hi Nirmala -

Thanks for buying the book. I hope you find it useful!

As for your issues, you may want to double check the name of the server and SQL Server instance to make sure they are correct. You may also want to verify that the server does indeed allow remote connections and that it is using named pipes as a communication protocol.

HTH...

Joe|||

I tried all the suggested things but unfortunately still seeing the same errors. Any more thoughts?

Thanks,

Nirmala

|||In the description of the problem you mention SQL Server 2000 and SSNS v2.0. However, in the actual error message it references SSNS 2005.

SSNS v2.0 was developed using version 1.1 of the .net framework and will only work with SQL Server 2000. SSNS 2005 was developed with v2.0 of the .net framework and is only available for use with SQL Server 2005.

Could it be that you have mismatched versions? And that is what is causing the problems you are seeing?

HTH...

Joe|||

Hi

I had a similar error in analysis project.

In my case I did not use the real servername as I had put an alias name for the server in my hosts file.

When I changed the server name in my datasource to reflect the real server name in stead of the alias name, I was able to deploy the project.

Regards

Per

Named Pipes Provider, error: 40 - Could not open a connection

Ok,
I've spent a bunch of hours trying to figure out how to connect to SQL
Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
I can run ASP.net code with no problem. I can access SQL Server from the
command line using osql with no problem.
But trying to access sql server 2005 from asp.net yields the following
message:
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could
not open a connection to SQL Server)
Can someone help me with this? I have both tcp/ip and named pipes enabled.
--
ThanksCan you post your connection string?
specifying
Network=DBMSSOCN
in your connection string will cause it to use tcp instead of named pipes,
which is less error prone.
See here for more details:
http://www.aspfaq.com/show.asp?id=2126
Also, check out the post regarding connections to sql express.
http://www.aspfaq.com/sql2005/show.asp?id=3
HTH
--
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> Ok,
> I've spent a bunch of hours trying to figure out how to connect to SQL
> Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> I can run ASP.net code with no problem. I can access SQL Server from the
> command line using osql with no problem.
> But trying to access sql server 2005 from asp.net yields the following
> message:
> System.Data.SqlClient.SqlException: An error has occurred while establishing
> a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could
> not open a connection to SQL Server)
> Can someone help me with this? I have both tcp/ip and named pipes enabled.
> --
> Thanks|||The connections string is:
Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
Catalog=sqlexpress;Integrated Security=SSPI");
The new error message I get is:
(provider: TCP Provider, error: 0 - No connection could be made because the
target machine actively refused it.)
The detail is as follows:
System.Data.SqlClient.SqlException: An error has occurred while establishing
a connection to the server. 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 connections. (provider: TCP Provider, error: 0 - No connection
could be made because the target machine actively refused it.)
It appears that the connection is blocked but I'm not sure where. I've
checked Windows Firewall and made sure that the appropriate ports are open...
--
Thanks
"Ryan Powers" wrote:
> Can you post your connection string?
> specifying
> Network=DBMSSOCN
> in your connection string will cause it to use tcp instead of named pipes,
> which is less error prone.
> See here for more details:
> http://www.aspfaq.com/show.asp?id=2126
> Also, check out the post regarding connections to sql express.
> http://www.aspfaq.com/sql2005/show.asp?id=3
> HTH
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > Ok,
> >
> > I've spent a bunch of hours trying to figure out how to connect to SQL
> > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > I can run ASP.net code with no problem. I can access SQL Server from the
> > command line using osql with no problem.
> >
> > But trying to access sql server 2005 from asp.net yields the following
> > message:
> >
> > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could
> > not open a connection to SQL Server)
> >
> > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> >
> > --
> > Thanks|||Check out this link.
http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
This is a post that explains exactly how to enable remote connections for
express.
Ryan Powers
Clarity Consulting
http://www.claritycon.com
"Greg" wrote:
> The connections string is:
> Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> Catalog=sqlexpress;Integrated Security=SSPI");
> The new error message I get is:
> (provider: TCP Provider, error: 0 - No connection could be made because the
> target machine actively refused it.)
> The detail is as follows:
> System.Data.SqlClient.SqlException: An error has occurred while establishing
> a connection to the server. 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 connections. (provider: TCP Provider, error: 0 - No connection
> could be made because the target machine actively refused it.)
> It appears that the connection is blocked but I'm not sure where. I've
> checked Windows Firewall and made sure that the appropriate ports are open...
> --
> Thanks
>
> "Ryan Powers" wrote:
> > Can you post your connection string?
> >
> > specifying
> > Network=DBMSSOCN
> > in your connection string will cause it to use tcp instead of named pipes,
> > which is less error prone.
> >
> > See here for more details:
> > http://www.aspfaq.com/show.asp?id=2126
> >
> > Also, check out the post regarding connections to sql express.
> > http://www.aspfaq.com/sql2005/show.asp?id=3
> >
> > HTH
> >
> > --
> > Ryan Powers
> > Clarity Consulting
> > http://www.claritycon.com
> >
> >
> > "Greg" wrote:
> >
> > > Ok,
> > >
> > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > command line using osql with no problem.
> > >
> > > But trying to access sql server 2005 from asp.net yields the following
> > > message:
> > >
> > > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > > a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could
> > > not open a connection to SQL Server)
> > >
> > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > >
> > > --
> > > Thanks|||Excellent! I had to change from dynamic to static TCP port number. It works
great now.
Thanks for all your help
Greg
"Ryan Powers" wrote:
> Check out this link.
> http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx
> This is a post that explains exactly how to enable remote connections for
> express.
>
> --
> Ryan Powers
> Clarity Consulting
> http://www.claritycon.com
>
> "Greg" wrote:
> > The connections string is:
> > Cn = new SqlConnection("Network=DBMSSOCN;Data Source=192.168.1.103;Initial
> > Catalog=sqlexpress;Integrated Security=SSPI");
> >
> > The new error message I get is:
> > (provider: TCP Provider, error: 0 - No connection could be made because the
> > target machine actively refused it.)
> >
> > The detail is as follows:
> > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > a connection to the server. 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 connections. (provider: TCP Provider, error: 0 - No connection
> > could be made because the target machine actively refused it.)
> >
> > It appears that the connection is blocked but I'm not sure where. I've
> > checked Windows Firewall and made sure that the appropriate ports are open...
> >
> > --
> > Thanks
> >
> >
> > "Ryan Powers" wrote:
> >
> > > Can you post your connection string?
> > >
> > > specifying
> > > Network=DBMSSOCN
> > > in your connection string will cause it to use tcp instead of named pipes,
> > > which is less error prone.
> > >
> > > See here for more details:
> > > http://www.aspfaq.com/show.asp?id=2126
> > >
> > > Also, check out the post regarding connections to sql express.
> > > http://www.aspfaq.com/sql2005/show.asp?id=3
> > >
> > > HTH
> > >
> > > --
> > > Ryan Powers
> > > Clarity Consulting
> > > http://www.claritycon.com
> > >
> > >
> > > "Greg" wrote:
> > >
> > > > Ok,
> > > >
> > > > I've spent a bunch of hours trying to figure out how to connect to SQL
> > > > Server 2005. I have MSDE 2005, IIS 6.0 and ASP.NET configured on my laptop.
> > > > I can run ASP.net code with no problem. I can access SQL Server from the
> > > > command line using osql with no problem.
> > > >
> > > > But trying to access sql server 2005 from asp.net yields the following
> > > > message:
> > > >
> > > > System.Data.SqlClient.SqlException: An error has occurred while establishing
> > > > a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could
> > > > not open a connection to SQL Server)
> > > >
> > > > Can someone help me with this? I have both tcp/ip and named pipes enabled.
> > > >
> > > > --
> > > > Thanks

Named Pipes Provider, error: 40 - Could not connect; Error 2

I have installed MSSQL 2005 successfuly, checked the services their are running I can connect to the

server with Intergrations Services ok. I get the following when I try to connect to the Database Engine

(provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

What file is SQL looking for (net helpmsg 2)?

Thanks for the help

Did you enable remote conenctions ? Check my website for the screencast which explains how to enable the Remote connections on your instance.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Would this be true for a standalone PC? I don't have SQL Server installed on a remote server.|||

For a standalone PC, you want to disable remote connections for TCP/IP and Named Pipes but you probably want to enable them locally (especially considering that you are trying to use named pipes here). So you should start SQL Server Configuration Manager, then go to "Protocols" then enable both TCP/IP and Named Pipes. To make sure that remote computers cannot connect to your machine -- go to SQL Server Surface Area Configuration -> Surface Area Configuration for Services and Connections ->Remote Connections and turn off remote connections.

That should do it,

John

Named Pipes Provider, error: 40 - Could not connect; Error 2

I have installed MSSQL 2005 successfuly, checked the services their are running I can connect to the

server with Intergrations Services ok. I get the following when I try to connect to the Database Engine

(provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

What file is SQL looking for (net helpmsg 2)?

Thanks for the help

Did you enable remote conenctions ? Check my website for the screencast which explains how to enable the Remote connections on your instance.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Would this be true for a standalone PC? I don't have SQL Server installed on a remote server.|||

For a standalone PC, you want to disable remote connections for TCP/IP and Named Pipes but you probably want to enable them locally (especially considering that you are trying to use named pipes here). So you should start SQL Server Configuration Manager, then go to "Protocols" then enable both TCP/IP and Named Pipes. To make sure that remote computers cannot connect to your machine -- go to SQL Server Surface Area Configuration -> Surface Area Configuration for Services and Connections ->Remote Connections and turn off remote connections.

That should do it,

John

Named Pipes Provider, error: 40 - AAAAAAAAAAAAAAARGH!

Hi,

I have been getting this error for about 6 hours now. I have read every article from google about it and absolutely none of the solutions work for me.

I am running Windows XP Home Edition

I downloaded and installed Visual Studio Web Developer Express about a week ago.

I downloaded SQL Server Express 2005 yesterday.

It installed fine.

I got my first error trying to add New Item->Sql Server Database only to find out the default instance SQLExpress was not working and i was running a different instance.

Anyway, I am trying to connect to sql server with the below code:

 SqlConnection myConnection =new SqlConnection("server=mycomp/mssqlserver;database=mydb;Trusted_Connection=yes"); SqlCommand myCommand =new SqlCommand("select category, title, article from articles where id=15");// + article + ");", myConnection); myConnection.Open();

Which give me the below error:

An error has occurred while establishing a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. 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 connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:

Line 30: SqlCommand myCommand = new SqlCommand("select category, title, article from articles where id=15");// + article + ");", myConnection);Line 31:Line 32: myConnection.Open();Line 33: Line 34:

I have followed all the instructions online like enabling 445 firewall stuff, making sure i accept local and remote connection, enabling TCP/IP Named pipes and heaps of protocols ect but nothing works.

I am about to uninstall sql server and .net and call it quits.

This stupid server is too hard to configure.

If anyone could help me get it running it would be gretly appreciated however, this question seems to be asked all over the net and i have read gazzilions of threads with all kinds of answers but nothing works.

Thanks

Did you try to re-install SQL? and install it as default instance?

|||

Ok, I got your problem. You have to do some more configuration
Go to SQL Server - SQL Server Configuration Manager.
Check the protocols Named Pipes and TCP/IP should be enabled
then go to Client Protocols, and check Named Pipes and TCP/IP should be enabled

Please check it, I hope it works.
Let me know in case of any difficulties.

|||

Thanks guys.

As you can see in my first post i have tried all the common solutions like configuring the client protocols ect.

I think i will just reinstall and see how it goes.

Cheers

|||

Let us know how it turns out

Named Pipes Provider, error 40 Could not open a connection to SQL

Hi,
I have a big problem, I have a website in a Windows 2003 and SQL Server
2005, and the website usually goes weel, but some times and error appears,
the error is "Named Pipes Provider, error: 40 - Could not open a connection
to SQL Server".
There is not installed a firewall and TCP and Pipes connection are enabled.
Any ideas?
Thanks in advance,
Miguel
I have seen this before in SQL Servers that have been configured to support
N connections and no more. In this case, the named pipe is opened (the
Connection) but the server finds that the connection limit has been reached
so it closes the pipe at the server end. This confuses the connection pooler
who responds that the named pipe has failed and the connection could not be
opened after all.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"JMLA" <JMLA@.discussions.microsoft.com> wrote in message
news:FFF29A16-3C52-4596-AC88-F18D41E31309@.microsoft.com...
> Hi,
> I have a big problem, I have a website in a Windows 2003 and SQL Server
> 2005, and the website usually goes weel, but some times and error appears,
> the error is "Named Pipes Provider, error: 40 - Could not open a
> connection
> to SQL Server".
> There is not installed a firewall and TCP and Pipes connection are
> enabled.
> Any ideas?
> Thanks in advance,
> Miguel
|||Hi William Vaughn,
I have upgraded the MaxUserPort in the registry to 40000, and nothing
happens, any ideas?
Thanks in advance,
Miguel.
"William (Bill) Vaughn" wrote:

> I have seen this before in SQL Servers that have been configured to support
> N connections and no more. In this case, the named pipe is opened (the
> Connection) but the server finds that the connection limit has been reached
> so it closes the pipe at the server end. This confuses the connection pooler
> who responds that the named pipe has failed and the connection could not be
> opened after all.
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "JMLA" <JMLA@.discussions.microsoft.com> wrote in message
> news:FFF29A16-3C52-4596-AC88-F18D41E31309@.microsoft.com...
>
>
|||It's not ports, it's "Connections". It might be a license restriction as
well...
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"JMLA" <JMLA@.discussions.microsoft.com> wrote in message
news:CB4C9FE7-A3F2-4720-B163-0DF2784C952E@.microsoft.com...[vbcol=seagreen]
> Hi William Vaughn,
> I have upgraded the MaxUserPort in the registry to 40000, and nothing
> happens, any ideas?
> Thanks in advance,
> Miguel.
> "William (Bill) Vaughn" wrote:
sql

Named Pipes Provider, error 40 Could not open a connection to SQL

Hi,
I have a big problem, I have a website in a Windows 2003 and SQL Server
2005, and the website usually goes weel, but some times and error appears,
the error is "Named Pipes Provider, error: 40 - Could not open a connection
to SQL Server".
There is not installed a firewall and TCP and Pipes connection are enabled.
Any ideas?
Thanks in advance,
MiguelI have seen this before in SQL Servers that have been configured to support
N connections and no more. In this case, the named pipe is opened (the
Connection) but the server finds that the connection limit has been reached
so it closes the pipe at the server end. This confuses the connection pooler
who responds that the named pipe has failed and the connection could not be
opened after all.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"JMLA" <JMLA@.discussions.microsoft.com> wrote in message
news:FFF29A16-3C52-4596-AC88-F18D41E31309@.microsoft.com...
> Hi,
> I have a big problem, I have a website in a Windows 2003 and SQL Server
> 2005, and the website usually goes weel, but some times and error appears,
> the error is "Named Pipes Provider, error: 40 - Could not open a
> connection
> to SQL Server".
> There is not installed a firewall and TCP and Pipes connection are
> enabled.
> Any ideas?
> Thanks in advance,
> Miguel

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...
>

Named Pipers Provider, error 40, ok from local, error to remote - help

Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald|||Do you have to connect with named pipes? If not, change the connection string
to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
connectivity components are properly installed on the web server and you can
ping the database server from the web server, I'd try a few things.
1. Find out the IP address and the TCP port that the SQL instance listens on.
2. Change the connection string to the IP address followed by a comma and
then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
you may have a problem with accessing the port. (if it's the default instance
using the default port, you don't need to test with the port number specified
explicitly).
3. Change the IP to the server name in the Server property of the connection
string, and try again. If this doesn't work, you may have a problem with
resolving the server to the IP address. Try the fully qualified domain name
instead.
If you can connect with TCP/IP, but not with names pipes, you may have a
problem with the ports used by the named pipes being blocked.
Linchi
"Ranginald" wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald
>|||How would I find out the TCP port that the SQL instance listens on?
Thanks
Linchi Shea wrote:
> Do you have to connect with named pipes? If not, change the connection string
> to connect with TCP/IP (set Network Library=dbmssocn). Assuming that the SQL
> connectivity components are properly installed on the web server and you can
> ping the database server from the web server, I'd try a few things.
> 1. Find out the IP address and the TCP port that the SQL instance listens on.
> 2. Change the connection string to the IP address followed by a comma and
> then the TCP port (e.g. set Server=169.12.35.51,5002). If this does not work,
> you may have a problem with accessing the port. (if it's the default instance
> using the default port, you don't need to test with the port number specified
> explicitly).
> 3. Change the IP to the server name in the Server property of the connection
> string, and try again. If this doesn't work, you may have a problem with
> resolving the server to the IP address. Try the fully qualified domain name
> instead.
> If you can connect with TCP/IP, but not with names pipes, you may have a
> problem with the ports used by the named pipes being blocked.
> Linchi
> "Ranginald" wrote:
> > Hi.
> >
> > I am new to sql server so please bear with me.
> > Here is the problem.
> >
> > I am using VWD express to connect to a sql server 2005 db on my local
> > machine. The site and the sql server are local and everything is fine.
> > No problems.
> >
> > I have a sql server hosting plan to host the db. (my local is SQL
> > Server 2005 and the hosted is Sql Server 2000).
> >
> > I use the LOCAL VWD website to access the HOSTED sql server and it
> > connects with no problem. I changed data in the remote version of the
> > db as a double-check that I am accessing the remote db and not the
> > local db.
> >
> > When I go ahead and upload the web site to my web host, different from
> > the sql host (long story), I get this error (provider: Named Pipes
> > Provider, error: 40 - Could not open a connection to SQL Server).
> >
> > Any ideas why this error is happening. My web host verifies that my
> > connection string is fine, and that if I can connect with my local
> > machine then there should be no problem and the problems is on the
> > hosting end.
> >
> > Thanks in advance,
> > Ranginald
> >
> >sql

Named Pipers Provider, error 40, ok from local, error to remote - help

Hi.
I am new to sql server so please bear with me.
Here is the problem.
I am using VWD express to connect to a sql server 2005 db on my local
machine. The site and the sql server are local and everything is fine.
No problems.
I have a sql server hosting plan to host the db. (my local is SQL
Server 2005 and the hosted is Sql Server 2000).
I use the LOCAL VWD website to access the HOSTED sql server and it
connects with no problem. I changed data in the remote version of the
db as a double-check that I am accessing the remote db and not the
local db.
When I go ahead and upload the web site to my web host, different from
the sql host (long story), I get this error (provider: Named Pipes
Provider, error: 40 - Could not open a connection to SQL Server).
Any ideas why this error is happening. My web host verifies that my
connection string is fine, and that if I can connect with my local
machine then there should be no problem and the problems is on the
hosting end.
Thanks in advance,
RanginaldOk. Problem solved. I was using a web host with multiple hosted
domains and I think I probably had some kind of IIS app directrory
problem. I moved the site to its own hosting and all was fine with no
changes needed.
Thanks anyway. Hope this tidbit helps someone.
Rangy
Ranginald wrote:
> Hi.
> I am new to sql server so please bear with me.
> Here is the problem.
> I am using VWD express to connect to a sql server 2005 db on my local
> machine. The site and the sql server are local and everything is fine.
> No problems.
> I have a sql server hosting plan to host the db. (my local is SQL
> Server 2005 and the hosted is Sql Server 2000).
> I use the LOCAL VWD website to access the HOSTED sql server and it
> connects with no problem. I changed data in the remote version of the
> db as a double-check that I am accessing the remote db and not the
> local db.
> When I go ahead and upload the web site to my web host, different from
> the sql host (long story), I get this error (provider: Named Pipes
> Provider, error: 40 - Could not open a connection to SQL Server).
> Any ideas why this error is happening. My web host verifies that my
> connection string is fine, and that if I can connect with my local
> machine then there should be no problem and the problems is on the
> hosting end.
> Thanks in advance,
> Ranginald

Named Pipe Provider/Linked Server Connection Error

Hello, everyone!

I'm currently having an issue with a linked server. Here's the surrounding information:

A) I have a clustered SQL Server 2005 Instance (A) and a SQL Server 2000 instance (B).

B) There is a linked server on A to B. When I set it up, I did run the fix to ensure A could talk to B (There was an issue with communication between 2005 and 2000 servers). It has been there since I installed A, and has worked fine.. Until last week.

C) This linked server uses static credentials to connect to B.

D) Named Pipes are enabled on both servers to listen to both connections on both A and B in cliconfg. So A has a named pipe listening for B, and B has a named pipe listening for A.

E) A has a view that looks at a table on B - It's a table view, very simple, just pulls in all the data from the table on B.

So, I go to do a select statement from the view, connected as a user other then 'sa'. I then get the error:

Named Pipes Provider: Could not open a connection to SQL Server Linked Server

Error Source: ncli Client (Paraphrasing, didn't copy that down, but it was the ODBC connector)

Well, that's odd. It's been working fine for months now..

I then go and connect as sa on A to query B. It works! Mind you, absolutely NO QUERY from A to B will run again until I run SOME kind of query has been run as sa on A.

Mind you, this is not a credential issue. Every user who connects to the linked server to B uses a stored credential that is DBO to the database on B. The same User Name and Password exists on both A and B.

Also of note, I check the activity monitor. There's a process that is "dormant" every time I run a query against the view. The details of this connection are:

sp_reset_connection;1

My question is, why is it resetting the connection on B when being queried from A? Why is it "all of a sudden" a problem? Are there any changes that coudl ahve been made that would cause this?

Any help with this confusing issue would be appreciated.

Thanks!

No one has any idea?

|||we found this to help us out: data source = servername,1433 (the port used), we noticed that when using an alias as the Linked Servername (not the actual servername) it failed, yet if the servername was the LS name it worked, so we added ',1433' to the data source and it cleared up our problem.

Named Pipe Provider/Linked Server Connection Error

Hello, everyone!

I'm currently having an issue with a linked server. Here's the surrounding information:

A) I have a clustered SQL Server 2005 Instance (A) and a SQL Server 2000 instance (B).

B) There is a linked server on A to B. When I set it up, I did run the fix to ensure A could talk to B (There was an issue with communication between 2005 and 2000 servers). It has been there since I installed A, and has worked fine.. Until last week.

C) This linked server uses static credentials to connect to B.

D) Named Pipes are enabled on both servers to listen to both connections on both A and B in cliconfg. So A has a named pipe listening for B, and B has a named pipe listening for A.

E) A has a view that looks at a table on B - It's a table view, very simple, just pulls in all the data from the table on B.

So, I go to do a select statement from the view, connected as a user other then 'sa'. I then get the error:

Named Pipes Provider: Could not open a connection to SQL Server Linked Server

Error Source: ncli Client (Paraphrasing, didn't copy that down, but it was the ODBC connector)

Well, that's odd. It's been working fine for months now..

I then go and connect as sa on A to query B. It works! Mind you, absolutely NO QUERY from A to B will run again until I run SOME kind of query has been run as sa on A.

Mind you, this is not a credential issue. Every user who connects to the linked server to B uses a stored credential that is DBO to the database on B. The same User Name and Password exists on both A and B.

Also of note, I check the activity monitor. There's a process that is "dormant" every time I run a query against the view. The details of this connection are:

sp_reset_connection;1

My question is, why is it resetting the connection on B when being queried from A? Why is it "all of a sudden" a problem? Are there any changes that coudl ahve been made that would cause this?

Any help with this confusing issue would be appreciated.

Thanks!

No one has any idea?

Named pipe error 53

I get the following error when I try to connect from an XP SP2 client to SQL
MSDE:
An error has occurred while establishing a connection to the server. 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 connections.
(provider: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
Before last week, al worked fine, but suddenly I get this message.
What goes wrong?Is the service on another machine ? Can you reach the computer via ping ?
Did you try disabling the firewall on the Windows XP machine to see if it is
dedicted to the settings of the firewall ?
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Johan" <Johan@.discussions.microsoft.com> wrote in message
news:68D2C2C3-B0B1-4756-BBBD-B6A6D2577EDA@.microsoft.com...
>I get the following error when I try to connect from an XP SP2 client to
>SQL
> MSDE:
> An error has occurred while establishing a connection to the server. 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 connections.
> (provider: Named Pipes Provider, error: 40 - Could not open a connection
> to
> SQL Server) (Microsoft SQL Server, Error: 53)
> Before last week, al worked fine, but suddenly I get this message.
> What goes wrong?sql

Name cannot begin with the '>' character, hexadecimal value 0x3E

Hi,

This is my first attempt at SSRS, I've added code section to the xml file. But when I use <> for not equal to, it is giving me this error. What should I do? The code is as posted here.

Thanks,

Debi

***************************************************************************************

<Code>
Dim PrevId as Object
Dim a_Count As Double
Dim b_Count As Double
Dim c_Count As Double
Dim d_Count As Double
Dim e_Count As Double
Dim Total As Double = 0
Function SumMPCount(ByVal CurrID As Object,ByVal code As Object, ByVal NewCount As Object) As Double

If(CurrID is Nothing or code is Nothing or NewCount is Nothing)Then
Exit Function
End if
If PrevId Is Nothing Then
PrevId = CurrId
End if
If CurrID <> PrevID Then
a_Count = 0
b_Count = 0
c_Count = 0
d_Count = 0
e_Count = 0
Total = 0
End if
Select Case mp_Code
Case "a"
a_Count = a_Count + NewCount
SumMPCount = a_Count
case "b"
b_Count = b_Count + NewCount
SumMPCount = b_Count
case "c"
c_Count = c_Count + NewCount
SumMPCount = c_Count
case "d"
d_Count = d_Count + NewCount
SumMPCount = d_Count
case "e"
Total = a_Count + b_Count + c_Count + d_Count + e_Count
SumMPCount = Total
case else
e_Count = e_Count + NewCount
SumMPCount = e_Count
End Select

PrevId = CurrId
End Function
</Code>

It looks like you directly copy&pasted the code snippet into the RDL(XML) file and therefore the <> is not encoded an is interpreted as invalid xml element.

You have two options - either copy&paste the code snippet into the report designer custom code window (and report designer will automatically encode the characters correctly), or replace the <> in the RDL file with &lt;&gt; (which is the encoded representation).

-- Robert

|||

Thanks for the reply. Where is the custom code window? When I right click on the report and select properties, it just shows me the usual Properties tab on the RHS which shows background color, image, etc..

I actually worked around it using Object variables and using "Is" instead of <> .

|||I think he might have meant
right click on the report.rdl -> Prooperties -> Code tab -> paste theresql

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.