WEBM Messages

Explanation:	The Integration Service could not connect to the webMethods Broker.
User Response:	See the additional error message for more information.

WEBM_1002 Failed to reconnect to the webMethods Broker.

Explanation:	The Integration Service could not reconnect to the webMethods Broker.
User Response:	See the additional error message for more information.

WEBM_1003 Failed to disconnect from the webMethods Broker.

Explanation:	The Integration Service could not disconnect from the webMethods Broker.
User Response:	See the additional error message for more information.

WEBM_1004 Preserve Client State option is set, but no client ID is given in application connection <application connection name>.

Explanation:	In the specified webMethods application connection, you selected the Preserve Client State option. However, you did not specify a client ID.
User Response:	Set a value for the client ID if you select the Preserve Client State option.

WEBM_1006 Exception from the Broker: <webMethods Broker name>.

Explanation:	The Integration Service encountered an error from the webMethods Broker.
User Response:	See the webMethods error message for more information.

WEBM_2001 Failed to get a document from the webMethods Broker.

Explanation:	The Integration Service could not read a webMethods document.
User Response:	See the additional error message for more information.

WEBM_2002 Failed to acknowledge a document to the webMethods Broker.

Explanation:	The Integration Service could not acknowledge a document it read from the source.
User Response:	See the additional error message for more information.

WEBM_2003 Failed to process a received document.

Explanation:	The Integration Service could not process a document it read from the source.
User Response:	See the additional error message for more information.

WEBM_2004 Client Group does not have the permission to subscribe to document type <document type>.

Explanation:	The Integration Service could not read a webMethods document from the source. The document belongs to a document type the client group specified in the webMethods application connection does not have permission to subscribe to.
User Response:	If you want to receive webMethods documents of this document type, configure the webMethods client to allow the client group to receive documents of this type.

WEBM_2005 Source <source name> is configured to receive messages, but no client ID is given in application connection <application connection name>.

Explanation:	This is a warning message. You configured the session to receive documents in deliver/receive mode. However, the application connection for the webMethods source definition in the session properties does not contain a client ID.
User Response:	You can configure a value for client ID in the webMethods application connection properties.

WEBM_2010 Reader received and rejected a document with a mismatched document type <document type>: <document>.

Explanation:	The Integration Service read a document that does not match the document type in the source definition. The document is rejected.
User Response:	None.

WEBM_2011 Failed to store a document in the recovery cache: <error message>.

Explanation:	The Integration Service could not store a document it read from the source in the recovery cache.
User Response:	See the additional error message for more information.

WEBM_2012 Failed to retrieve a document from the recovery cache: <error message>.

Explanation:	During a recovery session, the Integration Service could not read a document from the recovery cache.
User Response:	See the additional error message for more information.

WEBM_2013 The data retrieved from the recovery cache is not a valid webMethods document.

Explanation:	During a recovery session, the Integration Service read data from the recovery cache that is not a webMethods document. The recovery cache may have been modified. As a result, the recovery session failed.
User Response:	Rerun the session.

WEBM_2014 Failed to create a recovery cache to store documents: <error message>.

Explanation:	The Integration Service could not create a recovery cache.
User Response:	See the additional error message for more information.

WEBM_2015 Failed to open a recovery cache to recover documents: <error message>.

Explanation:	During a recovery session, the Integration Service could not open the recovery cache.
User Response:	See the additional error message for more information.

WEBM_2016 There is no cache folder specified for recovery.

Explanation:	The session is configured for recovery, but the recovery cache folder is not specified.
User Response:	Specify a value for the recovery cache folder in the session properties.

WEBM_2017 Failed to initialize the cache folder <recovery cache> for recovery.

Explanation:	The session is configured for recovery, but the specified recovery cache folder does not exist. The Integration Service could not initialize the session.
User Response:	Create the directory for the recovery cache folder.

WEBM_3001 Failed to process a row of data.

Explanation:	The Integration Service could not process a webMethods document.
User Response:	See the additional error message for more information.

WEBM_3002 Invalid data <data> for field <field name>.

Explanation:	The data in the specified field does not match the datatype for the field. For example, the data for the field is string, but the field is of datatype Boolean.
User Response:	Make sure the data for the field matches the datatype of the field.

WEBM_3003 Data conversion error for field <field name>.

Explanation:	The Integration Service could not convert the data for the specified field. For example, the field is of datatype integer, but the data for the field is out of range.
User Response:	Make sure the data for the field uses the proper range and precision.

WEBM_3005 Client Group does not have the permission to publish document type <document type>.

Explanation:	The Integration Service tried to write documents to the target of the specified document type. However, the client group specified in the webMethods application connection for the target does not have permission to publish documents of this type.
User Response:	If you want to publish webMethods documents of this document type, configure the webMethods client to allow the client group to publish documents of this type.