IBM E02HRLL-G - WebSphere Partner Gateway Express, Administration Manual

Page: 195 / 268

Appendix B - failed events
When a document fails processing, the WebSphere Partner Gateway system
generates an event. See Table 43 for a list of WebSphere Partner Gateway failed
events and their corresponding descriptions. See Table 44 on page 200 for a list of
events that can be generated by the EDI components.
Note: The HTTP Receiver component will return an HTTP error code if it is
unable to persist the document. For all other Receiver component types, the
document content will be persisted at its current location at the time of failure.
Table 43. Failed events
Event code Event name Internal description Severity Extended description
BCG103001 Database Failure Database Error: {0} failed in
{1} with exception {3} Critical
BCG103101 Cache Engine Error Cache Engine instanceId {0}
on host {1} failed to
initialized, please correct
the problem and restart the
service, error reason:{2} Critical
BCG103201 Hub Owner State
Engine Error Error Reason:{0} Error This event is generated when
a unrecoverable system occurs
causing a document to fail
processing. An example can
be a database write error.
BCG103203 Receiver Processing
Error Receiver ’{0},{1}’ failed to
processing document, error:
{2}. Error This event is generated when
the receiver component is
unable to process a document
because of document or
system errors.
BCG103205 Receiver Error Receiver ’{0},{1}’ failed to
process receiver: {2}. Error
BCG106004 No Default
Destination Pair Connection create failed. A
pair of default destinations
does not exist between
partners: {0} and {1} Error
BCG106005 No Action Found A connection could not be
created for the B2B
capability because no
actions are associated with
the interaction. Error
BCG106600 Document Definition
Create Error Child level = {0} greater
than or equal to parent
level = {1} Error
© Copyright IBM Corp. 2007, 2008
189