The folllowing error may display during installation, running LiteSpeed backup or running xp_sqllitespeed_version
"An error occured when attempting to detect if LiteSpeed was installed on<nameof></nameof>The error message is: Failed to login to SQL server"
There could be an alias or host file entry on the host or client machine that is set incorrectly and pointing to the wrong server or IP address, which in turn can lead to a connectivity failure. This error may display when using Named Pipes.
1. Determine if SQL Server is listening on Named Pipes, TCP/IP, or any other protocol by opening the current SQL Server Error Log. Verify lines similar to the following:
"2007 02 14 09:49:36.17 server SQL server listening on TCP, Shared Memory, Named Pipes.
2007 02 14 09:49:36.17 server SQL server listening on 192.168.1.5:1433, 127.0.0.1:1433."
Verify that SQL Server is listening on the correct IP address.
2. Verify SQL Server's protocol settings and are communicating on same port in SQL Server Network Utility and SQL Server in the SQL Client Network Utility (the client to the host and vice versa).
2. Create a new alias in the SQL Server in the SQL Client Network Utility to test connectivity, using the server name, the IP address, or even using a different protocol. Then try connecting using that alias.
3. In case of named instances, SQL Server dynamically determines the listening port. It may attempt to listen on the port it used previously. If it cannot bind to that port, the named instance may bind to a different port. Verify that the clients are set to dynamically determine the port. Or, specify a static port for that instance to bind on, using the Client Network Utility.
For additional information, see:http://www.sqljunkies.com/HowTo/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
