Error: "Login failed for user 'null'.", without a specific SQL Server login name (4220639)

Errors such as "Login failed for user 'user1'" or Login failed for user 'NTAUTHORITYANONYMOUS LOGON' Or "Login failed for user 'null'.", which don't mention a specific SQL Server login name, usually indicate a problem with Windows Authentication. In such cases you can use SQL Authentication to connect to SQL as a workaround, until you resolve the Windows Authentication issue.

Windows Authentication Permission issues

The MSI does not execute with the same network permissions as the user who invokes the setup. The msi may be using the permissions of the machine ID that the user is on (rather than being the user) and the permissions on Active Directory may be different.

If the connection fails with an error for a SQL Login, for example, "Login failed for user 'sa'. Not associated with a trusted connection," then verify that SQL Server is set up for Windows and SQL Authentication.

Verify that both SQL Servers are running under domain accounts if LiteSpeedLocal and LiteSpeedCentral (repositories) are on different servers. Also, verify that both SQL Server Agents are running with the same domain account that has full privileges on both SQL Servers.

WORKAROUND:
Complete the installation without configuring the LiteSpeedLocal or LiteSpeedCentral (Activity Logging). Once complete, run Instance Configuration. The MSI is called differently than the SLSInstaller.exe (instance configuration). This is a limitation of the msi. SLSInstaller is running as the user, rather than the machine, which is why the permissions were adequate to succeed.