KAVJS2607-E

The possible causes for the service for which property distribution failed are as follows:

• A distribution-destination service has stopped or a communication error has occurred.

• The versions of the Store databases for the distribution-destination services do not match.

• The maximum number of nodes that can be added to a distribution-destination service has been exceeded.

• If the name of a property is displayed, the property does not exist in the distribution-destination service, or an agent in the service is in the suspended state.

(S)

Distributes properties to the services that can receive properties and ends processing.

(O)

For the failed distribution-destination service(s):

• Make sure the operating status and communication status of the service and manager are normal.

• Make sure the versions of the distribution-source Store databases match.

• Make sure the number of property nodes does not exceed the maximum.

• If "Realtime Report Data Collection Mode" is displayed as the property name, check whether the version of the PFM - Base or PFM - Manager installed on the same host as that of the distribution-destination service supports the history collection priority function. For a version compatible with the history collection priority function, check whether the function is enabled in PFM - Base or PFM - Manager.

• If "Monitoring Level" is displayed for the property name, use either the Monitoring Suspension Settings window or a monitoring resume command to resume the monitoring of agents in the suspended state. If the problem persists, disable the monitoring suspension function.