Common gateway error messages

Gateway_name Writer: MemStrDup() failure in _gateway_name CacheAdd().

Gateway_name Writer writer_name: Memory allocation failed.

Gateway_name Writer: Memory allocation failure.

Gateway_name Writer: Memory allocation error.

Gateway_name Writer: Memory reallocation error.

Failed to allocate memory in writer writer_name.

Gateway_name Writer writer_name: Failed to allocate memory for a GPCModule handle.

Gateway_name Writer: Serial x not found in serial cache. Cannot Delete.

Gateway_name Writer writer_name: Failed to construct path to gateway_name Read/Write Module.

Gateway_name Writer writer_name: Failed to construct the argument list for gateway_name Module.

Gateway_name Writer writer_name: GPCModule creation failed.

Gateway_name Writer writer_name: Failed to start the OS-gateway_name Writer.

Gateway_name Writer writer_name: Failed to start the gateway_name-OS Reader.

Failed to start the ObjectServer gateway reader or writer module.

Check that the module is installed in the correct location and that the file permissions are set correctly.

Gateway_name Writer writer_name: Failed to shutdown gateway_name Writer.

Failed to stop gateway writer module.

Check the writer log file for more information.

Gateway_name Writer writer_name: Failed to construct path to gateway_name Read/Write Module.

Failed to construct the path to the gateway reader or writer module application.

Check that the module is installed in the correct location and that the file permissions are set correctly.

Gateway_name Writer writer_name: Failed to find the gateway_name Read/Write Module [x].

Cannot find the module binary.

Check that the module is installed in the correct location and that the file permissions are set correctly.

Gateway_name Writer writer_name: Incorrect permissions on the gateway_name module binary [x].

The module's file permissions are set incorrectly.

Check that the module is installed in the correct location and that the file permissions are set correctly.

Gateway_name Writer writer_name: Failed to create the Serial Cache Mutex.

The gateway writer failed to create the necessary data protection structure for the internal serial number cache due to insufficient resources. This is generally due to insufficient memory.

Try to free more memory.

Gateway_name Writer writer_name: Failed to create the Conn Mutex.

The gateway writer failed to create the necessary data protection structure for the ObjectServer connection due to insufficient resources.

Try to free more memory.

Gateway_name Writer writer_name: Failed to start the gateway_name-to-OS service thread.

The gateway failed to spawn the service thread.

Check that the gateway can access the ObjectServer.

Gateway_name Writer writer_name: Failed to send a shutdown request to the gateway_name Writer.

The gateway did not shut down cleanly.

Check the writer log file for more information.

Failed to install SIGCHLD handler.

Failed to install SIGPIPE handler.

The gateway failed during handler installation.

Refer to your support contract for information about contacting the helpdesk.

No <mapname> attribute for gateway_name writer writer_name.

The gateway could not find the map name.

Check the configuration file.

<mapname> attribute is not a name for gateway_name writer writer_name.

Incorrect writer name given.

Check the configuration file.

A MAP called <map> does not exist for gateway_name writer writer_name.

The gateway could not find the specified map.

Check the configuration file.

MAP <map> is invalid for gateway_name writer writer_name.

The given map is not valid.

Check the configuration file.

Map <map> is not the journal map and cannot contain the <journal map name> map item in gateway_name Writer writer_name.

If this map is not the journal map, then the JOURNAL_MAP_NAME attribute is set incorrectly.

Check the JOURNAL_MAP_NAME attribute in the gateway configuration file.

Gateway_name Writer: Failed to send gateway_name Event to the gateway_name Writer module.

The gateway failed to send a given event.

Check the log files for more information.

Gateway_name Writer: Failed to wait for return from the gateway_name Writer module.

There was an error in retrieving the success statement.

Check the log files for more information.

Gateway_name Writer: Failed to read the status return message from the gateway_name Writer module.

The gateway failed to retrieve the status of a module.

Check the log files for more information.

Gateway_name Writer: Failed to send event to gateway_name.

The module failed to send the event to gateway.

Check the log files for more information.

Gateway_name Writer: gateway_name Writer Module experienced Fatal Error.

There was a fatal error.

Check the log files for more information.

Gateway_name Writer: Failed to send event to gateway_name. Unknown type.

The gateway received unexpected type.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Failed to build serial index.

The gateway failed to build indexes.

Check that the Serial column exists in the ObjectServer alerts.status table.

Incorrect data type for the Serial column.

The gateway did not receive the correct data type.

Check that the data type for the Serial column in the ObjectServer alerts.status table is an integer.

Gateway_name Writer: Failed to build server serial index.

