skorpiodude
asked on
SQLServer Mgt Studio cannot connect to server with named-pipes and tcp/ip
SQLServer Mgt Studio 2008 cannot connect to SQLExpress 2008 R2 using TCP/IP and Named-Pipes but it is able to connect using Shared Memory protocol. Apparently, something is blocking TCP/IP and Named-Pipes between the Mgt Studio and the SQLServer which I need help in figuring out how to remove the block.
The SQLServer startup log shows it is listening to TCP/IP and named pipes. Portion of the log is as follows:
2013-02-14 10:36:56.41 Server Server is listening on [ 'any' <ipv6> 1433].
2013-02-14 10:36:56.41 Server Server is listening on [ 'any' <ipv4> 1433].
2013-02-14 10:36:56.41 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRE
2013-02-14 10:36:56.41 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\
2013-02-14 10:36:56.41 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2013-02-14 10:36:56.41 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2013-02-14 10:36:56.41 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-02-14 10:36:56.45 spid10s Starting up database 'tempdb'.
This is the error message that the SQLServer Management Studio gets when it fails connecting using TCP/IP or Named-Pipes:
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
As I mentioned above, the SQLServer Management Studio connects successfully to the SQLServer when I specify in its option to use the "Shared Memory" network protocol.
Please help.
The SQLServer startup log shows it is listening to TCP/IP and named pipes. Portion of the log is as follows:
2013-02-14 10:36:56.41 Server Server is listening on [ 'any' <ipv6> 1433].
2013-02-14 10:36:56.41 Server Server is listening on [ 'any' <ipv4> 1433].
2013-02-14 10:36:56.41 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRE
2013-02-14 10:36:56.41 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\
2013-02-14 10:36:56.41 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2013-02-14 10:36:56.41 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2013-02-14 10:36:56.41 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2013-02-14 10:36:56.45 spid10s Starting up database 'tempdb'.
This is the error message that the SQLServer Management Studio gets when it fails connecting using TCP/IP or Named-Pipes:
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
As I mentioned above, the SQLServer Management Studio connects successfully to the SQLServer when I specify in its option to use the "Shared Memory" network protocol.
Please help.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Thanks for the reply. Everything checks out as per the your advice and the guidelines from "angel eyes" but still does not work. I finally decided to uninstall and install the SQLServer and then everything works fine.
Roy