Hitachi

JP1 Version 11 JP1/Performance Management - Agent Option for Service Response Description, User's Guide and Reference


13.8.1 PFM - Agent for Service Response service cannot be started

The following subsections describe how to handle the problem when the PFM - Agent for Service Response service cannot be started.

Organization of this subsection

(1) Extensible Service Probe service cannot be started or will be inactive when reloaded (in cases other than IE scenarios)

[Figure]
KAVK08137-E A password has not been set up.

This problem occurs when the password needed for measurement conditions is not specified as defined in the measurement condition registration file (esptask.xml). For details about how to handle this problem, see the description of the message with ID KAVK08137-E in 12.4 Messages.

[Figure]
KAVK08171-E There is no Web transaction.
KAVK08172-E The format of a definition in the Web transaction file is invalid.

This problem is specific to a Web transaction. The Web transaction may not be defined correctly. See the description of the message with each ID in 12.4 Messages to handle the problem indicated by each message.

For the causes other than above, check the contents of the integrated trace log output, and use the ID of the recorded message to see the description in 12.4 Messages.

(2) Extensible Service Probe service cannot be started or will be inactive when reloaded (in IE scenarios)

[Figure]
KAVK10002-E jpcviemd has already started.

This problem occurs when the IE Probe Daemon service is started as a Windows service after it is started as an application. Start the service in either of the methods. For details about how to start the service, see 5.1.2 (2) Starting the IE Probe Daemon service.

[Figure]
KAVK10033-E The content of a definition in the measurement condition registration file is invalid. (ID=measurement-condition-ID,TAG=<INTERVAL>)

If the value of TAG is <INTERVAL>, the same value may be specified for both the measurement interval (INTERVAL) and timeout period (TIMEOUT) in the measurement condition registration file. Review the values in this file, and then start the PFM - Agent for Service Response service again or reload it.

[Figure]
KAVK10040-E An attempt to open the IE scenario file has failed.

This may be due to either of the following reasons:

  • The IE scenario file cannot be accessed.

  • The specification of the IE scenario file in the measurement condition registration file (esptask.xml) is invalid.

For details about how to handle the problem, see the description of the message with ID KAVK10040-E in 12.4 Messages.

[Figure]
KAVF16028-E Processing to reload the IE Probe daemon has failed.

Although no measurement condition for IE scenarios is defined in the measurement condition registration file (esptask.xml), the ie_service_flag setting may be set to Y in the Probe action condition definition file (esp.conf).

If you want to measure IE scenarios, add at least one measurement condition for an IE scenario in the measurement condition registration file. If you do not measure IE scenarios, set ie_service_flag to N. For details about the definitions in the Probe action condition definition file and measurement condition registration file, see 8.2 Probe action condition definition file (esp.conf) and 8.3 Measurement condition registration file (esptask.xml).

For the causes other than above, check the contents of the integrated trace log output, and use the ID of the recorded message to see the description in 12.4 Messages.