Hitachi

JP1 Version 12 JP1/Integrated Management 2 - Manager Messages


KAVB1869-E

The common exclusion condition group could not be updated. (cause = cause)

An error occurred when an attempt to update the common-exclusion-conditions extended definition file was made.

S:

Terminates definition update processing.

O:

If one of the following messages is displayed for cause, check the operation mode for the JP1/IM - Manager common exclusion-conditions, restart JP1/IM - View, and then retry the operation.

  • JP1/IM - Manager is running in compatibility mode.

  • The common exclusion conditions is operating in a basic mode.

  • The common exclusion conditions is operating in a extended mode.

If one of the following messages is displayed for cause, delete unnecessary common exclusion-condition groups.

  • The number of common exclusion condition group (extended) definitions exceeds the limit.

  • The filter size of the common exclusion condition group (extended) exceeds the limit.

If the message shown below is displayed for cause, the definition file might be corrupted. Stop JP1/IM - Manager, change the operation mode for the common exclusion-conditions to basic mode, and then change it back to extended mode to initialize the definition of the common exclusion-conditions (extended).

  • The common exclusion extended definition file is invalid.

If the following message is displayed for cause, allocate sufficient memory, and then retry the operation.

  • A memory shortage occurred while loading was being performed.

If the following message is displayed for cause, check whether a shortage has occurred in other OS resources such as file descriptors.

  • An I/O error occurred while loading was being performed.

If the message shown below is displayed for cause, the definition includes a character that might cause character corruption when the definition is stored. Ensure that any environment-dependent character or other character that might cause character corruption is not used, and then apply the definition again.

  • A character that cannot be stored successfully is included.

If a message other than the above is displayed for cause or if the problem cannot be resolved, check the following OS log items.

  • In Windows: Windows event log

  • In UNIX: System log (syslog)

After checking the OS log items, check whether a shortage has occurred in other OS resources such as file descriptors. If a resource shortage has not occurred, use the data collection tool to collect data, and then contact a system administrator.