KNAN26163-E

An error occurred during startup of a remote-monitoring event log trap.

S:

Stops the remote-monitoring event log trap.

O:

If the following detailed information is displayed, take the indicated corrective action.

• The operation definition file is invalid.

  The action definition file contains an invalid specification. Check the contents of the action definition file.

  If you want to use the parameters listed below in the action definition file for a remote-monitoring event log trap, upgrade JP1/Base and JP1/IM - Manager to version 11-10 or later. If you do not want to use these parameters, delete them.

  • open-retry-times

  • open-retry-interval

• Authentication failed.

  Check the following items:

  • Are the user name, password, and domain name specified correctly in the System Common Settings or Remote Monitoring Settings window?

  • Is DCOM configured correctly on the monitored host?

  • Is DCOM configured correctly on the JP1/IM - Manager host?

  If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

• An attempt to connect monitored host failed.

• The collection of log files did time-out.

  If this message appears at startup of a remote event-log trap, check the following items, and then restart the remote event-log trap.

  • Is communication with the monitored host possible?

  • Has the password for the user who logs in to the monitored host expired?

  • Has the remote communication type for the monitored host name been set correctly?

  • Is the WMI service running?

  If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

  If the above methods cannot resolve the problem or if a timeout occurred during collection of log files, check the following items:

  • Check the load on the system.

  • Make sure that the host is running.

  • Check whether the number of connections exceeded the maximum.

  • Make sure that the IM host account has been specified correctly in the system common settings.

• Creation of the jcfallogtrap process failed.

  Check the IM host account specified in the system common settings.

• The specified command option is invalid.

  An incorrect startup option is specified. Check the startup option.

  • Is the maximum number of monitored log files exceeded?

  • Can the option and its value be specified with additional options?

• The event service is not running.

  Make sure that the event service is running. If the event service has stopped, start it, and then restart the remote log-file trap or remote event-log trap.

• The log file trap service is not running.

  Check the following items:

  • Make sure that the log file trap service is running. If the log file trap service has stopped, start it, and then restart the remote-monitoring log file trap or remote-monitoring event log trap.

  • Check the integrated trace log to see if the JP1/Base KAVA3663-E or KAVA3917-E message was output. If the message was output, take the corrective action given for that message.

• JP1/Base command execution error

  Check the JP1/Base environment.

  Check whether the JP1/Base LogTrap service or daemon has stopped or restarted. If the JP1/Base LogTrap service or daemon has stopped, start it and then start or restart all the remote monitoring profiles. If the JP1/Base LogTrap service or daemon has restarted, stop all the remote monitoring profiles, and then start or restart them.

• Communication with JP1/Base failed.

  If possible, restart JP1/Base.

• An attempt to connect to the JP1 Event service failed.

  If possible, restart the event service.

• The JP1/Base command arguments are invalid.

  Check the startup option.

• The maximum number of collection processes has been reached.

  The number of collection processes has reached the maximum. Stop unnecessary log file traps, and then restart.

• An attempt to connect monitored host failed.

  Check the following items, and then restore the remote log-file trap or remote event-log trap.

  • Is DCOM configured correctly on the monitored host?

  • Is DCOM configured correctly on the JP1/IM - Manager host?

  If no error is found by checking the above items, make sure that the WMI connection has been configured correctly.

• The remote event-log trap has already been started.

  Check whether the remote-monitoring event log trap is already running on the monitored host.

In any other case, use the data collection tool to collect data, and then contact a system administrator.