-
Title
Error: "Failed to login to SQL Server" due to Namepipes protocol changing from TCP/IP -
Description
Error: "Failed to login to SQL Server" when accessing Quest Enterprise Console. However, all other test connectivity, sql server native, and ping results are all fine.
-
Cause
To connect to SQL Server Database Engine you must have a network protocol enabled.
Click Start | All programs | Microsoft SQL server | Client network utility | select Alias tab | Named Pipes
a. Change from NAMEPIPE to TCP/IP.
b. After user ran exec xp_sqllitespeed_version | the TCP\IP is no longer in place, and the protocol reverts to NAMEPIPE.
c. Run the xp_sqllitespeed_version command again, error message displays that the user failed to login to SQL Server.
-
Resolution
Reinstall TCP\IP protocol and update Server Connection Properties to TCP/IP, save settings.
-
Additional Information
For further information in changing protocols, see : http://msdn.microsoft.com/en-us/library/ms345306.aspx