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
Exception during marshalling notification message to element: cause

An exception occurred while the probe was parsing incoming events. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in creating EventNotification List event: cause

An exception occurred while the probe was creating an ObjectServer event in response to receiving an event notification from the OPC UA server. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in parsing notification event: cause

An exception occurred while the probe was parsing data in an event notification received from the OPC UA server. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in creating DataChange Notification event: cause

An exception occurred while the probe was creating an ObjectServer event in response to receiving a data change notification from the OPC UA server. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in parsing DataChange event: cause

An exception occurred while the probe was parsing data in a data change notification received from the OPC UA server. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in creating StateChange Notification event: cause

An exception occurred while the probe was creating an ObjectServer event in response to receiving notification of a state change in a monitored item. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Exception in parsing StateChange event: cause

An exception occurred while the probe was parsing data in a state change notification received from the OPC UA server. The cause contains a message associated with the exception.

Contact IBM Support.

Run the probe in debug and stream capture mode to collect the probe debug log and stream capture log and submit the logs to IBM support.
Unknown event type: type with id: identifier

The probe received a notification from the OPC UA server that is not one of the types that the probe recognizes. That is, the notification does not indicate a data change, event notification, or a status change. The type shows the type of the notification and identifier is its identifier.

Currently, the probe only supports a few event types identified in the OPC UA standard. If the probe receives an unknown event type, contact IBM support. It could be that either the probe is unable to recognize the event type or the event type is not supported.
ServiceException during setting up properties for endpoint...

A ServiceException has occurred while the probe was reading the properties required to set up communication with the OPC UA server.

Contact IBM Support.
Unable to connect as client to endpoint: cause

An exception occurred during the process of connecting to the OPC UA server, creating a session and activating that session. The cause contains a message associated with the exception.

Make sure that the OPC UA server is up and running and check the connection related properties such as host, port, and service name. Ensure that there is no firewall issue blocking the connection. If the problem continues, contact IBM support.
Timeout while waiting response from OPC-UA, wait for next resync cycle.

When the probe issues a Publish request to the OPC UA server, it expects a response within a set time period. This warning indicates that there was no response. This can occur for any of the following reasons:

  • There are no notifications on the server to send to the probe.

    In this case, the server queues the publish request and sends notifications when any are available. In addition the probe tries again at the next publishing interval.

  • There is an error in the connection between the probe and the server.
  • The server is incorrectly configured.

The probe will retry again in the next resynchronize cycle.
MalformedURL Exception during create URL for WSDL location: cause

The URL of the WSDL file for the SOAP session is incorrectly formatted. The cause contains more information on the nature of the error. Either the value of the EndpointWsdlLocation property is incorrect or, if that property has no value, one or more of the following properties have incorrect values:

  • EndpointHttpHost
  • EndpointHttpPort
  • EndpointSessionService
    Name

Check that the value of each of the properties has the correct syntax, and that the values are correct for your site. Correct any errors and restart the probe.

Unable to create session.

The probe was unable to create the session with the OPC UA server through the OPC UA CreateSession service.

The values of one or more of the following properties are incorrect or invalid:

HttpTimeout

MaxResponseMessageSize

OPCSessionName

RequestedSession Timeout

Ensure that all these properties have values that are valid for your site and then restart the probe.
Unable to activate session identifiers: sessionid

The probe was unable to activate the OPC UA session. The sessionid contains the identifier of the session.

It is a very rare case that the OPC UA server returns a session ID that the probe cannot activate. It could be one of the following has occurred:

  • The activate session has expired.
  • The OPC UA server has removed the activate session.
  • The OPC UA server is no longer responsive or alive.

Ensure that the OPC UA server is running. Then, stop the probe and retry the connection to the OPC UA server.

If the problem continues, contact IBM support.
Unable create monitored items.

The probe was unable to send the list of items to be monitored to the OPC UA host as part of the CreateMonitoredItems service.

Check that the definitions of the monitored items in the OpcUaEvent.xml or OpcUaDataChange.xml configuration files and any notification filters you have defined are valid. Correct any errors and restart the probe.
Unable create subscription.

The probe was unable to create a subscription for monitored items because the OPC UA CreateSubscription service failed.

The values of one or more of the following properties are incorrect or invalid:

MaxNotificationPer
Publish

RequestedLifetimeCount

RequestedMaxKeepAlive
Count

RequestedPublishing
Interval

Ensure that all these properties have values that are valid for your site and then restart the probe.
Unable to publish and get alarms from endpoint.

A Publish operation failed to complete successfully.

Check that the OPC UA server is operating and has connectivity to the probe. In addition check that the following properties have values that are correct and valid:

HttpTimeout

MaxResponseMessageSize
There is some errors occurred during publish request:

The OPC UA Publish service returned one or more errors. The lines in the log file immediately following this message describe the publishing errors.

For each error, locate its cause and amend the configuration of the probe, the server, or both as appropriate.
SOAP Handler exception for outbound message: cause

An exception occurred when the probe was manipulating the header of an outbound SOAP message. The cause contains a message associated with the exception.

Contact IBM Support.
SOAPException during stream capture logging: cause

A SOAP exception occurred when the probe was capturing the stream of SOAP data to a file. The cause contains a message associated with the exception.

