KNAN22501-E

An attempt to stop the log file trap failed due to one of the following causes:

• A database access error occurred.

• The log file trap service is not running.

• An attempt to execute the command that stops the log file trap failed.

• An attempt to delete the configuration file on the agent host failed.

• An attempt to update the startup definition file (startup-definition-file-path) failed.

S:

Ceases attempting to stop the log file trap.

O:

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

• IM Configuration Management database-access error

  Execute the jimdbstatus command to check whether the IM database service is running. If the IM database service is not running, start it.

• The log file trap service is not running.

  Check whether the log file trap service is running. If the log file trap service is not running, start it, and then retry the operation.

• Execution of the command to stop the log file trap failed.

  Check whether the command that stops the log file trap can be executed on the agent host.

• Deletion of the configuration file "file-name" on the agent host failed.

  Manually delete the configuration file having the indicated file name on the agent host.

• An attempt to update the startup definition file "startup-definition-file-path" failed.

  Check the following on the agent host, and then retry the operation.

  • Has the format of the startup definition file been set correctly?

  • Has the access permission for the startup definition file been set correctly?

  • Is there sufficient disk space?

• The file does not exist.

  Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

• The directory does not exist.

  Make sure that the log-file trap action definition file and the log-file trap startup definition file exists and that it is accessible.

• Failed to write the configuration file.

  Make sure that you have write permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have write permission for the JP1/Base conf directory on the target host.

• Failed to read the configuration file.

  Make sure that you have read permission for the log-file trap action definition file and the log-file trap startup definition file and that another application has not locked the file. In addition, make sure that a JP1/Base error message or warning message was not output to the integrated trace log on the target host and that you have read permission for the JP1/Base conf directory on the target host.

• There is no access permission.

  Check the settings of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent, confirm that the access from a manager host is admitted.

• The configuration file for rollback failed to be created.

  Make sure that you have access permission for the displayed configuration file and the log-file trap startup definition file and that another application has not locked the file.

  Check the network condition and status with the acquired target.

  Also make sure that JP1/Base is running.

  If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

  • In agent host: JP1/IM-Manager, JP1/Base

  • In manager host: JP1/Base

• Another session has exclusive rights.

  In the Login User List window, determine whether a user has acquired exclusive access permission. If it is not problematic to do so, select the check box next to the user that has acquired exclusive permission, and click the Release Exclusive Editing button to release exclusive permission.

  Make sure that JP1/Base is running on agent host.

  If the problem cannot be resolved by taking the above action, use the data collection tool to collect the following data, and then contact a system administrator.

  • In agent host: JP1/IM-Manager, JP1/Base

  • In manager host: JP1/Base

• A communication error occurred.

  Check the network condition and status with the acquired target.

  Also make sure that JP1/Base is running on the target host.

  If JP1/Base is not running on the target host, take the following actions:

  Start the service or process.

  In the Display/Edit Profiles window, click Operation, and then Rebuild Profile Tree.

If detailed information other than the above is output, use the data collection tool to collect data, and then contact a system administrator.