The gateway failed to get the server serial index.

Check that the ServerSerial column exists in the ObjectServer alerts.status table.

Incorrect data type for the Server Serial column.

The gateway did not receive the correct data type.

Check that the data type for the ServerSerial column in the ObjectServer alerts.status table is an integer.

Gateway_name Writer: Failed to build server name index.

The gateway failed to get the server name index.

Check that the ServerName column exists in the ObjectServer alerts.status table.

Incorrect data type for the Server Name column.

The gateway did not receive the correct data type.

Check that the data type for the ServerName column in the ObjectServer alerts.status table is a string.

Gateway_name Writer: Failed to find field <fieldnumber> in gateway_name Event.

The gateway could not find the field number it was looking for.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Invalid field name for expansion on action SQL [<field>].

The gateway received an invalid field name.

Refer to the IBM Tivoli Netcool/OMNIbus Administration Guide for information about ObjectServer SQL.

Gateway_name Writer: Unenclosed field expansion request in action SQL [<sql action>].

The gateway did not find an enclosing bracket.

Check the action.sql file.

Gateway_name Writer: Failed to turn counter-part notification back-on. Fatal error in gateway_name-to-OS Feedback.

Gateway_name Writer: Failed to turn counter-part notification off.

Gateway_name-to-OS Feedback failed.

The gateway failed to send a notify command.

This is an internal error. Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Failed to send SQL command to ObjectServer.

Gateway_name-to-OS Feedback failed.

The gateway failed to send the SQL command to the ObjectServer.

Check the ObjectServer log file.

Failed to find the column <column_name> in map <map_name>.

The gateway failed to find the given column.

Check that the given column name is entered correctly in the configuration file and that it is shown in the ObjectServer alerts.status table.

Gateway_name Writer: Failed to lock the cache mutex.

The writer failed to lock the ObjectServer feedback connection in order to access the connection and feed back problem ticket data changes for the associated alert.

This lock failure may be due to insufficient resources or as a result of the underlying threading system preventing a deadlock between multiple threads that are contending for the resource.

Failed to find cached problem ticket for serial <serial number> using map <map name>.

The gateway failed to find the specified cache problem ticket number.

Check that the specified ticket was originally created by the gateway.

Gateway_name Writer: Failed to unlock the cache mutex.

After access to the cache, an attempt to unlock the data structures protection lock failed. This message indicates that the gateway is in a position which will lead to a deadlock situation.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Cache add error.

The gateway could not add the serial to the serial cache due to insufficient resources.

Try to free more memory.

Gateway_name Writer writer_name: Failed to create gateway_name Event for journal update.

The gateway failed to create the journal event update.

Check the writer log file.

Gateway_name Writer writer_name: Failed to send journal update event to gateway_name.

The gateway failed to send journal event update.

Check the writer log file.

<attribute name> attribute is not a string for gateway_name writer writer_name.

An attribute in the writer was of an incorrect data type.

Check the writer definition in the configuration file.

No <attribute name> attribute for gateway_name writer writer_name given.

The gateway failed to find the attribute.

Add the attribute to the writer definition in the configuration file.

Gateway_name Writer writer_name: Failed to find the <counterpart attribute> attribute for the writer. This is necessary due to bi-directional nature.

An attempt to find the necessary counterpart attribute failed.

Check the configuration file.

Gateway_name Writer writer_name: Is not a name for an Object Server reader.

The gateway found an incorrect data type.

Check the configuration file.

Gateway_name Writer writer_name: Reader <reader> was not found for counter part.

The reader was not found.

Check the counterpart configuration in the configuration file.

Gateway_name Writer writer_name: Failed to send SKIP Command.

This command failed to disable IDUC on a bidirectional connection.

Refer to your support contract for information about contacting the helpdesk.

Connection to feedback server failed.

The gateway failed to make a connection.

Check the ObjectServer log file.

Failed to set the death call on the feedback connection.

The gateway failed to set the necessary property.

This is an internal error. Refer to your support contract for information about contacting the helpdesk.

Writer counterpart error.

The gateway failed to find the counterpart attribute for gateway writer.

Check the counterpart configuration in the configuration file.

Gateway_name Writer: Failed to stat() the action SQL file "filename".

The gateway failed to stat the file in order to determine its size.

Check the file access permissions for the specified action file.

Gateway_name Writer: Empty action SQL file "filename".

File "filename" is empty.

Check the action SQL file.

Gateway_name Writer: Failed to open the action SQL file "filename".

The gateway failed to open the file.

Check the file permissions.

Gateway_name Writer: Failed to read the action SQL file "filename".

The gateway failed to read the file.

