Unable to obtain Naming Server Instance
Source:
ZENworks Server Management; Management and Monitoring Services; SLOADER or NetExplorer
Severity:
Critical
Possible Cause:
The service loader was started while the Naming Server was not running.
Action:
Start the Naming Server.
To start the Naming Server, enter mmsnaming at the Management server prompt. You need not restart the service loader because it will locate the Naming Server after a short interval.
Service Manager is already running
Source:
ZENworks Server Management; Management and Monitoring Services; SLOADER or NetExplorer
Explanation:
Management and Monitoring Services does not allow you to run multiple instances of the same Service Manager.
Possible Cause:
You might be trying to run the service manager even if an instance of the service manager is not actually running. This happens when the earlier instance of service manager is closed using java ‑kill instead of stopservice.
Action:
Restart the Naming Server by closing the Naming Server and starting the Naming Server again.
To restart the Naming Server, enter mmsNaming.
mw.log is an invalid transaction log
Source:
ZENworks Server Management; Management and Monitoring Services; SLOADER or NetExplorer
Severity:
Critical
Explanation:
You might see this error message while starting a Sybase server.
Possible Cause:
Creating an index on a function and then inserting, updating, or deleting data in the table where index was created causes an invalid transaction log entry. This invalid entry does not allow Sybase to start.
Action:
Do the following:
-
Make sure that mgmtdbs.ncf file contains the -F option.
-
Start the Sybase with the -F option.