Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KNAN22424-E

Collection of operation definition information for profile-type failed. (Cause: detailed-information)

Acquisition of operation definition information failed because of an error.

S:

Stops acquisition of operation definition information.

O:

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

  • 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.

  • The product is not supported.

    In the IM Configuration Management window, make sure that the version of JP1/Base displayed in the product information is 09-00 or later. If the JP1/Base version is 09-00 or later, click Edit IM Configuration, and then confirm again that the version of JP1/Base is 09-00 or later.

  • The data that was acquired while connected to the host is invalid.

    Invalid data may have been received temporarily. Retry the operation.

    Also check the network configuration and status with the acquired host.

  • A request was executed in an invalid operating environment.

    It is possible that the IM configuration (system hierarchy) has been deleted.

    Click Operation, and then Verify IM Configuration to confirm that the current configuration is correct.

  • No authentication servers have been set up.

    Register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.

  • User mapping has not been registered.

    The user mapping information was not registered, or the mapping information file may be corrupted. Re-execute the user mapping configuration command.

  • The execution environment of JP1/Base is invalid.

    Re-register an authentication server using the JP1/Base Environment Settings dialog box (in Windows) or the jbssetusrsrv command (in UNIX), and then re-execute the command.

    If the error cannot be resolved, check the following items:

    • Is the JP1/Base conf directory defined in the common definition?

    • Did the JP1/Base configuration end normally?

    • In Windows: Is there a problem with access permission to the blockade file in the installation destination folder \jp1base\conf\user_acl\blockade?

    • In UNIX: Is there a problem with access permission to the blockade file in the /etc/opt/jp1base/conf/user_acl/blockade directory?

  • The specified event log trap is not running.

    The event log trap might have been stopped by another user or might have terminated abnormally. Check the log data for the event log trap in the integrated trace log.

  • The specified log file trap is not running.

    The log file trap might have been stopped by another user or might have terminated abnormally. Check the log data for the log file trap in the integrated trace log.

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