Check the file permissions.

Gateway_name Writer: No Action SQL find in file "filename".

There is no action SQL in the file.

Check the file.

Gateway_name Writer writer_name: Failed to read the conversions table.

The gateway failed to read the conversions table.

Check the file permissions.

Gateway_name Writer: Failed to find PM %s in cache for return PMO event.

The gateway has received a Problem Management Open return event from gateway for the problem ticket. When an attempt was made to look up the problem ticket number in the writer's cache, in order to determine the serial number of the ticket's associated alert, no record could be reclaimed or found.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Open Feedback Failed.

The gateway failed to construct the open action SQL statement or send the SQL action command to the server.

Check the ObjectServer SQL file.

Gateway_name Writer: No Update action SQL for gateway_name Update event.

There is no update action SQL statement.

Check the configuration file.

Gateway_name Writer: Failed to find PM %s in cache for return PMU event.

The gateway has received a Problem Management Update return event from gateway for the problem ticket. When an attempt was made to look up the problem ticket number in the writer's cache in order to determine the serial number of the ticket's associated alert, no record could be reclaimed or found.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Update Feedback Failed.

The gateway failed to construct the open action SQL statement or send the SQL action command to the server.

Check the ObjectServer log file.

Gateway_name Writer: Failed to find PM %s in cache for return PMJ event.

The gateway has received a Problem Management Journal return event from gateway for the problem ticket. When an attempt was made to look up the problem ticket number in the writer's cache in order to determine the serial number of the ticket's associated alert, no record could be reclaimed or found.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Journal Feedback Failed.

The gateway failed to construct the open action SQL statement or send the SQL action command to the server.

Check the ObjectServer log file.

Gateway_name Writer: Failed to find PM %s in cache for return PMC event.

The gateway has received a Problem Management Close return event from gateway for the problem ticket. When an attempt was made to look up the problem ticket number in the writer's cache in order to determine the serial number of the ticket's associated alert, no record could be reclaimed or found.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Close Feedback Failed.

The gateway failed to construct the open action SQL statement or send the SQL action command to the server.

Check the ObjectServer log file.

Received error code <code> from Reader/Writer Module - [<message>].

The gateway received an error message.

Check the module log files.

Gateway_name Writer: Failed to read gateway_name event from gateway_name Reader Module.

The gateway failed to read the event sent by the gateway reader module.

Check the reader log files.

Gateway_name Writer: Received event of type <event type> which was unexpected.

The gateway received an unknown event type.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Received invalid known message from Reader/Writer Module for this system.

The gateway received an invalid known message.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Received unknown message from Reader/Writer Module.

The gateway received an invalid unknown message.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Failed to block on data feed from gateway_name Reader Module.

The gateway failed to block due to a shutdown request. This message is displayed when the gateway is shutting down.

Refer to your support contract for information about contacting the helpdesk.

Gateway_name Writer: Fatal thread termination. Stopping gateway.

A thread exited unexpectedly.

Check the gateway log files.

<attribute name> attribute is not a string for gateway_name writer writer_name - IGNORED

An attribute name is not recognized. The gateway will ignore it.

Check the gateway log files.

<attribute name> attribute must be set to TRUE or FALSE for writer writer_name.

An attribute name has not been set to TRUE or FALSE.

Check the gateway configuration file.

Gateway_name Writer writer_name: Failed to shutdown gateway_name Reader/Writer Modules.

The gateway failed to shut down the reader and writer modules.

Check the module log file.

Gateway_name Writer writer_name: Failed to disconnect feedback connection.

The disconnect of feedback channel failed.

Check the ObjectServer log file.

Failed to create gateway_name event structure for a problem management open event in writer writer_name.

The gateway writer failed to allocate a gateway event structure for a problem management open event due to insufficient memory resources.

Try to free more memory.

Gateway_name Writer: FEEDBACK FAILED!!

The gateway failed to store the problem number.

Check the ObjectServer log file.

Failed to create journal for gateway_name writer writer_name (from INSERT)

The gateway failed to create journal.

Check the writer log file.

Failed to create gateway_name event structure for a problem management update event in writer writer_name.

The gateway writer failed to allocate a gateway event structure for a problem management update event due to insufficient memory resources.

Try to free more memory.

Gateway_name Writer writer_name: Failed to delete problem ticket from cache for serial <serial number>.

The gateway failed to delete serial number from cache.

This is an internal error. You can ignore it.

Failed to create gateway_name event structure for a PMC event in writer writer_name.

The gateway writer failed to allocate a gateway event structure for a Problem Management Close event due to insufficient memory resources.

Try to free more memory.