7.0 Monitor Agent Problems

A suggested solution is provided for the following problem:

Monitor Agent Won’t Start

Problem: The Monitor Agent does not start.
Possible Cause: The --home switch is missing.
Action: Make sure the --home switch provides the correct path to the domain directory where the domain database (wpdomain.db) resides. See Using Monitor Agent Startup Switches in Monitor in the GroupWise 2012 Administration Guide.
Possible Cause: The server where the domain resides is down.
Action: Check the status of the server where the domain resides.
Possible Cause: The domain database (wpdomain.db) is damaged.
Action: If the domain database (wpdomain.db) is available to the Monitor Agent but cannot be read, it might be damaged. In ConsoleOne, perform maintenance to correct any problems with the domain database. See Maintaining Domain and Post Office Databases in Databases in the GroupWise 2012 Administration Guide.
Possible Cause: The Monitor Agent encounters an error condition.
Action: If you receive an error message when trying to start the Monitor Agent, look it up in Monitor Agent and Application Error Messages in GroupWise 2012 Troubleshooting 1: Error Messages.