Error Messages
The following table lists the error messages of TIBCO ActiveMatrix BusinessWorks Plug-in for IBM MQ.
| Message Identifier | Message | Solution |
|---|---|---|
| TIBCO-BW-PALETTE-MQ-000001 | {0} | This is an internal error. It is appropriate to open a support issue for this error. |
| TIBCO-BW-PALETTE-MQ-100001 | {0) | This is a trace message and resolution is not applicable. |
| TIBCO-BW-PALETTE-MQ-200001 | {0} | This is a debug message and resolution is not applicable. |
| TIBCO-BW-PALETTE-MQ-300001 | {0} | This is an informational message and it highlights the runtime progress of the activity. Resolution is not applicable. |
| TIBCO-BW-PALETTE-MQ-400001 | {0} | This is a warning message, usually related to having received a warning from the MQ API. No resolution is necessary. |
| TIBCO-BW-PALETTE-MQ-400401 | Warning; failed to release resources in event source: [{0}] | This indicates that connections or destinations may have been left open after the end of the process. Investigate if this occurs frequently. |
| TIBCO-BW-PALETTE-MQ-400402 | Warning; explicit client confirmation not encountered for message in activity [{0}] | A confirmation was indicated for this process starter and none was encountered in the process. Correct the process. |
| TIBCO-BW-PALETTE-MQ-400403 | Warning; confirm encountered for a message that did not specify explicit client confirmation | A confirmation activity was encountered for a process started that did not indicate confirmation was required. Correct the process. |
| TIBCO-BW-PALETTE-MQ-400404 | Warning, error while closing client: [{0}] | An exception happened when closing the connection to the queue manager. An orphaned connection might exist until the instance is terminated. Investigate if this occurs frequently |
| TIBCO-BW-PALETTE-MQ-400405 | Warning; exception encountered while rolling back a queuing operation; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | Check to see if a message was removed from the queue without having been properly processed. Investigate to ensure that the message was successfully rolled back. |
| TIBCO-BW-PALETTE-MQ-400406 | Warning; exception encountered while closing a destination; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | An exception was encountered while closing the destination object. Examine the error codes and consult the IBM MQ documentation for more information. |
| TIBCO-BW-PALETTE-MQ-400407 | Warning; exception encountered while closing the queue manager; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | There is no resolution required for this warning. |
| TIBCO-BW-PALETTE-MQ-400408 | Warning; exception encountered while disconnecting from the queue manager; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | There is no resolution required for this warning. |
| TIBCO-BW-PALETTE-MQ-400409 | Warning; exception encountered during commit; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | Examine the error codes and consult the IBM MQ documentation for more information. Contact support if no resolution is reached. |
| TIBCO-BW-PALETTE-MQ-400410 | IBM MQ warning during get or put operation; CompCode [{0}] ReasonCode [{1}] ErrorCode [{2}] DecodedMessage [{3}] | This operation completed successfully but a warning exception was thrown. Examine the output of the activity to be sure that it conforms to expectations. The most common reason for a warning is that an encoding problem exists with the message. |
| TIBCO-BW-PALETTE-MQ-400411 | The named property [{0}] does not exist in the message or is not of type [{1}] | The schema which represents the message properties contained a node that was not in the message. This could be normal or could indicate an incorrect schema. |
| TIBCO-BW-PALETTE-MQ-500200 | Value "[{0}]" for field [{1}] contains whitespace | Correct the configuration or mapped variable. |
| TIBCO-BW-PALETTE-MQ-500201 | Error sending message: [{0}] | The message has not been sent. Use the error message provided to debug the issue. Contact support if no resolution is reached. |
| TIBCO-BW-PALETTE-MQ-500202 | Error connecting to queue manager: [{0}] | The plug-in cannot connect to the queue manager, either because it is misconfigured or there is a network or queue manager problem. Correct the problem and retry. |
| TIBCO-BW-PALETTE-MQ-500203 | Error Opening:[{0}] [{1}] | Ensure that the queue exists and this this user has access to it. |
| TIBCO-BW-PALETTE-MQ-500205 | Error closing destination [{0}] with close option [{1}] message: [{2}] | No resolution required. There has been an error closing the destination after the process has finished committing its work. |
| TIBCO-BW-PALETTE-MQ-500206 | Error processing credentials: [{0}] | Examine the configuration of the connection resource's TLS configuration for possible problems with the keystore password. |
| TIBCO-BW-PALETTE-MQ-500207 | Message get error; DecodedMessage [{0}] CompCode [{1}] ReasonCode [{2}] ErrorCode [{3}] | The schema for the message did not match the content or the code page used to decode it was incorrect. Correct the configuration. |
| TIBCO-BW-PALETTE-MQ-500208 | Error getting a message: [{0}] | This is a generic get failure. Examine the contents of the embedded message for more information. Contact support if no resolution is reached. |
| TIBCO-BW-PALETTE-MQ-500209 | Error connecting to the local queue manager because the native libraries are not available on java.library.path: [{0}] | Ensure that the relevant library search paths for the platform contain the MQ native library directories. Refer to the Users Guide for assistance. |
| TIBCO-BW-PALETTE-MQ-500210 | Connection resource local bindings are not supported for XA transactions | In order to participate in an XA transaction the connection must be of the Remote or CCDT type. |
| TIBCO-BW-PALETTE-MQ-500211 | Failed to create destination [{0}:{1}] | The configuration of the destination is incorrect. Verify that this destination exists and that the application is authorized to open it. |
| TIBCO-BW-PALETTE-MQ-500212 | Configuration error; Model queue not provided | Provide a model queue for the temporary destination. |
| TIBCO-BW-PALETTE-MQ-500213 | Malformed URL exception for client connection table: [{0}] | The CCDT TAB file was not found. Valid formats for this URL are: file:///.. ftp://... http://... A browser can be used to test that the URL is valid. |
| TIBCO-BW-PALETTE-MQ-500214 | Internal Error; missing required input parameter: [{0}] | No input was provided for a put or publish activity. Provide content for the message being sent. |
| TIBCO-BW-PALETTE-MQ-500215 | Activity [{0}] confirm failed | The queue manager was unable to commit a unit of work. Examine the error message and queue manager logs to determine why the queue manager could not perform the associated commit operation. |
| TIBCO-BW-PALETTE-MQ-500216 | Queue manager failed to commit a unit of work: [{0}] | Examine the error message and queue manager logs to determine why the queue manager could not perform the associated commit operation. |
| TIBCO-BW-PALETTE-MQ-500217 | Get timed out | There were no messages matching the selection criteria for this get operation within the number of milliseconds that the operation was configured to wait. This can be a normal occurrence. |
| TIBCO-BW-PALETTE-MQ-500218 | Index type error | Check that the queue is indexed. It is not possible to filter a get unless the queue manager is maintaining indexes for the filter fields. Note that z/OS queue managers do not automatically index queues where other platforms do. |
| TIBCO-BW-PALETTE-MQ-500219 | Activity cancelled | The MqListener eventsource is stopped while processing a message; the message is backed out. |
| TIBCO-BW-PALETTE-MQ-500220 | Message received on a cancelled listener; sent to dead letter queue: [{0}] | The MqListener eventsource was stopped but because the IBM MQ get API call is not interruptable it subsequently received a message which has been transferred to the dead letter queue. This can be avoided by turning on explicit commits. |
| TIBCO-BW-PALETTE-MQ-500221 | Message received on a cancelled listener but there is no dead letter queue; messageId [{0}] lost. | The MqListener eventsource was stopped but because the IBM MQ get API call is not interruptable it subsequently received a message. There is no dead letter queue so the message has been discarded. |
| TIBCO-BW-PALETTE-MQ-500222 | IO Error in MQ; [{0}] | There has been an error reading or writing the contents of a message. Ensure that the message body is described correctly by its schemas (if any), and that all encodings are correct. |
| TIBCO-BW-PALETTE-MQ-500223 | Invalid application properties item: [{0}] Message: [{1}] | An application properties item of an unsupported type was provided. Use a supported type for the property. |
| TIBCO-BW-PALETTE-MQ-500224 | Invalid dynamic properties item: [{0}] Message: [{1}] | A dynamic property item of an unsupported type or content was provided. Use a supported type for the property. |
| TIBCO-BW-PALETTE-MQ-500225 | Failed to open poison message error queue [{0}:{1}] | The error queue defined for poison message handling could not be opened. Provide an accessible queue for poison messages. |
| TIBCO-BW-PALETTE-MQ-500226 | Failed to put a poison message to the configured error queue [{0}:{1}] | Ensure that the application has access to the queue and can put messages on it. |
| TIBCO-BW-PALETTE-MQ-500227 | A poison message ID [{0}] was detected and copied to the error queue [{1}] | Ensure that the application has access to the queue and can put messages on it. |
| TIBCO-BW-PALETTE-MQ-500230 | Message put error; DecodedMessage [{0}] CompCode [{1}] ReasonCode [{2}] ErrorCode [{3}] | Examine the provided message and codes to determine the source of the put error. Contact support if no resolution is reached. |
| TIBCO-BW-PALETTE-MQ-500231 | Local transaction commit failed | The queue manager failed to commit a unit of work which was associated with a local transaction. This failure occurred on the first (possibly only) queue manager involved so all resources is backed out. |
| TIBCO-BW-PALETTE-MQ-500232 | Local transaction commit for queue manager [{0}] failed after [{1}] succeeded; queues are in an inconsistent state | The queue manager failed to commit a unit of work which was associated with a local transaction. Multiple queue managers were involved and at least one other queue manager has committed messages as part of this failed transaction. It is not supported to enlist multiple queue managers in a local transaction. |
| TIBCO-BW-PALETTE-MQ-500233 | Failed to confirm or release an MQ ProcessStarter activity [{0}]. This error can occur after recovering from a check-pointed BusinessWorks process instance. | A confirm activity has attempted to confirm a message after an activity resume (from checkpoint) but the connection is lost. The message is backed out and the process must be restarted. |
| TIBCO-BW-PALETTE-MQ-500234 | Process started encountered an unexpected error:[{0}] | Internal error. Contact support. |
| TIBCO-BW-PALETTE-MQ-500235 | Failed to close the destination object associated with this process | An error was encountered closing a destination. This is not normally a serious problem but should be investigated if it occurs repeatedly. |
| TIBCO-BW-PALETTE-MQ-500236 | Configuration error; Dynamic ReplyTo Model not provided | A model queue was not provided for a temporary replyto destination. |
| TIBCO-BW-PALETTE-MQ-500237 | Error processing password: [{0}] | There is a problem decoding the password, check that it is correctly specified on the connection resource. |
| TIBCO-BW-PALETTE-MQ-500250 | Error processing message body field [{0}] - [{1}] | The message body schema for this message does not match the contents of the message in type or length. The field in error is indicated. |
| TIBCO-BW-PALETTE-MQ-500251 | Inquire error; Unknown queue type [{0}] returned | This is an internal error. It is appropriate to open a support issue for this error. |
| TIBCO-BW-PALETTE-MQ-500252 | Inquire error; Unknown sharability type [{0}] returned | This is an internal error; contact support. |
| TIBCO-BW-PALETTE-MQ-500253 | Inquire error; Destination type [{0}] provided | Destination type must be queue |
| TIBCO-BW-PALETTE-MQ-500254 | Inquire error; Reason [{0}] CompCode [{1}] ReasonCode [{2}] ErrorCode [{3}] | Examine the provided reason and codes to determine the source of the inquire error. The codes are described in IBM's IBM MQ documentation. |
| TIBCO-BW-PALETTE-MQ-500255 | Connection pool is exhausted, size is [{0}] | Increase the pool size |
| TIBCO-BW-PALETTE-MQ-500256 | Browse timed out | There were no messages matching the selection criteria for this browse operation within the number of milliseconds that the operation was configured to wait. This can be a normal occurrence. |
| TIBCO-BW-PALETTE-MQ-500257 | Error reported by the CICS bridge: [{0}] | Examine the error message and resolve the problem related to the host program execution. |
| TIBCO-BW-PALETTE-MQ-500257 | IBM MQ client API version info: [{0}] | Information only, no resolution required. |
| TIBCO-BW-PALETTE-MQ-500258 | IBM MQ BusinessWorks plug-in version info: [{0}] | Information only, no resolution required. |
Copyright © Cloud Software Group, Inc. All rights reserved.