Check the following properties and ensure that the configuration inside the opc_ua_dsl_log. properties file is correct:

  • StreamCapture
  • StreamCapturePath
  • DSLLogConfig

If the problem continues, contact IBM support.
IOException during stream capture logging: cause

An I/O error occurred when the probe was capturing the stream of SOAP data to a file. The cause contains a message associated with the error.

This exception is rare, but when it occurs it is typically caused by the environment or machine issues related to the I/O operation not being able to open and write into the log file.

Check to ensure that the machine is stable and healthy (for example, sufficient disk space).
Exception during stream capture logging: cause

An error, other than a SOAP exception or an I/O error, occurred when the probe was capturing the stream of SOAP data to a file. The cause contains a message associated with the error.

Contact IBM support and provide the exception cause and details.
IOException when closing stream capture buffer: cause

An I/O error occurred when the probe tried to close the file of captured SOAP data. The cause contains a message associated with the error.

This exception is rare, but when it occurs it is typically caused by the environment or machine issues related to the I/O operation not being able to close the buffer log.

Check to ensure that the machine is stable and healthy (for example, sufficient disk space).
Exception when closing stream capture buffer: cause

An error, other than an I/O error, occurred when the probe tried to close the file of captured SOAP data. The cause contains a message associated with the error.

This exception is rare, but when it occurs it is typically caused by the environment or machine issues.

Contact IBM support and be prepared to provide the exception cause and details.
Unable to create probe watch.

An error occurred when the probe tried to create and send a ProbeWatch message to the ObjectServer.

Check that the ObjectServer is up and running and that the probe server is in good health (for example, there is sufficient CPU memory and disk space).

It is possible that the errors are caused by the Tivoli Netcool/OMNIbus Core library, nonnative, or probe SDK Java. If this is the case, contact IBM support.
Unable to find the configuration file defined by the MonitoredItems ConfigFile property: cause

The probe was unable to find the XML file that defines the set of items to monitor. The path of this file is in the MonitoredItemsConfigFile property. The cause contains a message associated with the error.

Make sure that the value of the MonitoredItems ConfigFile property is correct and has the correct syntax. Ensure that the probe can open and read the file. Follow any advice given the accompanying error message.
The returned status code Status indicates that some issues may have occurred when creating the monitored items on the server.

The status code returned from the OPC UA CreateMonitoredItem service is not a success code. Status contains the status code that the OPC UA server returned.

Refer to the OPC UA specification or the OPC UA server (vendor) documentation to verify the cause of the status code and possible ways to correct the issue.
Unable to close the buffer reader - IOException: cause

The probe encountered an IO exception when it tried to close the buffered reader that receives notifications. The cause contains a message associated with the error.

This exception is rare, but when it occurs it is typically caused by the environment or machine issues related to the I/O operation not being able to close the buffer log.

Check to ensure that the machine is stable and healthy (for example, sufficient disk space).
The probe only supports a configuration file that has no more than CharCount characters.

The probe limits the size of the XML file that defines the items to monitor to CharCount characters. The file you have supplied exceeds that limit.

Reduce the size of the file by means such as:

  • Reducing or removing comments
  • Reducing the amount of white space
  • Removing some definitions of monitored items
Could not find the related attribute list for the client handle handle. The probe will use the default attribute list for the event.

The probe should generate the event attribute list for the client handle specified for the <ClientHandle></ClientHandle> tag in the XML configuration file associated with the MonitoredItemsConfigFile property. However, the probe could not find the event attribute list for this client handle. Thus, the probe will use the default event attribute list.

Ensure that you have specified a valid event attribute list in the XML configuration file associated with the MonitoredItems ConfigFile property (the default is $OMNIHOME/var/OpcUaEvent.xml).

Ensure that you specify a unique client handle in the <ClientHandle></ClientHandle> tag for each of the event sets you want to monitor. A client handle is an integer and you can start with the values 1, 2, 3, and so forth. Thus, if there were three event sets that you want to follow you would specify the following:

<ClientHandle>1
</ClientHandle>
.
.
.
<ClientHandle>2
</ClientHandle>
.
.
.
<ClientHandle>3
</ClientHandle>
.
.
.

For each client handle, ensure that you define a valid set of event attributes within the <SimpleAttribute Operand>
</SimpleAttribute Operand> tags contained within the <SelectClauses>
</SelectClauses> tags.
Duplicate client handle key found. The client handle already exists in the current attribute map.

The probe found a duplicate client handle where that client handle already existed in current event attribute map.

Ensure that you have specified a unique client handle in the XML configuration file associated with the MonitoredItems ConfigFile property (the default is $OMNIHOME/var/OpcUaEvent.xml). For the event notification list, you can share the client handle only if you are using the same set of event attributes (defined within the <SelectClauses></SelectClauses> tags for all the monitored events. Otherwise, you should specify a unique client handle (<ClientHandle></ClientHandle> tags) for each set of monitored events.

If you are sharing the client handle correctly as specified previously, ignore this warning message.
Some errors occurred while the probe was creating monitored items.

The probe returned a nonzero status code after attempting to create the monitored event attribute list. The nonzero value indicates that some errors occurred.

Check the log files and the XML configuration file associated with the MonitoredItems ConfigFile property (the default is $OMNIHOME/var/OpcUaEvent.xml) to ensure that the monitored event items configuration is correct.