ADDITIONAL INFORMATION:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
Previous post i was given a solution about SQL Server 2008 R2 Setup Error - is not a valid login or you do not have permission , Error : 40 – could not open a connection to SQL server.
I have a SQL 2000 instance, and a SQL 2008 R2 instance, running on Windows Server 2008 R2. The sql 2000 instance is functioning correctly, as is the management studio. I can connect to other SQL 2008 servers, just not my local one.
Named pipes and TCPIP are both enabled. The SQL Browser service is running, as is the SQL Server service.
Solution For this
The SQL Server 2000 instance is the default instance and the SQL Server 2008 instance is a named instance, right?
Please check if the SQL Server 2008 service is running and you specify the correct instance name when connecting to it.
Please see:
1) Error: 53
winerr 53 means "The network path was not found". If you got this message, it means the client stack cannot find the target machine. Here are possible reasons for this failure,
a) typo in the server name, or using "/" rather than "\" between server name and instance name, e.g. "myserver/myinst" is not correct.
b) name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case
c) The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
Copied from:
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/16/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error-xxx.aspx
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
Previous post i was given a solution about SQL Server 2008 R2 Setup Error - is not a valid login or you do not have permission , Error : 40 – could not open a connection to SQL server.
I have a SQL 2000 instance, and a SQL 2008 R2 instance, running on Windows Server 2008 R2. The sql 2000 instance is functioning correctly, as is the management studio. I can connect to other SQL 2008 servers, just not my local one.
Named pipes and TCPIP are both enabled. The SQL Browser service is running, as is the SQL Server service.
Solution For this
The SQL Server 2000 instance is the default instance and the SQL Server 2008 instance is a named instance, right?
Please check if the SQL Server 2008 service is running and you specify the correct instance name when connecting to it.
Please see:
1) Error: 53
winerr 53 means "The network path was not found". If you got this message, it means the client stack cannot find the target machine. Here are possible reasons for this failure,
a) typo in the server name, or using "/" rather than "\" between server name and instance name, e.g. "myserver/myinst" is not correct.
b) name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case
c) The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
Copied from:
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/16/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error-xxx.aspx
Comments
Post a Comment