How to troubleshoot a local repository that is not updating to a central repository?
Does the litespeedlocal..litespeedactivity table contain current records regarding the LiteSpeed backups?
If so, at the command prompt, navigate to %Program FilesImcedaLiteSpeedSQL ServerEngine and run the following command:
activitymanager.exe -logging
The resulting log will be in Litespeed's default log directory, The location of the log is determined by the path in the HKEY_LOCAL_MACHINE\SOFTWARE\Imceda\SQLLiteSpeed\Engine\ErrorLogPath -- The default is: C:\Documents and Settings\All Users\Application Data\Quest Software\LiteSpeed. The log will be named similar to: 'ActivityManager.exe - 13-Jun-2011 09-42-01-643.txt'.
This log file determines if the account that is running the LiteSpeed Activity Service has the appropriate permissions. The user account owning the LiteSpeed Activity Service must have permission to insert, update, and delete from MSDB and the local/central repository databases (typically named LiteSpeedLocal and LiteSpeedCentral).
During Instance Configuration, LiteSpeed assigns the “service logon” right to the user account the statistics replication service (Litespeed Activity Service).
Verify that there are not conflicting entries pointing to two different Central Repositories in theHKEY_LOCAL_MACHINE\SOFTWARE\Imceda\SQLLiteSpeed\Engine\ActivityServers registry keys. See attached file 'Two Central Repositories' for example.
For information on Cluster troubleshooting, see Solution 17927
To reset connections, from Enterprise Console | Connections, delete the existing Central Repository. Rerun Instance Configuration, selecting "Configure local and central repositories" Verify that the service account can login to the Central Repository database using Windows Authentication. Check the 'Collect Statistics' checkbox for both LiteSpeedLocal and LiteSpeedCentral.
In LiteSpeed Enterprise Console | Connections create New, select the server and instance when LiteSpeedCentral is located (the Instance Name and Display Name must be the same), select Statistics Database (typically LiteSpeedCentral) and click 'OK'. Verify that 'Collect Statistics' checkbox is selected and choose the repository to use next time LiteSpeed is started. The servername must be highlighted and click 'OK'.
