Error messages

Error messages provide information about problems that occur while running the probe. You can use the information that they contain to resolve such problems.

The following table describes the error messages specific to this probe. For information about generic error messages, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide.

Table 1. Error messages
Error	Description	Action
`Encountered a JAXException attempting to send subscription request` `Encountered a SOAPException attempting to send subscription request` `Encountered a WebServiceException attempting to send subscription request` `Error creating a DocumentBuilder instance: message` `Error creating a JAXBContext instance: message` `Error formatting Expires to String: message` `Error parsing Expires to Date: message` `ReferenceParameter does not exist in SubscribeResponse`	These errors indicate problems with probe startup.	Ensure that theNNMPort property points to the port where the NNMi system has been configured to host the WS-API. Check any firewalls between the probe and the NNMi machine. Confirm that the NNM WebServices API is functioning correctly by checking that your NNMi installation has an Integration Enablement License and that the services are available. This can be confirmed by looking at the jmx-console view of the NNM Jboss server. Check that the environment has been configured to use Java.
`HeartbeatInterval out of range! Please reconfigure property.`	The probe performed a check on the value specified in the HeartbeatInterval property and determined it was out of range.	Check the value of the HeartbeatInterval property an ensure the value is between 1 and 299.
`NNM credentials not recognized` `End Point Started at : Location of Probe's Receiver Endpoint` `End Point Stopped at : Location of Probe's Receiver Endpoint`	These errors indicate problems with the probe configuration.	Ensure that the NNMAddress, NNMPassword, and NNMPort properties are set correctly. Check that the Probe Receiver Port is clear.
`Unable to contact the NNM Incident service for resynchronization because: message`	The probe was unable to contact the NNMi Incident service for resynchronization. The `message` provides additional information about the error.	Check the values of the NNMAddress and NNMPort properties to ensure a valid TCP/IP address and port number for the NNMi system. Also check that there is no firewall blocking access to the NNMi system.
`Unable to process incident array received in resynchronization because: message`	The probe was unable to process the NNMi incident array received in the resynchronization operation. The `message` provides additional information about the error.	Check the values of the NNMUserID and NNMPassword properties to ensure these are valid encrypted identifiers of an account on the NNMi system. Also check that the value specified for the ResyncFilterValue property is valid for the event values specified in the ResyncFilterName property.
`Unable to process requested custom filter`	The probe was unable to process the custom filter. As a result, the probe continues processing with the default resynchronization filters.	A resynchronization filter was defined using the ResyncFilterName, ResyncFilterOperation, and ResyncFilterValue properties. Check each of these properties as follows: That the name you specified for the ResyncFilterName is one of the valid names. Note that these names are case sensitive. That the operation you specified for the ResyncFilterOperation property is one of the valid operators and conditions. The character operators are case sensitive. See Defining a resynchronization filter for the valid values associated with these properties.