LiteSpeed scheduled jobs fail when the SQL Browser service is not running. Error displays: Msg 60901, Level 16, State 1, Line 2883584: Failed to login to SQL Server
Here are the steps that Litespeed is doing to generate the cluster instance names.
1. Litespeed request from the domain controller a list of registered SQL servers.
2. Litespeed display this list of server names
3. Litespeed then does a DNS look up for the ip address of all servers on the list returned from the domain controller in step 1.
4. Litespeed then queries each SQL server's browser service for a list of instance names and port numbers.
5. Litespeed updates the list with the SQL instance names.
The reply back from the SQL browser service contains a field that indicates if the instance is clustered.
A network trace may be used to determine if there is missing info from the domain controllers.
By configuring an alias, you can bypass the discovery phase that SQL Browser service goes through for each connection, since an alias has a pre-defined protocol and the port your server is listening on,therefore speeding up the connection.