SQL2000 error: ... When connecting to SQL Server 2005

  • Thread starter Thread starter prefersgolfing
  • Start date Start date
P

prefersgolfing

The complete error is :
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)

Our db is SQL 2000 running on a Win 2003 cluster, where there is only one
instance loaded.
The client app is a Windows Service written in VS2005 that runs on a Windows
2000 server.

We booted the cluster last night, now we're getting the above error in the
service. Anybody else ran into this?

Is the name of the default instance on a cluster MyServer\MSSQLSERVER ?

Thanks
 
I use SQL 2005, and have never needed to quote the default instance name. So
I would try a connection string to "server" not "server\instance" unless you
have specifically asked during setup for SQL Server to create a named
instance.

The error you are getting is a very generic one, and it can mean many, many
things regarding the failure of the conenction. If you look about 10 posts
down from this one, you'll see someone has made a link to the following site
which seams good:

http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html

Also, I like the following site:

http://support.microsoft.com/Default.aspx?id=328306

Which is intended for SQL 2000, but lots of the problems it lists is
applicable to SQL 2005 also.

I'd first look at the instance problem, then my favourite trick is to go to
DOS, and try:

TELNET servername 1433

If it can connect, then you have an open IP connection to the SQL Server,
and your code is more than likely at fault, if you can't connect, check your
SQL Server Network Settings - sometimes some of the settings are turned off,
i.e. TCP/IP!

James.
 
I had a similar problem and discovered that the firewall on my sqlserver 2000
system
was not allowing connections on port 1433. Once I opened up port 1433 (I
also changed the scope so that only systems on the same subnet were allowed
access) everything worked fine.
 
Back
Top