Source: ZENworks Server Management; Management and Monitoring Services; Atlas Manager
Possible Cause: Atlas Manager is not running at the site server.
Action: Check if Atlas Manager is running:
Check the log files generated in the following directory: Installvolume: \installdirectory\zenworks\mm\logfiles\sloader.
Select the sloader-bignumber.txt file that contains the latest modified time stamp.
Search for the following string:
AtlasManager:CmdServerObjThread.java :com.novell.managewise.AtlasCmdServerObj[XXXXX] is ready.
(XXXXX will be replaced by some detailed information in the file.)
If this string does not exist, you might need to wait for about 4-5 minutes for the services to start. If they do not start automatically, you need to restart them.
Possible Cause: The ZENworks Server Management server processes were stopped and restarted when ConsoleOne® was running.
Action: Perform the following tasks:
In ConsoleOne, select ZENworks Server Management Site.
Click Refresh.
If the error message persists, close the ConsoleOne session that is currently running. Launch ConsoleOne again.
Possible Cause: The ConsoleOne snap-in and the site server have different ZENworks Server Management versions.
Action: Perform the following tasks:
Ensure that the ConsoleOne snap-in and the site server are using the same ZENworks Server Management version. The ZENworks for Servers 3.x snap-ins do not work with the ZENworks 6.5 Server Management site server, and vice versa.
Install the latest ZENworks Server Management version of the snap-ins on the console and the latest version of the site server on the server and restart the processes.