6.3 Health Reports Error Messages

Unable to locate the Health Report service on the server. Check if the Health Report service is running on the server

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports
Severity: Critical
Possible Cause: The Health Report service is not running on the site server.
Action: Do the following:

  1. Select Tools > Management Site Server Status.

  2. Check the status of the health submodule of the Service Manager.

  3. Start the Health Report service, if it is stopped.

A communication error has occurred at the server. Failed to complete the attempted operation

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports
Severity: Informational
Possible Cause: The communication between the Health Report client and the Health Report server was lost because the Health Report service running on the site server was down during the operation.
Action: Do the following:

  1. Select Tools > Management Site Server Status.

  2. Check the status of the health sub-module of the Service Manager.

  3. Start the Health Report service if it is stopped.

Possible Cause: The healthreportslib.jar file version on the site server and on the machine where you have installed ConsoleOne is not the same version because the TID's .jar file is updated on the site server or on the machine where you have installed ConsoleOne.
Action: Check if the healthreportslib.jar file is identical on the site server and the machine where you installed ConsoleOne. If not, update the older version with the new version. The healthreportslib.jar file is in the following location:

  • Site Server: volume:\zenworks\mms\lib\mw

  • Machine where ConsoleOne is installed: ConsoleOne\1.2\lib\mw

Possible Cause: Communication between the Health Report client and the Health Report server was lost because the network connection between the machine where you installed ConsoleOne and the site server was lost.
Action: Check the network connectivity. Reconnect if necessary.

The Health Profiles are missing. Try restarting the site server

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports
Severity: Critical
Possible Cause: The site server was not installed correctly. The Health profiles are created during installation.
Action: In ConsoleOne, check the SNMP settings from the properties of the site. If most of the values are -1, then problems exists in the installation. Do either of the following:

  • Reinstall the site server.

  • Enter the following SQL calls on the database from any of the database interaction tools:

    • call MW_DBA.initializeDB(0);
    • call Globalc$SNMPCommunicationParameters(p$Timeout=250,p$Retries=2,p$IP_Port=161,p$IPX_Port=36879,p$read_authentication=0,p$write_authentication=0,p$ReadCommunity='public',p$WriteCommunity='public');
    • call Health.c$addHealthProfileTypes(‘sys:\zenworks\mms\mwserver\bin');
    • commit;

The Health Report is not available for viewing. Try the following: Generate Health Report before viewing. Check the publish directory configuration for profiles

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports
Severity: Informational
Possible Cause: The Health Reports are not generated at a specific location.
Action: Define a new Health Report in ConsoleOne and run it immediately using the Now option.
Action: Launch index.html from where you have published the report.

The agent is not responding - please check if agent and connection is operational

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports
Severity: Informational.
Possible Cause: The SNMP service might be down.
Action: Start the SNMP service.
Possible Cause: Insufficient timeout value.
Action: Increase the timeout value.
Possible Cause: The node might be down.
Action: Start the node.

The agent might not be instrumented for Health Reports - please check installation of agent

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports.
Severity: Informational.
Possible Cause: The SNMP agent might not be running on the machine.
Action: Install the relevant agents, such as nwtrned and nttrend.

The SNMP properties are not complete and cannot get the trend values

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports.
Severity: Informational.
Possible Cause: Incorrect SNMP Read community string.
Action: Specify the correct SNMP Read community string.

The agent is not trending required attributes for health data computation

Source: ZENworks Server Management; Management and Monitoring Services; Health Reports.
Severity: Informational.
Possible Cause: The attributes required for health calculation are not being trended.
Action: Trending must be enabled on all the attributes, that are used for health calculation.