Error: Unable to use selected instance. LitespeedLocal not configured when setting up Log Shipping. The same root cause may also prevent LiteSpeedLocal
Inadequate permissions on the registry keys.
To troubleshoot, run this query to determine if the login for the SQL Server Service can access the registry entry for the LiteSpeed repositories.
The login for the SQL Server Service must have Full Permission on the keys (and all child keys):
HKEY_CURRENT_USER\Software\Imceda
HKEY_LOCAL_MACHINE\SOFTWARE\Imceda
Right click on the HKEY_LOCAL_MACHINE\SOFTWARE\Imceda, verify the SQL Server login appears (add if necessary), is defined as an Admin user. Then, in permissions check pushing them onto the Child Objects, Click apply.
The LiteSpeed Console will need to be closed and reopened to run with the new permissions.
ADDITIONAL INFORMATION:
If the issue is on a cluster, you'll might want to follow the same registry steps for replacing permissions on the other node(s) as well. Otherwise, if the instance fails over it could potentially have issues again if the permissions on the other nodes were setup the same way.
-- With Native SQL Server xp, this will check with the permissions for the user who is running the query in SSMS
declare@statsDatabasesysname
EXECUTEmaster.dbo.xp_instance_regread N'HKEY_LOCAL_MACHINE',N'SOFTWARE\Imceda\SQLLiteSpeed\Engine\ActivityServers\[server_name],
N'StatsDatabase',@statsDatabaseoutput
Select@statsDatabase
/* or you can run the following to see if LiteSpeed (who runs as SQL Server Service login) can access the value in the RegKey
-- With LiteSpeed xp
declare @statsDatabase sysname
EXECUTE master.dbo.xp_sls_regread N'HKEY_LOCAL_MACHINE', N'SOFTWARE\Imceda\SQLLiteSpeed\Engine\ActivityServers\[server_name]',
N'StatsDatabase', @statsDatabase output
Select @statsDatabase
