Error messages

Failed to open listening socket, could not bind to port port number which is already in use by another application

The command port cannot be opened because the value specified by the CommandPort property is already in use (possibly by another instance of the probe).

Specify another port number using the CommandPort property or close the application that is using the specified port.

Failed to send probe watch: exception

The probe is unable to send ProbeWatch messages to the ObjectServer.

Check the connection between the probe and the ObjectServer.

Failed to accept new client connection, socket error code= ErrorCode

The command port is unable to accept a new incoming connection from the client because of a socket error.

Check the detailed description of the ErrorCode that is available from the Microsoft MSDN Library. Go to http://msdn.microsoft.com/en-us/library and search for Windows Sockets Error Codes.

[Command Port] hostname Failed to serve client. Reason: reason

The command port is unable to continue processing requests from the client running on the host hostname.

Check the reason given in the error message for more details. This problem is sometimes caused by a forced disconnection on the client side.

[Command Port] hostname Failed to write to client: client. exception

An I/O problem is preventing the probe from sending processed results back to the command port client.

Check the exception given in the error message for more details. This problem is sometimes caused by a forced disconnection on the client side.

Command port request of alert field entry cannot be processed and is thus ignored

The probe is unable to set the requested alert field specified by the alert field entry argument sent to the command port.

Ensure that the argument is specified in the following format:

alertId(field=value)

For more information, see the description of the set_field command in Command port module.

Unable to locate SCOM SDK assembly file sdk file in the folder specified by the ScomSdkDir property

The probe failed to load the .NET libraries located in the folder specified by the ScomSdkDir property.

Verify that the ScomSdkDir property is correctly specified. For more information, see Properties and command line options.

If this problem persists, contact IBM Software Support.

Failed to process alerts update. Reason: reason

The command port is unable to process a client request to update specified alert fields and submit the result to Microsoft SCOM 2012.

The client commands are in the proper format but there is another error, such as a non-updatable field being specified or the connection to Microsoft SCOM 2012 is down. Check the reason given in the error message for more details. Check in guide on updatable fields and also reason for more details.

For more information about updating alarm fields in Microsoft SCOM 2012 using the command port, see Command port module.

Probe configuration could not be loaded, probe should not reconnect.

There is an error in the properties file that is preventing the probe configuration from being loaded.

Check the properties file for syntax errors.

Refer to Properties and command line options and verify that the property values are specified correctly.

Failed to process incoming alert with id alert GUID, alert is discarded

The probe failed to parse the given alert retrieved from Microsoft SCOM 2012.

Microsoft SCOM 2012 might have sent the alert in an unexpected format. Contact IBM Software Support.

Missing assembly file dll file in folder app dir. Please make sure probe package and dependencies packages are properly installed

A library file required by probe is missing.

This error is probably caused by a missing or manually deleted file that the probe depends on. You might need to reinstall the probe.

Unable to get events. Reason: Failed to connect to SCOM. Further Reason: Unable to resolve configured SCOM host name of hostname. Even Further Reason: The requested name is valid, but no data of the requested type was found

The host name specified by the ScomHost property cannot be resolved to an IP address.

Verify that a valid host name has been specified for the ScomHost property.

Use a DNS tool to verify that the value of the ScomHost property can be resolved to an IP address.

If the value of the ScomHost property is correctly specified, verify that the DNS settings on the probe's host are set correctly.

Unable to get events. Reason: Failed to connect to SCOM. Further Reason: The client has been disconnected from the server. Please call ManagementGroup.Reconnect() to reestablish the connection. Even Further Reason: The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:30:00'. Next Further Reason: An existing connection was forcibly closed by the remote host

The connection between the probe and Microsoft SCOM 2012 was forcibly closed.

If this error occurs after the probe has just started, it is probably caused by an incorrect Windows user account. Ensure that the account has been provisioned in Active Directory.

If this error occurs after the probe has started and run for some time, it is caused by the timeout of an idle connection between the probe and Microsoft SCOM 2012. Specify a shorter time period for the PollInterval property.

Unable to get events. Reason: Failed to connect to SCOM. Further Reason: The user does not have sufficient permission to perform the operation. Even Further Reason: SOAP security negotiation with scom_url for target scom_url failed. See inner exception for more details. Next Further Reason: The Security Support Provider Interface (SSPI) negotiation failed.

The probe failed to complete client authentication with Microsoft SCOM 2012.

The value specified for the ConnectorPassword property is incorrect. It does not match the correct password for the probe's user account.

If you have encrypted the password, verify that the encrypted string starts and ends with an @ symbol.

Verify that the generic Netcool/OMNIbus ConfigKeyFile property is correctly specified.

For more information about encrypting property values, see the IBM Tivoli Netcool/OMNIbus Administration Guide (SC14-7605).

For more information about generic Netcool/OMNIbus properties, see the IBM Tivoli Netcool/OMNIbus Probe and Gateway Guide (SC14-7608).

Unable to get events. Reason: Failed to connect to SCOM. Further Reason: The user user ID does not have sufficient permission to perform the operation.

The probe successfully completed client authentication but failed it authorize with Microsoft SCOM 2012.

The user account specified by the ConnectorUser property does not have sufficient permissions for the probe to continue operation. Verify that the user account's group has been assigned the Operations Manager Administrator user role in the Microsoft SCOM 2012 Operations Console.

Unable to get events. Reason: Timed out in receipt of any event from SCOM

The probe timed out due to inactivity on the connection to Microsoft SCOM 2012.

Change the value of the Timeout property to ensure that events get processed. For more information about specifying a value for this property, see Inactivity.

Unable to get events. Reason: Error in probe configuration. Further Reason: detail

There is an error in the properties file. The probe cannot proceed with its operations.

Check the detail given in the error message and check the property listed there.

Unable to get events. Reason: detail

The probe has encountered an unspecified error.

Check the detail given in the error message for more information.