Messages are logged with message class 0800. In the Administrator, section
you find the logging settings in the tree for Adapters. See the webMethods Integration Server Administrator's Guide for changing the logging settings.The messages have the format:
0800nnnn
where | 0800 | is the message class, and |
nnnn | is the message number in the range 0000 - 9999 |
08000212 | 08000213 | 08000219 | 08000220 | 08000221 | 08000229 | 08000246 | 08000300 | 08000310 | 08000333 | 08000401 | 08000402 | 08000403 | 08000404 | 08000420 | 08000421 | 08000422 | 08000423 | 08000424 | 08000441 | 08000442 | 08000443
08000212 | WmEntireX: exception during register: <exception detail> |
Explanation |
An error occurred during |
Action |
Use exception detail to fix. This is typically a configuration issue. |
08000213 | WmEntireX: exception during receive: <exception detail> |
Explanation |
An error occurred during |
Action |
Use exception detail to fix. |
08000219 | WmEntireX: connection.receive: unknown server command <actual command> |
Explanation |
<actual command> was send to the adapter listener. This is unknown and cannot be handled. |
Action |
Change command. The only known command is
|
08000220 | WmEntireX: connection.receive: conversational call <actual packet type> rejected |
Explanation |
The adapter listener does not support conversational RPC. |
Action |
Use non-conversational calls. |
08000221 | WmEntireX: connection.receive: illegal packet type <actual packet type> |
Explanation |
The adapter listener received an illegal packet type. |
Action |
Change your RPC client to send valid packet types. |
08000229 | WmEntireX: unsupported RPC protocol version: <actual protocol version> |
Explanation |
The RPC client is sending an old protocol version that is not supported by the adapter listener. |
Action |
Update your RPC client. |
08000246 | WmEntireX: Some programs not found in COBOL metadata, expected library: <library name>, actual: <actual library name>, programs not found: <expected program names> |
Explanation |
The COBOL metadata of the connection is not consistent. |
Action |
Regenerate your connection and the adapter services. |
08000300 | WmEntireX: exception during processing notification result: <exception details> |
Explanation |
The adapter listener trapped into an exception while processing the result of the notification execution. |
Action |
Use exception details to fix. |
08000310 | WmEntireX: listener.processNotificationResults error: <error details> |
Explanation |
The Integration Server runtime reported an error during notification. |
Action |
Use error details to fix. |
08000333 | WmEntireX: exception during syncListener.runNotification: <exception details> |
Explanation |
The adapter listener trapped into an exception while processing a notification event. |
Action |
Use exception details to fix. |
08000401 | WmEntireX: no program info for <program name> found in metadata info |
Explanation |
The metadata for this connection does not contain necessary info for this program. |
Action |
Re-create this connection. |
08000402 | WmEntireX: illegal program info for <program name> found in metadata info, length=<number of info blocks for the program> |
Explanation |
The metadata for this connection does not contain consistent info for this program. |
Action |
Re-create this connection. |
08000403 | WmEntireX: illegal program info for <program name> found in metadata info, length(headerInfos)=<number of info blocks for the program header> |
Explanation |
The metadata for this connection does not contain consistent info for this program. |
Action |
Re-create this connection. |
08000404 | WmEntireX: exception while processing metadata info: <exception details> |
Explanation |
The metadata for this connection does not contain consistent info for this program. |
Action |
Re-create this connection. |
08000420 | WmEntireX: exception while reading metadata info: <exception details> |
Explanation |
The metadata for this connection is not readable. |
Action |
Re-create this connection. Use exception details to fix. |
08000421 | WmEntireX: metadata info cannot be empty |
Explanation |
The metadata for this connection is empty. |
Action |
Re-create this connection. |
08000422 | WmEntireX: no library name found in metadata info |
Explanation |
The metadata for this connection does not contain an IDL library name. |
Action |
Re-create this connection. |
08000423 | WmEntireX: no programs found in metadata info |
Explanation |
The metadata for this connection does not contain an IDL program name. |
Action |
Re-create this connection. |
08000424 | WmEntireX: no information found for program <program name> |
Explanation |
The metadata for this connection does not contain the signature information for <program name>. |
Action |
Re-create this connection. |
08000441 | Illegal value of type <actual type>, <expected type> expected |
Explanation |
The actual parameter type provided by the Integration Server differs from the expected parameter type. The types are incompatible. |
Action |
Supply parameters of expected type. |
08000442 | Illegal value <actual value> for type <actual IDL data type> |
Explanation |
The actual parameter value provided by the Integration Server does not match the expected parameter type. |
Action |
Use exception details to fix this. |
08000443 | Illegal type <actual type> for <parameter name> |
Explanation |
The parameter has an unknown IDL type. |
Action |
Contact Software AG support. |