KNAN22426-E

Acquisition of the contents of the configuration file failed because a connection could not be established with the managed host.

S:

Stops acquisition of the contents of the configuration file.

O:

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

• There is no access permission.

  The agent configuration on the manager might be different from the agent configuration enabled in the system, or might have been deleted.

  In the IM Configuration Management window, click Operation, and then Verify IM Configuration to make sure that the agent configuration matches the agent configuration enabled in the system. If the agent configurations do not match, in the Edit Agent Configuration window, click Operation and then Apply Agent Configuration to use batch distribution to make the agent configurations match. Also, check the setting of the host access control definition file (jbsdfts_srv.conf) in JP1/Base on the agent.

• Failed to read the configuration file.

  Make sure that you have read permission for the displayed configuration 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.

• 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

• The file does not exist.

  • For Log File Trapping:

  Stop log file traps and starting log file traps.

  • For Event Forwarding, Event Log Trapping, or Local Action:

  Make sure that the displayed configuration file or directory exists and that it is accessible.

  If it does not exist, create a configuration file on the agent host and then retry the operation.

• The directory does not exist.

  Make sure that specified file or directory by the log-file trap startup definition file exists and that it is accessible.

  Make sure that the specified file or directory exists and that it is accessible.

• A required service or process is not running.

  Make sure that the relevant service or process is running. If it is not running, take the following actions, and then retry the operation.

  • Start the service or process.

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

• A communication error occurred.

  Check the network condition and status with the acquired target.

  Also make sure that JP1/Base is running.

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

  • Start the service or process.

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

• The processing is busy. Please try again.

  Wait awhile, and then retry the operation.

• A memory shortage occurred on the manager host.

  Make sure that there is enough free memory on the manager host, and then retry the operation.

• A memory shortage occurred on the agent host.

  Make sure that there is enough free memory on the agent host, and then retry the operation.

• A system error occurred.

  Make sure the output destination of the displayed configuration file and the log-file trap startup definition file does not contain a directory of the same name as the that file.

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

• 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

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