There are a number of Local repositories on different machine which are to update a central repository stored on another machine. It seems that the Central repository is not being updated with information from the local repository.
There could be a number of reasons for this problem so please follow the steps outlined below to determine the cause and take appropriate action.
Since there are a number of reasons for this error we need to look at all possibilities to see where the fault lies.
1. Are the Local Repositories being updated?
Confirm to see if the local repositories are being updated by performing a backup on a machine with the local repository and then running a command in Query Analyzer against the Local repository. Run the following command:
Select * from LiteSpeedActivty
From the results check to see if details of the backup just performed are included in the results.
Please note that if there has been a lot of activity the command above may take a long time to return results in which case you should refine it further with perhaps either the database name or date/time period specified in a where clause.
The alternative is to set up the local machine to use the Local repository as the central repository and see if results are updated. Check out solution 18395 on instructions to do this.
If the local repository is being updated then it suggests there is a problem with the update to the Central repository server.
If the Local repository is not being updated it suggests there may be a problem with the configuration of the Local repository such as the user not having access to the Local repository or Activity reporting is disabled.
Run the instance configuration to set up and configure a local repository.
2. Is the LiteSpeed Activity Service Running on the Local Repository machine?
Check the Services on the machine to ensure the LiteSpeed Activity Service is running. If it is please check that the user running this service has access to update the Central repository.
3. Are all machines on the same domain?
If the machines are not on the same domain trusted connections may need to be set up to allow cross domain access for the Litespeed Activity Service to update the Central Repository.
4. Are Registry keys valid?
The LiteSpeed process that updates the Central Repository is ActivityManager.exe. This process uses connection details stored in the registry to connect to the Repositories. Check and ensure these keys exist.
These keys are updated by running the Instance Configuration and setting up the Repositories. If the installer is not updating the registry then it is most likely that the user running the installer does not have sufficient privileges to update the registry information on the Local computer.