Microsoft SQL Native Client error '80004005' Named Pipes Provider: Could not open a connection to SQL Server [5]. "
Experts,
I am getting this error in an asp application. I am trying to set up a staging environment for this application and the app works in production. When I change the connection string to thit he production database the error disappears. However, I get this error when the application is pointed to the staging database. Named Pipes, TCP/IP and have been enabled. We will really appreciate your help. BTW, our database is a 2005 db.
the error I am getting on the page is,
Microsoft SQL Native Client error '80004005'
Named Pipes Provider: Could not open a connection to SQL Server [5].
I am getting this error in an asp application. I am trying to set up a staging environment for this application and the app works in production. When I change the connection string to thit he production database the error disappears. However, I get this error when the application is pointed to the staging database. Named Pipes, TCP/IP and have been enabled. We will really appreciate your help. BTW, our database is a 2005 db.
the error I am getting on the page is,
Microsoft SQL Native Client error '80004005'
Named Pipes Provider: Could not open a connection to SQL Server [5].
ASKER
What do you mean by including the port number and Also, Different versions of what? We have the same versions of SQL Server and SQl is listening on the same ports on both systems.
post your connection string please (make sure to take out the username/password/server values)
ASKER
Sorry about that, the connection string is below
dim objConn
Set objConn = Server.CreateObject("ADODB
objConn.ConnectionString = "provider=SQLNCLI;server=S
objConn.Open
dim objConn
Set objConn = Server.CreateObject("ADODB
objConn.ConnectionString = "provider=SQLNCLI;server=S
objConn.Open
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
See the following for some troubleshooting.
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
I'd double check that named pipes is really enabled on your development sql server (since it's disabled by default).
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
I'd double check that named pipes is really enabled on your development sql server (since it's disabled by default).
also make sure you are using the correct server. You may need to include a port number with it, but double check to make sure...