3 B2B-50006 to B2B-53104

B2B-50006: Exception Received

Cause: B2B received an exception message from the trading partner.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50007: Notification of failure received

Cause: B2B received a notification of failure - out of band exception from trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50008: Document level retry count is exhausted.

Cause: Maximum number of document level retries has been reached.

Action: Increase the maximum number of document level retries

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50009: Failed to Send

Cause: B2B cannot send message to the trading partner

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50010: Trading partner agreement identification error

Cause: B2B cannot identify an agreement using the current details

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50011: Message Correlation Error

Cause: B2B cannot correlate the message

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50012: Pack/Unpack Error

Cause: Error in packaging

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50013: Security Error

Cause: Error in security validation

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50014: General Error

Cause: Internal error in engine

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50015: In-band notification error

Cause: Internal engine error

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50021: User request to set error for all pending batch messages with same batch id [{0}]. The Message IDs are {1}

Cause: User request to set error for all pending batch messages with same batch id [{0}].

Action: User request to set error for all pending batch messages with same batch id [{0}]. This error is expected, hence no action is necessary

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50025: Repository error

Cause: Error accessing metadata repository

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50026: Repository error

Cause: Error accessing stream data store

Action: Review the diagnostic log to verify the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50027: Failed to write data into output stream.

Cause: Failed to write data into output stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50028: Failed to read data from input stream.

Cause: Failed to read data from input stream.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50029: B2B runtime error

Cause: A runtime error has occurred.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50030: B2B Negative Ack Received

Cause: B2B has received a negative acknowledgement

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50031: B2B general error

Cause: A general error has occurred

Action: Review the UI report for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50032: B2B exchange protocol negative acknowledge received

Cause: Received a negative exchange acknowledge message.

Action: Review the negative exchange acknowledge message to determine the cause, or check with the trading partner.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50033: B2B functional acknowledgment processing error

Cause: An error occurred during functional acknowledgment processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50034: B2B negative functional acknowledgment

Cause: A negative functional acknowledgment is received.

Action: Review the negative functional acknowledge message to determine the cause or check with the trading partner.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50035: B2B exception message processing error

Cause: An error occurred during exception message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50036: B2B trading partner agreement identification error

Cause: An error had occurred during identify trading partner agreement.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50037: B2B inbound message processing error

Cause: An error occurred during incoming message processing.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50038: B2B outbound app message input {0} header processing error

Cause: An error occurred during outbound {0} input processing.

Action: Review the input properties sent for outbound message processing. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50039: Negative Interchange acknowledgment received

Cause: A negative Interchange acknowledgment is received.

Action: Review the negative Interchange acknowledge message to determine the cause or check with the trading partner.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50040: Unable to correlate the received Functional Ack

Cause: A Functional Ack received for unknown message.

Action: Review the control number of the incoming message

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50041: TopLink server session initialization error

Cause: An error occurred during TopLink server session initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50042: B2B trace context initialization error

Cause: An error occurred during trace context initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50043: Functional acknowledgement received for errored business message with id {0}

Cause: Functional acknowledgement received for errored business message.

Action: Review the control number of the original business in the incoming FA payload.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50044: Exception Message Received from backend

Cause: An Exception Message Received from backend.

Action: Review the payload from the Exception message.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50050: Engine initialization error.

Cause: An error occurred during engine initialization.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50051: Failed to shut down the B2B engine.

Cause: An error occurred during engine shut down.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. If the problem persists, contact Oracle Support Services

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50052: Engine already initialized.

Cause: Attempt made to initialize B2B engine which has been initialized already.

Action: Ensure that the engine is stopped before attempting to initialize

Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50059: Error in starting B2B Server.

Cause: An error has occurred while starting the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-50060: Error in stopping B2B Server

Cause: An error has occurred while stopping the server.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50075: Error loading document or exchange plug-in.

Cause: Error loading document or exchange plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50076: Error loading packaging plug-in.

Cause: Error loading packaging plug-in.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50077: Cannot Initialize Transport.

Cause: Cannot Initialize Transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50078: Cannot shut down transport.

Cause: Cannot shut down transport.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50079: Transport error

Cause: An error has occurred in transport layer

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50080: Exchange protocol identification error.

Cause: Failed to identify the exchange protocol of the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50081: Duplicate exchange protocol message error

Cause: Duplicate exchange protocol message generated by the trading partner.

Action: Report this error to the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-50082: Duplicated Control Number error

Cause: Message received with duplicate control number {0}.

Action: Report this error to the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-50083: Document protocol identification error.

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50084: No service found

Cause: Requested service was not registered in system

Action: Check requested web service URL

Level: 1

Type: ERROR

Impact: Process

B2B-50085: Duplicated transaction number error for xpath {0} with value {1}. The message id : {2}

Cause: Message received with duplicate transaction number error for xpath {0} with value {1}. The message id : {2}

Action: Check the xpath value of the message

Level: 1

Type: ERROR

Impact: Process

B2B-50086: Error during the identification of Group segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50087: Error during the identification of Interchange segment in payload. {0}

Cause: Failed to identify the document protocol for the message.

Action: Check the group segment in the payload.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50545: An agreement {0} has expired or is not in force as yet. The effective From/To dates are {1} - {2}.

Cause: An agreement effective From/To dates are invalid.

Action: Change the agreement effective From/To dates.

Level: 1

Type: ERROR

Impact: Process

B2B-50546: Information given to identify an agreement is insufficient: FromTP {0}, ToTP {1}, document type {2}.

Cause: Failed to identify the agreement

Action: Make sure From/To TP and document information is not Null.

Level: 1

Type: ERROR

Impact: Process

B2B-50547: Agreement not found for trading partners: FromTP {0}, ToTP {1} with document type {2}.

Cause: Failed to identify the trading partner agreement from the given input values.

Action: Make sure there is an agreement configured for the From/To trading partner and document information that presents in the message.

Level: 1

Type: ERROR

Impact: Process

B2B-50548: Agreement {0} not in active state.

Cause: Agreement was not in active state.

Action: Make sure the agreement is deployed and it is in Active state.

Level: 1

Type: ERROR

Impact: Process

B2B-50549: Cannot uniquely identify the trading partner. The trading partners {0} have the same set of identifications.

Cause: The trading partners {0} have the same set of identifications

Action: Make sure the trading partners have unique identifications

Level: 1

Type: ERROR

Impact: Process

B2B-50550: Cannot find the trading partner for the given identification type {0} and value {1}

Cause: The trading partner was not exist for the given identification type and value.

Action: Create or update the trading partner with the given identification type and value.

Level: 1

Type: ERROR

Impact: Process

B2B-50601: Agreement found but the certificate used for client authentication may not represent the Trading Partner {0} whom it claims to be.

Cause: Certificate used for client authentication may not belong to the Trading Partner.

Action: Please make sure Trading partner alias has been configured correctly against Security Identifier. If it is not, then it is a serious security error, please consult your security administrator for further course of action.

Level: 1

Type: ERROR

Impact: Process

B2B-50602: Keystore not available to validate the incoming certificate over SSL.

Cause: Keystore may not be properly configured in B2B to validate the incoming SSL client certificate.

Action: Please make sure keystore has been configured correctly in B2B.

Level: 1

Type: ERROR

Impact: Process

B2B-50603: Agreement found but authenticated principal(user) over http do not represent the Trading Partner {0} whom it claims to be.

Cause: Authenticated user may not represent the Trading Partner.

Action: Please make sure the Security Identifier configuration in B2B against the Trading Partner is correct. If the value is correct, then it is serious security error, please consult your security administrator for further course of action.

Level: 1

Type: ERROR

Impact: Process

B2B-50651: Agreement not found for trading partners: FromTP {0}, ToTP {1} with {2}.

Cause: Failed to match the service, action, servicetype for the trading partner agreement from the message.

Action: Make sure there is an agreement that contains a matching service, action, servicetype in the CPA configured for the From/To, service,action, servicetype information that is present in the message.

Level: 1

Type: ERROR

Impact: Process

B2B-50701: The agreement {0} cannot be activated because a similar agreement {1} found in active state

Cause: Similar agreement found in active state. There cannot be two agreements with the same trading partners, document type, version, and direction.

Action: Make inactive existing active agreement which has the same trading partners, document type, version, and direction.

Level: 1

Type: ERROR

Impact: Process

B2B-50702: {0} does not exist in the repository.

Cause: {0} does not exist in the repository.

Action: Channel/TPName does not exist in the repository. Get the latest list of channels.

Level: 1

Type: ERROR

Impact: Process

B2B-50703: Endpoint {0} does not exist in the group.

Cause: Endpoint {0} does not exist in the group.

Action: Endpoint does not exist in the group. Get the latest list of endpoints.

Level: 1

Type: ERROR

Impact: Process

B2B-50704: Group {0} does not exist in the repository.

Cause: Group {0} does not exist in the repository.

Action: Group does not exist in the repository. Get the latest list of group.

Level: 1

Type: ERROR

Impact: Process

B2B-50705: Duplicate Endpoint {0}.

Cause: Endpoint {0} already exist in the repository

Action: Endpoint already exist in the repository.Can not create same name endpoint

Level: 1

Type: ERROR

Impact: Process

B2B-50706: No callout for internal delivery channel.

Cause: Callout can not be set for internal delivery channel.

Action: Remove callout from internal delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-50707: Endpoint Validation Error

Cause: Endpoint validation error.

Action: Endpoint validation error.Check the diagnostic log for more details.

Level: 1

Type: ERROR

Impact: Process

B2B-50708: Mandatory parameter value missing.

Cause: Mandatory Parameter can not be null.

Action: Provide the mandatory parameter value.

Level: 1

Type: ERROR

Impact: Process

B2B-50709: Endpoint Disablement Failed.

Cause: Endpoint can not disabled

Action: Endpoint Disablement Failed. Check the diagnostic log.

Level: 1

Type: ERROR

Impact: Process

B2B-50710: Document Protocol {0} does not supported

Cause: Document Protocol {0} not supported.

Action: Document Protocol does not supported.

Level: 1

Type: ERROR

Impact: Process

B2B-50711: Document definition {0} not exists

Cause: Document definition {0} does not exists.

Action: Document definition does not exists.

Level: 1

Type: ERROR

Impact: Process

B2B-50712: Error in removing document.

Cause: Error while removing document from endpoint.

Action: There is error while removing document from endpoint. Check the diagnostic log.

Level: 1

Type: ERROR

Impact: Process

B2B-50713: Internal Delivery Channel is used in endpoint document

Cause: Internal Delivery Channel is used in endpoint document

Action: Internal Delivery Channel is used in endpoint document. Check the diagnostic log.

Level: 1

Type: ERROR

Impact: Process

B2B-50714: IDREF_KEY Missing.

Cause: IDREF_KEY Missing in configuration.

Action: IDREF_KEY Missing in configuration. Check the diagnostic log.

Level: 1

Type: ERROR

Impact: Process

B2B-50715: No document attached to endpoint

Cause: There is no document attached to endpoint.

Action: There is no document attached to endpoint.There should be at least one document attached to enable the endpoint.Check the diagnostic log.

Level: 1

Type: ERROR

Impact: Process

B2B-50716: FTP Sequencing Parameters missing

Cause: timestamp_format,timestamp_offset,timestamp_source values are must for FTP if Sequencing is enabled

Action: Provide timestamp_format,timestamp_offset,timestamp_source values for FTP endpoint.

Level: 1

Type: ERROR

Impact: Process

B2B-50717: Block characters missing

Cause: Block characters parameters values are missing.

Action: Provide the Block characters parameters.

Level: 1

Type: ERROR

Impact: Process

B2B-50718: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Cause: Channel is associated with {0} TradingPartner(s) and associated TradingPartner(s) are {1}

Action: Make sure channel is not associated with any TradingPartner(s).

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50741: WS-HTTP transport protocol must have WSDL Artifacts.

Cause: WS-HTTP transport protocol did not have WSDL Artifacts.

Action: make sure WS-HTTP transport protocol has WSDL Artifacts.

Level: 1

Type: ERROR

Impact: Process

B2B-50742: Service parameter are not well formed in WS-HTTP channel.

Cause: service parameter did not have namespace encloses with curly braces in WS-HTTP Channel.

Action: Make sure service parameter has namespace encloses with curly braces in WS-HTTP channel.

Level: 1

Type: ERROR

Impact: Process

B2B-50743: Invalid Payload received for Sync Request from Backend. Payload is null

Cause: Either Back-end composite is a One-Way composite, or it is not configured properly to return a response.

Action: Make sure Composite is configured to send a response

Level: 1

Type: ERROR

Impact: Process

B2B-50744: Keystore details missing or invalid.

Cause: Keystore details have not been provided or are invalid.

Action: Provide Keystore details.If provided then check the validity of keystore location and password.

Level: 1

Type: ERROR

Impact: Process

B2B-50801: No input value is specified. At least one input value is needed: From/To trading partner or Document or Action

Cause: Missing input values

Action: Specify input values such as From/To trading partner or Document or Action

Level: 1

Type: ERROR

Impact: Process

B2B-50901: Failed to find a business message with B2BMessageId {0}.

Cause: Failed to find a business message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.

Level: 1

Type: ERROR

Impact: Process

B2B-50902: Failed to find a wire message with B2BMessageId {0}.

Cause: Failed to find a wire message with B2BMessageId.

Action: Review the UI report to verify that a message exists with B2BMessageId.

Level: 1

Type: ERROR

Impact: Process

B2B-50903: Message {0} retry count is zero.

Cause: The maximum number of message retries has been reached.

Action: Increase the maximum number of retries in delivery channel.

Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50904: ReferTo message not found.

Cause: The message ID specified in the header RefToMessageID not found.

Action: It is possible that the original message was purged. Try resubmitting the original message.

Level: 1

Type: ERROR

Impact: Process

B2B-50906: Failed to retrieve value for the given XPATH.

Cause: Error occurred while extracting XPATH value.

Action: Make sure XPATH in document definition is correct and applicable for the payload

Level: 1

Type: ERROR

Impact: Process

B2B-51000: General packaging Error

Cause: Packaging details were incorrect.

Action: Correct the packaging details in delivery channel.

Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-51001: Packaging fail

Cause: Packaging information were insufficient.

Action: Correct the packaging details in delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-51002: Unpacking fail

Cause: Packaging headers were incorrect.

Action: Correct the packaging details in delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-51003: Encoding failed

Cause: Encoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51004: Decoding failed

Cause: Decoding type was incorrect.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51005: Validating packaging metadata failed.

Cause: Packaging metadata was insufficient.

Action: Verify packaging metadata to pack the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51006: Invalid input parameter

Cause: Packaging input parameters were invalid.

Action: Verify the packaging parameters and packaging metadata.

Level: 1

Type: ERROR

Impact: Process

B2B-51007: Missing packaging metadata information.

Cause: Missing few packaging metadata.

Action: Verify the packaging metadata.

Level: 1

Type: ERROR

Impact: Process

B2B-51008: Circular dependency in packaging metadata.

Cause: Circular dependency found in packaging metadata.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51009: Missing one or more packaging elements in packaging metadata.

Cause: Missing one or more packaging elements in packaging metadata.

Action: Verify packaging metadata has packaging elements.

Level: 1

Type: ERROR

Impact: Process

B2B-51010: Missing composite packaging element in packaging metadata.

Cause: None of the composite packaging elements exist in the Multipart message.

Action: Make sure Multipart message has at least one composite packaging element.

Level: 1

Type: ERROR

Impact: Process

B2B-51011: Invalid packaging metadata.

Cause: Message has more than one simple part. Hence, failed to package the message.

Action: Verify MIME message has only one simple part.

Level: 1

Type: ERROR

Impact: Process

B2B-51012: Missing list of message components.

Cause: Missing list of message component in the message.

Action: Verify the message has list of component.

Level: 1

Type: ERROR

Impact: Process

B2B-51013: Missing one or more message components in the list of message components.

Cause: Protocol components did not have all the required components while packaging information.

Action: Verify the protocol components and set all the required components for packaging the information.

Level: 1

Type: ERROR

Impact: Process

B2B-51014: Missing data for message component.

Cause: Invalid data for message component.

Action: Verify message has component data.

Level: 1

Type: ERROR

Impact: Process

B2B-51015: Missing security information.

Cause: Invalid security information.

Action: Verify security information is exist in packaging.

Level: 1

Type: ERROR

Impact: Process

B2B-51016: Missing signature information.

Cause: Invalid digital signature information.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51017: Missing encryption information.

Cause: Required envelope information did not exist.

Action: Verify the required envelope information available in packaging.

Level: 1

Type: ERROR

Impact: Process

B2B-51018: Message is not digitally signed.

Cause: Message was not digitally signed.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51019: Message is not encrypted.

Cause: Message was not encrypted.

Action: Verify the message which has to be encrypted.

Level: 1

Type: ERROR

Impact: Process

B2B-51020: Signature protocol is not supported.

Cause: Signature protocol was not Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a signature protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-51021: Encryption protocol is not supported.

Cause: Encryption protocol was not a Secure Multipurpose Internet Mail Extensions (S/MIME).

Action: Use Secure Multipurpose Internet Mail Extensions (S/MIME) as a encryption protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-51022: Digest algorithm does not match.

Cause: Invalid digest algorithm.

Action: Verify digest algorithm.

Level: 1

Type: ERROR

Impact: Process

B2B-51023: Required signature information are already set for message.

Cause: Attempt made to set the signature information when it already has been set.

Action: Remove the existing signature information before attempting to set this new signature information.

Level: 1

Type: ERROR

Impact: Process

B2B-51024: Required envelope information is already set for message.

Cause: Attempt made to set envelope information when it has already been set.

Action: Remove the existing envelope information before attempting to set this new envelope information.

Level: 1

Type: ERROR

Impact: Process

B2B-51025: Keystore resource location incorrect

Cause: Incorrect keystore location specified.

Action: Specify correct keystore location.

Level: 1

Type: ERROR

Impact: Process

B2B-51026: Encoding type is not supported

Cause: Encoding type was not supported.

Action: Verify supported encoding type as any one of base64, quoted-printable, 7bit, 8bit, or binary.

Level: 1

Type: ERROR

Impact: Process

B2B-51050: MIME Content-Types do not match.

Cause: Mismatched MIME body part and MIME type.

Action: Verify the Content-Types in MIME body part.

Level: 1

Type: ERROR

Impact: Process

B2B-51051: MIME Content-Type parameter lists do not match.

Cause: While creating MIME body part, MIME Content-Type parameter lists mismatch.

Action: Verify the MIME Content-Type parameters list.

Level: 1

Type: ERROR

Impact: Process

B2B-51052: Invalid MIME Content-Type header or information.

Cause: Missing MIME Content-Type and value.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51053: Invalid MIME content disposition header or information.

Cause: Missing MIME content disposition header value.

Action: Verify MIME header content disposition.

Level: 1

Type: ERROR

Impact: Process

B2B-51054: Missing MIME Content-Type header information.

Cause: MIME Content-Type information was not exist.

Action: Verify MIME Content-Type header exist.

Level: 1

Type: ERROR

Impact: Process

B2B-51055: Missing information for message component.

Cause: Information were not exist for message component.

Action: Verify the message component information.

Level: 1

Type: ERROR

Impact: Process

B2B-51056: Missing or unable to read data from message.

Cause: Failed to read data from message.

Action: Verify the message data.

Level: 1

Type: ERROR

Impact: Process

B2B-51057: Invalid or corrupted message.

Cause: Invalid message format.

Action: Verify the message format.

Level: 1

Type: ERROR

Impact: Process

B2B-51075: Missing signer certificate.

Cause: Signer certificate not found.

Action: Provide the certificate to sign the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51076: Missing encryption certificate.

Cause: Encryption certificate not found.

Action: Provide the certificate to encrypt the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51077: Missing certificate chain.

Cause: Invalid certificate chain was exist.

Action: Provide the proper certificate with certificate chain.

Level: 1

Type: ERROR

Impact: Process

B2B-51078: Message has invalid digest information.

Cause: Failed to digest message or message corrupted.

Action: Provide appropriate digest for message.

Level: 1

Type: ERROR

Impact: Process

B2B-51079: S/MIME version is not supported.

Cause: Unsupported S/MIME version.

Action: Verify the S/MIME version should be either 2.0 or 3.0.

Level: 1

Type: ERROR

Impact: Process

B2B-51080: Signature algorithm {0} is not supported.

Cause: Unsupported signature algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51081: Digest algorithm {0} is not supported.

Cause: Unsupported digest algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process

B2B-51082: Encryption algorithm {0} is not supported.

Cause: Unsupported encryption algorithm specified.

Action: Review the UI report for the exact error, which begins with the string 'ERROR:' This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51083: General failure creating S/MIME digital signature.

Cause: A failure has occurred when creating the S/MIME digital signature.

Action: Verify that the keystore has the correct private key and certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51084: General failure verifying S/MIME digital signature.

Cause: A general failure has occurred when attempting to verify the S/MIME digital signature.

Action: 1. Use correct certificate to verify the signature. 2. Message might have been corrupted. Check with the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51085: General failure encrypting S/MIME message.

Cause: A general failure has occurred when attempting to encrypt the S/MIME digital signature.

Action: Use valid trading partner certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51086: General failure while decrypting S/MIME message.

Cause: General failure while decrypting S/MIME message.

Action: 1. Use correct Key Pair to decrypt the message. 2. Message might have been corrupted. Check with the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51087: Could not create digest data for S/MIME digital signature {0}.

Cause: Creating digest data for S/MIME digital signature failed {0}.

Action: Use the supported algorithm as per the S/MIME standard or as per the exchange protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-51088: Creating S/MIME digital signature failed {0}.

Cause: Failed to create S/MIME digital signature.

Action: Check the signing credentials.

Level: 1

Type: ERROR

Impact: Process

B2B-51089: Unable to verify S/MIME digital signature.

Cause: Verifying S/MIME digital signature failed {0}.

Action: Use correct certificate to verify the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51090: Unable to create S/MIME message recipient.

Cause: Creating S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51091: Unable to add a recipient to S/MIME message recipient list {0}.

Cause: Adding recipient to S/MIME message recipient list failed {0}.

Action: Check the recipient certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51092: Encrypting S/MIME message failed {0}.

Cause: Failed to encrypt S/MIME message.

Action: Check the certificate used to encrypt the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51093: Decrypting S/MIME message failed {0}.

Cause: Message encrypted using a wrong certificate.

Action: Check the key-pair used to decrypt the message or verify with the trading partner that the certificate used to encrypt the message is correct.

Level: 1

Type: ERROR

Impact: Process

B2B-51094: Processing signature information for S/MIME message failed.

Cause: Failed to Process signature information for S/MIME message.

Action: Request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51095: Processing envelope information for S/MIME message failed.

Cause: Failed to process envelope information for S/MIME message.

Action: Request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51096: Cannot include more than one signer in the S/MIME digital signature.

Cause: More than one signer in the S/MIME digital signature was not supported.

Action: Ask the trading partner to send the message with the single signer.

Level: 1

Type: ERROR

Impact: Process

B2B-51097: Found empty packaging IDs list during packaging plug-in initialization.

Cause: An empty packaging IDs list is passed for packaging plug-in initialization.

Action: Make sure correct packaging is mentioned.

Level: 1

Type: ERROR

Impact: Process

B2B-51098: Invalid Content-Type {0} in packaging metadata.

Cause: Packaging metadata contains invalid Content-Type.

Action: Make sure correct packaging details are mentioned.

Level: 1

Type: ERROR

Impact: Process

B2B-51099: An incorrect RosettaNet version has been found in the message.

Cause: Not a RosettaNet 1.1 message.

Action: Verify the packaging version.

Level: 1

Type: ERROR

Impact: Process

B2B-51105: Unsupported algorithm

Cause: Algorithm used was not supported by the S/MIME or exchange protocol.

Action: Use correct algorithm as specified by the exchange protocol or S/MIME standard.

Level: 1

Type: ERROR

Impact: Process

B2B-51107: Digest mismatch

Cause: Document might have been corrupted during transport.

Action: Request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51108: Failed to digest the message.

Cause: Failed to create the digest for the message.

Action: Check the payload or digest algorithm.

Level: 1

Type: ERROR

Impact: Process

B2B-51112: An invalid CRL has been found in the incoming message.

Cause: Invalid CRL.

Action: Check with the trading partner that CRL is correct and request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51114: CRL missing issuer

Cause: Issuer not found in CRL.

Action: Check with the trading partner that CRL issuer is correct and request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51120: Invalid Content-Type

Cause: Content-Type of the signed/encrypted message was not correct.

Action: Request a re-send from the partner or resend the message with correct Content-Type.

Level: 1

Type: ERROR

Impact: Process

B2B-51121: Empty recipient list

Cause: No recipient list was exist in the encrypted message.

Action: Check with the trading partner and request a re-send with recipient list.

Level: 1

Type: ERROR

Impact: Process

B2B-51122: Certificate decode error

Cause: Certificate was not correct.

Action: Check if the certificate is in correct format.

Level: 1

Type: ERROR

Impact: Process

B2B-51124: Failed to create certificate chain

Cause: Unable to create certificate chain while generating the message.

Action: Check if the certificate used is a trusted certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51125: No certificate to sign

Cause: Certificate used to sign the message was not available in the keystore.

Action: Check if the certificate is available in the keystore.

Level: 1

Type: ERROR

Impact: Process

B2B-51128: Certificate missing issuer

Cause: The certificate that is being used was missing issuer information.

Action: Use a trusted certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51143: Certificate expired

Cause: The certificate has expired.

Action: 1. Make sure host and trading partner has selected the local time zone, 2. If the time zone is correct request the trading partner to generate a new certificate.

Level: 1

Type: ERROR

Impact: Process

B2B-51145: Certificate is not valid yet.

Cause: Certificate was not valid. Because the certificate creation date was later than current system date.

Action: 1. Make sure Host and trading partner has selected the local time zone 2. System current date is later than certificate creation date.

Level: 1

Type: ERROR

Impact: Process

B2B-51147: Missing recipient information

Cause: Missed recipient information.

Action: Ask the trading partner to check the recipient certificate added during encryption and request for a re-send.

Level: 1

Type: ERROR

Impact: Process

B2B-51150: Failed to verify certificate chain.

Cause: Unable to verify the certificate chain while processing the message.

Action: Verify the certificates used and request a re-send.

Level: 1

Type: ERROR

Impact: Process

B2B-51152: CRL verification failed

Cause: CRL verification failed.

Action: CRL received not matching with the certificates in the keystore. Request the trading partner to send the correct CRL.

Level: 1

Type: ERROR

Impact: Process

B2B-51153: Certificate revoked

Cause: Certificate revoked.

Action: Request a re-send with the valid certificate from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51154: Certificate signature verification failed.

Cause: Failed to verify the certificate signature.

Action: Request for the valid certificate from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51165: Digest algorithm missing.

Cause: Message received with incorrect digest algorithm.

Action: Request a re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51193: Failed to open keystore.

Cause: Keystore file was not in correct format, incorrect location or incorrect password.

Action: Make sure the keystore is generated properly or the location or password is correct.

Level: 1

Type: ERROR

Impact: Process

B2B-51195: Failed to get key pair from keystore

Cause: Unable to retrieve key pair from the keystore.

Action: Verify that the keystore has valid key pair.

Level: 1

Type: ERROR

Impact: Process

B2B-51197: LDAP error

Cause: LDAP error

Action: Check the LDAP details.

Level: 1

Type: ERROR

Impact: Process

B2B-51198: LDAP connect failed.

Cause: LDAP connect failed.

Action: Check the LDAP details.

Level: 1

Type: ERROR

Impact: Process

B2B-51199: LDAP bind failed.

Cause: LDAP bind failed.

Action: Check the LDAP details.

Level: 1

Type: ERROR

Impact: Process

B2B-51200: LDAP search failed.

Cause: LDAP search failed.

Action: Check the LDAP details.

Level: 1

Type: ERROR

Impact: Process

B2B-51201: LDAP entry missing attribute.

Cause: LDAP entry missing attribute.

Action: Check the LDAP details.

Level: 1

Type: ERROR

Impact: Process

B2B-51202: No certificate in the directory for this user

Cause: Unable to retrieve the certificate for this user from the directory.

Action: Make sure that the certificate is available in the directory.

Level: 1

Type: ERROR

Impact: Process

B2B-51203: Error compressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload.

Level: 1

Type: ERROR

Impact: Process

B2B-51204: Error decompressing data.

Cause: An error has occurred while compressing data.

Action: Check the payload received or request for re-send from the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51205: The alias is not present or configured incorrectly in partner profile

Cause: The alias is not present or configured incorrectly in partner profile.

Action: Make sure that the alias is available in the partner profile.

Level: 1

Type: ERROR

Impact: Process

B2B-51206: Validation of signatures or checks on the authenticity or authority of the sender of the message have failed.

Cause: Alias is present but received message is unsigned

Action: Make sure received message is signed

Level: 1

Type: ERROR

Impact: Process

B2B-51207: Database Connection Failed.

Cause: Database Connection failed.

Action: Check the Datasource details.

Level: 1

Type: ERROR

Impact: Process

B2B-51208: SQL Exception occurred during JDBC processing

Cause: SQL Exception occurred during JDBC processing.

Action: Check the Datasource details.

Level: 1

Type: ERROR

Impact: Process

B2B-51300: Interface Sequencing failure - Inbound sequence row not present for correlation

Cause: Inbound sequence row not present for correlation.

Action: Check if the group count is configured incorrectly or if the sequence row was discarded.

Level: 1

Type: ERROR

Impact: Process

B2B-51500: Document exchange success.

Cause:

Action:

Level: 1

Type: NOTIFICATION

Impact: Process

B2B-51501: Document exchange initialization failure.

Cause: Failed to initialize the document specific guidelines.

Action: Verify the document specific initialization parameters.

Level: 1

Type: ERROR

Impact: Process

B2B-51503: General create message error.

Cause: Failed to create message components.

Action: Verify values for message creation components.

Level: 1

Type: ERROR

Impact: Process

B2B-51504: General decode error.

Cause: Failed to decode the message.

Action: Verify the incoming message contents.

Level: 1

Type: ERROR

Impact: Process

B2B-51505: General validation error.

Cause: An unexpected error occurred during validation.

Action: Verify the validity of the document against the document definition.

Level: 1

Type: ERROR

Impact: Process

B2B-51506: Message digest validation error.

Cause: Message digest obtained from the incoming message payload, did not match with the original message digest.

Action: Verify the digest algorithm.

Level: 1

Type: ERROR

Impact: Process

B2B-51507: Payload validation error.

Cause: An error occurred during message payload processing in document plug-in.

Action: Verify the message payload validity against the document definition.

Level: 1

Type: ERROR

Impact: Process

B2B-51508: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system. {0}

Cause: Validation of Group parameters failed. Verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in system.{0}

Action: Verify the EDI group header parameters of the message validity against the document definition.

Level: 1

Type: ERROR

Impact: Process

B2B-51509: Create message error: component- {0}.

Cause: Failed to create message components.

Action: Verify all components of the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51510: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of Batch header parameters failed. Verify all the Batch header parameters in the B2B configuration match the Batch header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify the batch message payload validity against the document definition.

Level: 1

Type: ERROR

Impact: Process

B2B-51511: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Interchange parameters in the message. Following parameters are not matching with the configured parameters in system.{0}

Action: Verify the EDI Interchange header parameters of the message validity against the document definition

Level: 1

Type: ERROR

Impact: Process

B2B-51512: Message payload parameter validation error.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.

Level: 1

Type: ERROR

Impact: Process

B2B-51513: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Cause: Validation of Interchange parameters failed. Verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid.

Action: Verify the EDI Interchange header parameters of the message validity against the document definition

Level: 1

Type: ERROR

Impact: Process

B2B-51514: Validation of Message header parameters failed. Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.

Cause: An error occurred in message header of document during message processing.

Action: Verify all the Message header parameters in the configuration match the Message header parameters in the message. Following parameters are not matching with the configured parameters.

Level: 1

Type: ERROR

Impact: Process

B2B-51515: Validation of parameters failed. Some or all of the following parameters do not match the configured parameters in B2B.

Cause: Document parameters validation failed.

Action: Verify the parameters of the message against the document protocol parameters.

Level: 1

Type: ERROR

Impact: Process

B2B-51516: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Cause: Validation of File header parameters failed. Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in system.

Action: Verify all the File header parameters in the B2B configuration match the File header parameters in the message. Following parameters are not matching with the configured parameters in B2B.

Level: 1

Type: ERROR

Impact: Process

B2B-51517: Document protocol identification error.{0}

Cause: Failed to identify the document protocol for the message.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51518: Mandatory parameter {0} {1} is missing.

Cause: Mandatory parameter {0} {1} is missing.

Action: Verify mandatory parameter is the same in payload and configuration.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51519: Interchange Receiver Id is not present.

Cause: Interchange Receiver Id is not present.

Action: Verify the Interchange Receiver Id is the same in payload and configuration.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-51520: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Cause: Validation of Interchange parameters failed. Following parameters are not matching with the configured parameters in B2B. {0}

Action: Verify the document Interchange parameters of the message validity against the document definition

Level: 1

Type: ERROR

Impact: Process

B2B-51521: Document Callout Translation error: {0}.

Cause: Error while using callout to translate document

Action: Check payload and read the parsing error

Level: 1

Type: ERROR

Impact: Process

B2B-51522: Translation is not enabled in the agreement. {0}

Cause: Translation is not enabled in the agreement. {0}

Action: Enable the translation in the associated agreement in the B2B console

Level: 1

Type: ERROR

Impact: Process

B2B-51550: Invalid usage code.

Cause: Specified usage code was neither production nor test.

Action: Verify that the usage code is either production or test.

Level: 1

Type: ERROR

Impact: Process

B2B-51551: Invalid timestamp.

Cause: Timestamp was not in the correct format.

Action: Correct timestamp format is CCYYMMDDThhmmss.sssZ.

Level: 1

Type: ERROR

Impact: Process

B2B-51552: Mismatch in the PIP binding ID.

Cause: PIP binding ID in the initiating message did not match the PIP binding ID in the response message.

Action: Ensure that the PIP binding ID in the initiating message matches the PIP binding ID in the response message.

Level: 1

Type: ERROR

Impact: Process

B2B-51553: Mismatch in PIP code.

Cause: PIP code in the initiating message did not match the PIP code in the response message.

Action: Ensure that PIP Code in the initiating message matches the PIP code in the response message.

Level: 1

Type: ERROR

Impact: Process

B2B-51554: Mismatch PIP in instance ID.

Cause: PIP instance ID in the initiating message did not match the PIP instance ID in the response message.

Action: Ensure that the PIP instance ID in the initiating message matches the PIP instance ID in the responding message.

Level: 1

Type: ERROR

Impact: Process

B2B-51555: Mismatch in PIP version.

Cause: PIP version in the initiating message did not match the PIP version in the response message.

Action: Ensure that PIP version in the initiating message matches the PIP version in the response message.

Level: 1

Type: ERROR

Impact: Process

B2B-51556: Invalid response message.

Cause: Message ID in the initiating message did not match the message ID in the RefTo field of the response message.

Action: Ensure that message ID in the initiating message matches the message ID in the RefTo field of the response message.

Level: 1

Type: ERROR

Impact: Process

B2B-51557: PIP binding ID exceeds 255 characters.

Cause: PIP binding ID cannot exceed 255 characters.

Action: Limit the total characters of PIP binding ID to 255.

Level: 1

Type: ERROR

Impact: Process

B2B-51558: Invalid value for secure transport required attribute.

Cause: Secure transport was neither Yes nor No.

Action: Ensure that the secure transport has values Yes or No.

Level: 1

Type: ERROR

Impact: Process

B2B-51559: Mismatch in manifest content-type.

Cause: Content-type in the manifest did not match the content-type associated with the attachment.

Action: Ensure that the content-type in the manifest and attachment are the same.

Level: 1

Type: ERROR

Impact: Process

B2B-51560: Mismatch in manifest content-ID.

Cause: Content-ID in the manifest did not match the content-ID associated with the attachment.

Action: Ensure that the content-ID in the manifest matches the content-ID associated with the attachment.

Level: 1

Type: ERROR

Impact: Process

B2B-51561: Mismatch in the service of the host and the trading partner.

Cause: FromService field in the initiating message did not match the ToService field in the response message.

Action: Verify the FromService field of the host matches with ToService field of the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51562: Mismatch in the service of the host and the trading partner.

Cause: ToService field in the initiating message did not match the FromService field in the response message.

Action: Verify the ToService field of the host matches with FromService of the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51563: Mismatch in the role of the host and the trading partner.

Cause: FromRole field in the initiating message did not match the ToRole field in the response message.

Action: Verify the FromRole field of the host matches with ToRole field of the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51564: Mismatch in the role of the host and the trading partner.

Cause: ToRole field in the initiating message did not match the FromRole field in the response message.

Action: Verify the ToRole field of the host matches with FromRole field of the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-51565: An unexpected error occurred while initializing the XML parser.

Cause: Failed to initialize XML parser.

Action: Ensure that the XML parser initialized properly.

Level: 1

Type: ERROR

Impact: Process

B2B-51566: Parse stream error

Cause: An unexpected error occurred while parsing the input stream.

Action: Verify the message components of incoming message.

Level: 1

Type: ERROR

Impact: Process

B2B-51567: Invalid Content-Type

Cause: Sub-type of the Content-Type in the HTTP header was neither Multipart/related nor Multipart/signed.

Action: Check for the Content-Type in the HTTP header.

Level: 1

Type: ERROR

Impact: Process

B2B-51568: encoding error

Cause: An unexpected error occurred while encoding data.

Action: Verify encoded type is base64.

Level: 1

Type: ERROR

Impact: Process

B2B-51569: decoding error

Cause: An unexpected error occurred while decoding data.

Action: Verify the decode type is base64.

Level: 1

Type: ERROR

Impact: Process

B2B-51570: Attachment error

Cause: An unexpected error occurred while creating an attachment as component data.

Action: Verify the well-form of the XML content for attachment.

Level: 1

Type: ERROR

Impact: Process

B2B-51571: Attachment error

Cause: An unexpected error occurred while forming an attachment as XML data.

Action: Verify that the XML format of the data for the attachment is well-formed XML. Also verify the encoding and type attributes of attachment.

Level: 1

Type: ERROR

Impact: Process

B2B-51572: Error reading input stream.

Cause: An unexpected error occurred while reading the input stream.

Action: Ensure the input value is nonempty.

Level: 1

Type: ERROR

Impact: Process

B2B-51573: Unexpected payload file naming, default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat

Cause: Payload file name was not as per expected naming convention.

Action: Expect default format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat.

Level: 1

Type: ERROR

Impact: Process

B2B-51574: Error loading XEngine libraries. XEngine is most likely not installed.

Cause: XEngine was not installed.

Action: Make sure XEngine is installed.

Level: 1

Type: ERROR

Impact: Process

B2B-51575: Incorrect document exchange version.

Cause: Document exchange version mismatch.

Action: Verify the document exchange header value.

Level: 1

Type: ERROR

Impact: Process

B2B-51576: Incorrect document exchange.

Cause: Document exchange mismatch.

Action: Verify the document exchange name.

Level: 1

Type: ERROR

Impact: Process

B2B-51577: Document exchange validation error

Cause: Document exchange validation failed.

Action: Verify the document exchange header values

Level: 1

Type: ERROR

Impact: Process

B2B-51578: Exception Reported: {0}

Cause: B2B is unable to continue processing due to Control Number sequence generation failure.

Action: Please refer to documentation for EM property : b2b.useSequenceControlNum for further information.

Level: 1

Type: ERROR

Impact: Process

B2B-51703: Failed to unpack the message.

Cause: An unexpected error occurred during the unpackaging of the RosettaNet business message.

Action: Verify the message headers.

Level: 1

Type: ERROR

Impact: Process

B2B-51705: Unable to read the preamble.

Cause: Failed to read preamble.

Action: Ensure the correctness of preamble content.

Level: 1

Type: ERROR

Impact: Process

B2B-51707: Unable to read the delivery header.

Cause: Failed to read delivery header.

Action: Ensure the correctness of the delivery header content.

Level: 1

Type: ERROR

Impact: Process

B2B-51709: Unable to read the service header.

Cause: Failed to read the service header.

Action: Ensure the correctness of the service header.

Level: 1

Type: ERROR

Impact: Process

B2B-51715: Failed to unpack the message - reading the service content.

Cause: Failed to read the service content.

Action: Ensure the correctness of the service content.

Level: 1

Type: ERROR

Impact: Process

B2B-51915: No type is specified in party ID.

Cause: No type was specified in party ID.

Action: Specify a party ID type.

Level: 1

Type: ERROR

Impact: Process

B2B-51916: Reference ID in the manifest does not match payload ID.

Cause: Reference ID in the manifest did not match payload ID.

Action: Make sure that reference ID in the manifest matches the payload ID.

Level: 1

Type: ERROR

Impact: Process

B2B-51917: Content-Type set for ebMS message is incorrect.

Cause: Content-Type set for ebMS message was incorrect.

Action: Set a valid Content-Type for the ebMS message.

Level: 1

Type: ERROR

Impact: Process

B2B-51918: This version of ebMS is not supported. Only version 2.0 is supported.

Cause: This version of ebMS was not supported. Only version 2.0 is supported.

Action: Make sure to exchange messages for the supported version.

Level: 1

Type: ERROR

Impact: Process

B2B-51919: Hub mode not supported.

Cause: As Hub mode was not supported, the actor value is incorrect.

Action: Specify the actor as urn:oasis:names:tc:ebXML-msg:actor:toPartyMSH

Level: 1

Type: ERROR

Impact: Process

B2B-51921: SOAP message has defective packaging.

Cause: Defect identified in packaging of the SOAP message.

Action: Make sure that the message is a valid SOAP message.

Level: 1

Type: ERROR

Impact: Process

B2B-51922: If the service type is not specified then the service must be a URI.

Cause: If the service type was not specified then the service must be a URI.

Action: Specify a service URI if the service type is not specified.

Level: 1

Type: ERROR

Impact: Process

B2B-51923: Value {0} for the element {1} is not recognized.

Cause: Failed to recognise value for the element.

Action: Specify a correct value for the element.

Level: 1

Type: ERROR

Impact: Process

B2B-51924: Message failed the security check.

Cause: Message failed the security check.

Action: Verify that the message has been encrypted and signed with the correct credentials.

Level: 1

Type: ERROR

Impact: Process

B2B-51925: Feature {0} is not supported.

Cause: Selected feature is not supported.

Action: Make sure the feature is currently supported.

Level: 1

Type: ERROR

Impact: Process

B2B-51926: SyncReply element must exist in the message.

Cause: SyncReply element must be present in the message.

Action: Add a SyncReply element in the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51927: Time to live has expired for the message.

Cause: Time to live has expired for the message.

Action: Make sure to send a message with a valid time to live value.

Level: 1

Type: ERROR

Impact: Process

B2B-51928: Message header validation failed. The received {0} does not match with the configured {1}.

Cause: Message header did not have the element.

Action: Make sure to add element to the message header.

Level: 1

Type: ERROR

Impact: Process

B2B-51929: No payload is found for the reference ID {0}.

Cause: No payload attached for the reference ID.

Action: Make sure to have a payload for the reference ID, or remove this reference ID from the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51930: Message with ID {0} is a duplicate message.

Cause: Duplicate message identified with same ID.

Action: Make sure to send a message with a unique message ID, a message which is not duplicated.

Level: 1

Type: ERROR

Impact: Process

B2B-51931: Error found in decrypting or verifying the message.

Cause: Error in decryption or on message verification.

Action: Make sure that the message is being decrypted and verified with the correct credentials.

Level: 1

Type: ERROR

Impact: Process

B2B-51932: Multiple parts with same Content-ID or Content-Location header.

Cause: Multiple parts with same Content-ID or Content-Location header.

Action: Use different Content-ID or Content-Location header values for different MIME parts of the message.

Level: 1

Type: ERROR

Impact: Process

B2B-51933: Referenced Content-ID or Content-Location header not found.

Cause: Referenced Content-ID or Content-Location header not found.

Action: Make sure that the referenced Content-ID or Content-Location header values are valid.

Level: 1

Type: ERROR

Impact: Process

B2B-51934: Unhandled attachment object {0} found.

Cause: Unhandled attachment object found.

Action: Make use of correct attachment type for attaching objects.

Level: 1

Type: ERROR

Impact: Process

B2B-51935: Error in resolving the content ID reference.

Cause: Failed to resolve the content ID reference.

Action: Make sure that the content ID reference is valid.

Level: 1

Type: ERROR

Impact: Process

B2B-51936: Signed acknowledgement requested, but not configured in delivery channel.

Cause: Signed acknowledgement requested, but not configured in delivery channel.

Action: Make sure that the sign acknowledgement is configured in delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-52250: Error decoding incoming message at MLLP exchange.

Cause: Message received consists of more than one part or component.

Action: Check the payload to make sure it has only one part/component.

Level: 1

Type: ERROR

Impact: Process

B2B-52251: Error identifying remote trading partner at MLLP exchange with MLLP ID {0}.

Cause: MLLP ID received from in the message header did not exist.

Action: Make sure that the MLLP ID of the remote trading partner is configured as in the trading partner identification section or the anonymous trading partner is configured.

Level: 1

Type: ERROR

Impact: Process

B2B-52252: Only one trading partner in the system can have hosted=true.

Cause: More than one trading partner has hosted=true.

Action: Make sure only one trading partner in the system has hosted=true.

Level: 1

Type: ERROR

Impact: Process

B2B-52253: Trading partner {0} must have trading partner name as one of the identification.

Cause: Trading partner must have trading partner name as one of the identification.

Action: Make sure trading partner has an identification with value as name of trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52254: Delivery channel {0} must have exchange protocol, if listening=false.

Cause: Delivery channel did not have exchange protocol.

Action: Make sure delivery channel has exchange protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-52255: Certificate alias not specified in the secure delivery channel {0}.

Cause: Security was enabled in delivery channel, but no certificate alias specified.

Action: Make sure certificate alias specified in the delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-52256: In delivery channel {0}, Transport protocol {1} is not supported by exchange protocol {2}.

Cause: Specified transport protocol was not supported by exchange protocol.

Action: Choose transport protocol which is supported by exchange protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-52257: In delivery channel {0}, algorithm {1} is not supported for exchange protocol {2}.

Cause: Specified algorithm was not supported by exchange protocol.

Action: Choose algorithm which is supported by exchange protocol.

Level: 1

Type: ERROR

Impact: Process

B2B-52258: In delivery channel {0}, exchange protocol parameter {1} is not supported for exchange protocol {2}.

Cause: Selected exchangeProtocolParameter was not part of the specified exchange protocol.

Action: Select specified exchangeProtocol and re-save again in UI.

Level: 1

Type: ERROR

Impact: Process

B2B-52259: In delivery channel {1}, exchange protocol {0} has to have acknowledge mode as ASYNC or NONE.

Cause: RNIF exchange protocol did not support SYNC acknowledge mode.

Action: Verify RNIF exchange protocol has acknowledge mode as ASYNC or NONE.

Level: 1

Type: ERROR

Impact: Process

B2B-52260: effectiveToDate {0} in agreement {1} must be a date in the future.

Cause: Date specified in effectiveToDate was not a future date.

Action: Ensure that the effectiveToDate in the agreement is a date in the future.

Level: 1

Type: ERROR

Impact: Process

B2B-52261: The effectiveFromDate {0} should be less than effectiveToDate {1} in agreement {2}.

Cause: The effectiveFromDate should be less than effectiveToDate.

Action: Make sure the effectiveFromDate is less than effectiveToDate.

Level: 1

Type: ERROR

Impact: Process

B2B-52262: Agreement {0} does not have a host and trading partner.

Cause: Agreement did not have a host and trading partner.

Action: Make sure agreement has a host and trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52263: One of the participants must be a host in an agreement {0}.

Cause: None of the participants was host in agreement.

Action: Make sure a participant in agreement is host.

Level: 1

Type: ERROR

Impact: Process

B2B-52264: Document type name {0} and document protocol version {1} used in agreement {2} are not in sync with the corresponding definition in trading partner {3}.

Cause: Document type name and document protocol version used in agreement were not in sync with the corresponding definition in trading partner.

Action: Make sure agreement has document type name and document type version as given in trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52265: DUNS identification value {0} must be 9 digit.

Cause: DUNS identification was not have value in 9 digit.

Action: Verify DUNS identification has value in 9 digit.

Level: 1

Type: ERROR

Impact: Process

B2B-52266: Identification type {0} and value {1} must be unique in the trading partner.

Cause: Identification type and value occurred more than once in the trading partner.

Action: Make sure type and value of identification unique in the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52267: Only one exchange protocol can have default=true.

Cause: More than one exchange protocol has default=true.

Action: Make sure only one exchange protocol has default=true.

Level: 1

Type: ERROR

Impact: Process

B2B-52268: Only one document protocol can have default=true.

Cause: More than one document protocol has default=true.

Action: Make sure only one document protocol has default=true.

Level: 1

Type: ERROR

Impact: Process

B2B-52269: Participant {0} cannot have more than one identification of the same type {1}.

Cause: Participant has more than one identification of the same type.

Action: Make sure participant is not referring to more than one identification of same type.

Level: 1

Type: ERROR

Impact: Process

B2B-52270: Participant {0} identification reference {1} is not part of same trading partner identification.

Cause: Participant refer to some other trading partner identification.

Action: Make sure identification referred in participant is part of same trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52271: Participant {0} delivery channel reference {1} is not part of same trading partner.

Cause: Participant delivery channel reference was not part of either same trading partner or host.

Action: Make sure delivery channel referred in participant is part of trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52272: Participant {0} document definition {1} is not part of same trading partner.

Cause: Participant document definition was not part of same trading partner.

Action: Make sure trading partner has specified document definition.

Level: 1

Type: ERROR

Impact: Process

B2B-52273: Participant {0} identification type {1} and value {2} are not synchronous with trading partner identification.

Cause: Participant identification type and value were not sync with trading partner identification.

Action: Make sure the value and type given in identification reference in participant is synchronous with trading partner identification.

Level: 1

Type: ERROR

Impact: Process

B2B-52274: Participant {0} can have only one exchange identifier.

Cause: Participant has more than one exchange identification.

Action: Make sure only one exchange identification found in participant.

Level: 1

Type: ERROR

Impact: Process

B2B-52275: Type of the parameter {0} must match with the default value {1}.

Cause: Parameter type and default value type mismatched.

Action: Check the type and value of parameter are same type.

Level: 1

Type: ERROR

Impact: Process

B2B-52276: Type of the parameter {0} must match with the value.

Cause: Parameter type and given value mismatched.

Action: Check the type and value of parameter are same type.

Level: 1

Type: ERROR

Impact: Process

B2B-52277: Only Custom document protocol can set custom attribute equal to true.

Cause: Other than custom document protocol has custom attribute set to true.

Action: Make sure only custom document protocol has this attribute set to true.

Level: 1

Type: ERROR

Impact: Process

B2B-52278: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID starts with doc_

Level: 1

Type: ERROR

Impact: Process

B2B-52279: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol reference is in the form of doc_id.xml

Level: 1

Type: ERROR

Impact: Process

B2B-52280: Trading partner {0} must have at least one exchange identification.

Cause: None of the exchange identification found in trading partner.

Action: Add at least one exchange identification in trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52281: Trading partner {0} must have ID {1} starts with tp_

Cause: Trading partner has ID which did not start with tp_

Action: Make sure trading partner has ID which starts with tp_

Level: 1

Type: ERROR

Impact: Process

B2B-52282: Trading partner {0} reference must be tp_id.xml

Cause: Trading partner reference was not in the form of tp_id.xml

Action: Make sure trading partner has reference in the form of tp_id.xml

Level: 1

Type: ERROR

Impact: Process

B2B-52283: In delivery channel {0}, certificate alias {1} not found in the keystore.

Cause: Given certificate alias did not exist in the keystore.

Action: Verify certificate alias is present in the keystore.

Level: 1

Type: ERROR

Impact: Process

B2B-52284: Delivery channel {0} which has transport protocol {1} cannot be a listening channel.

Cause: Selected transport protocol was not capable of listening

Action: Select listening transport to create listening delivery channel

Level: 1

Type: ERROR

Impact: Process

B2B-52285: Internal delivery channel {0} must use generic exchange.

Cause: Internal delivery channel has other than generic exchange protocol.

Action: Make sure internal delivery channel uses generic exchange.

Level: 1

Type: ERROR

Impact: Process

B2B-52286: HTTP transport protocol must have a URL.

Cause: HTTP transport protocol did not have a URL.

Action: Make sure HTTP transport protocol has a URL.

Level: 1

Type: ERROR

Impact: Process

B2B-52287: Agreement {0} must have ID {1} starts with tpa_

Cause: Agreement has ID which did not start with tpa_

Action: Make sure agreement has ID which starts with tpa_

Level: 1

Type: ERROR

Impact: Process

B2B-52288: Agreement {0} reference must be tpa_id.xml

Cause: Agreement reference was not in the form of tpa_id.xml

Action: Make sure agreement has reference which is in the form of tpa_id.xml

Level: 1

Type: ERROR

Impact: Process

B2B-52289: Agreement {0} has document definition with mismatching initiator flag.

Cause: Agreement has document definition with mismatching initiator flag in trading partner.

Action: Make sure document definition is supported to send or receive by trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52290: Agreement {0} must have exactly one supported document type.

Cause: Agreement has not exactly one supported document type.

Action: Make sure agreement has only one supported document type.

Level: 1

Type: ERROR

Impact: Process

B2B-52291: Duplicate agreement {0} found with same combination of trading partners {1}, {2}, and document type {3} and document protocol version {4}.

Cause: More than one agreement has same combination of trading partners, document type and version.

Action: Make sure only one agreement has same combination of trading partners, document type and version.

Level: 1

Type: ERROR

Impact: Process

B2B-52292: In agreement {0}, trading partner {1} must have a delivery channel.

Cause: The trading partner did not have delivery channel to send out bound message.

Action: Make sure in a agreement, the trading partner has a delivery channel to send out bound message.

Level: 1

Type: ERROR

Impact: Process

B2B-52293: In agreement {0}, the host {1} can refer to only the internal delivery channel.

Cause: Host refers to other than internal delivery channel.

Action: Make sure host is not referring to other than internal delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-52294: In agreement {0}, participant {1} cannot have more than one delivery channel.

Cause: Participant has more than one delivery channel.

Action: Make sure only one delivery channel exist for participant.

Level: 1

Type: ERROR

Impact: Process

B2B-52295: At least one name identification type present in system.

Cause: Name identification type did not present in system.

Action: Check at least one name identification type present in system.

Level: 1

Type: ERROR

Impact: Process

B2B-52296: Exchange identification {0} must have a value.

Cause: Exchange identification did not have a value.

Action: Make sure all exchange identification has a value.

Level: 1

Type: ERROR

Impact: Process

B2B-52297: Packaging protocol reference {0} must point to packaging protocol element.

Cause: Packaging protocol reference refer to other than packaging protocol element.

Action: Verify packaging protocol reference refers to packaging protocol element.

Level: 1

Type: ERROR

Impact: Process

B2B-52298: Transport URL {0} already used in system.

Cause: More than once same endpoint used in system.

Action: Make sure same endpoint not attached with different delivery channel in system.

Level: 1

Type: ERROR

Impact: Process

B2B-52299: Participant {0} must have at least one exchange identification.

Cause: None of the exchange identification referred in participant.

Action: Make sure participant has at least one exchange identification.

Level: 1

Type: ERROR

Impact: Process

B2B-52300: Duplicate ID {0} found in node {1} and node {2}.

Cause: Duplicate unique ID found in two different nodes.

Action: Target system has element with the same , change ID of importing node.

Level: 1

Type: ERROR

Impact: Process

B2B-52301: MDSReference {0} is not referring to the trading partner.

Cause: MDSReference did not refer to the trading partner.

Action: Make sure given reference is pointing to the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52302: MDSReference {0} is not referring to an agreement.

Cause: MDSReference did not refer to an agreement.

Action: Make sure given reference is pointing to an agreement.

Level: 1

Type: ERROR

Impact: Process

B2B-52303: Compressed file expected to import.

Cause: Given file was not compressed using ZIP format.

Action: Verify given file is in compressed in ZIP format.

Level: 1

Type: ERROR

Impact: Process

B2B-52304: Agreement {0} cannot have listening channels.

Cause: Listening channels referred in agreement.

Action: Verify agreement is not referring to any listening channels.

Level: 1

Type: ERROR

Impact: Process

B2B-52305: In agreement {0}, trading partner {1} cannot have internal delivery channel.

Cause: Trading partner has internal delivery channel(s).

Action: Make sure none of the trading partners has internal delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-52306: Internal delivery channel {0} must not use HTTP transport.

Cause: Internal delivery channel has HTTP as transport.

Action: Make sure internal delivery channel is not using HTTP transport.

Level: 1

Type: ERROR

Impact: Process

B2B-52307: Listening delivery channel {0} must have a polling interval value.

Cause: Listening channel did not have value for polling interval.

Action: Make sure listening channel has polling interval value.

Level: 1

Type: ERROR

Impact: Process

B2B-52308: Listening delivery channel {0} with transport {1} does not have user name and password.

Cause: Listening delivery channel did not have user name and password in transport.

Action: Make sure listening delivery channel has user name and password in transport.

Level: 1

Type: ERROR

Impact: Process

B2B-52309: Validation error: see the diagnostic log for more details.

Cause: Unknown exception found in validation engine.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52310: The XML {0} is not well-formed.

Cause: Given XML content was not well-formed.

Action: Check XML content is well-formed and valid based on XSD/DTD constraints.

Level: 1

Type: ERROR

Impact: Process

B2B-52311: New document protocol {0} found in source reference {1}.

Cause: New document protocol name found in import source.

Action: Check name of the document protocol is correct.

Level: 1

Type: ERROR

Impact: Process

B2B-52312: Document protocol {0} must have ID {1} starts with doc_

Cause: Document protocol has ID which did not start with doc_

Action: Make sure document protocol has ID which starts with doc_

Level: 1

Type: ERROR

Impact: Process

B2B-52313: Document protocol {0} reference must be doc_id.xml

Cause: Document protocol reference was not in the form of doc_id.xml

Action: Make sure document protocol has reference in the form of doc_id.xml

Level: 1

Type: ERROR

Impact: Process

B2B-52314: Repository host name {0} and source Host name {1} are different.

Cause: Different host name found in repository and source.

Action: Make host name as unique in source and target system, while doing import.

Level: 1

Type: ERROR

Impact: Process

B2B-52315: Duplicate identification type {1} and value {2} found in source trading partner {0}.

Cause: More than one identification type found in source trading partner(s) for a same value and type.

Action: Make sure combination of identification type and value unique in the trading partner.

Level: 1

Type: ERROR

Impact: Process

B2B-52316: Pre-import transfer operation failed.

Cause: Pre-import validation(s) failed while importing.

Action: Check validation error messages found below this message and correct source files accordingly.

Level: 1

Type: ERROR

Impact: Process

B2B-52317: Duplicate identification type {1} and value {2} found in source agreement {0}.

Cause: More than one identification type found in source agreement(s) for a same value and type.

Action: Make sure combination of identification type and value unique in agreement.

Level: 1

Type: ERROR

Impact: Process

B2B-52318: MDSReference {0} does not exist in Repository.

Cause: Specified reference was not available in repository.

Action: Make sure specified reference is available in repository.

Level: 1

Type: WARNING

Impact: Process

B2B-52319: Transfer error: see log for more details.

Cause: Unknown exception identified in transfer.

Action: Check the diagnostic log. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52320: In agreement {0}, functional acknowledge can be enabled only when translate=true.

Cause: Agreement has functional acknowledge with translate flag set to inactive.

Action: Functional acknowledge can be active only when translate is active.

Level: 1

Type: ERROR

Impact: Process

B2B-52321: No metadata found to import.

Cause: No metadata identified in recommended package.

Action: Check given import file has metadata in correct package.

Level: 1

Type: ERROR

Impact: Process

B2B-52322: Mandatory field {0} is missing in {1}.

Cause: Metadata might be imported without all mandatory fields.

Action: Import metadata with all mandatory fields or save again the business object which has error, using UI.

Level: 1

Type: ERROR

Impact: Process

B2B-52323: Out-bound agreement {0} has to have only one exchange identifier type - {1}, in both participants

Cause: Out-bound agreement has more than one exchange identifier, or has different type of exchange identifier which is not suitable to exchange protocol.

Action: Make sure given exchange identifier is supported by chosen exchange protocol in delivery channel.

Level: 1

Type: ERROR

Impact: Process

B2B-52324: Listening Delivery channel {0} has duplicate endpoint {1}

Cause: Already a delivery channel has same endpoint, hence new delivery channel cannot be activated with same endpoint.

Action: Make sure all listening channel endpoints are unique.

Level: 1

Type: ERROR

Impact: Backup and Recovery

B2B-52325: Error in the SOA Composite {0}

Cause: See the base error message in the SOA Composite.

Action: Correct the error in the Fabric Composite.

Level: 1

Type: ERROR

Impact: Process

B2B-52326: Transport protocol with HTTPs URL has to have valid keystore location and password in host

Cause: Valid keystore location and password was not specified in host.

Action: Check with administrator, whether valid keystore location specified in host.

Level: 1

Type: ERROR

Impact: Process

B2B-52327: Channel {0} with transport {1} should have Queue name along with either datasource or the combination of SID, port number, user name, host name and password.

Cause: AQ channel does not have required parameter values to connect to AQ queue.

Action: Provide AQ Queue name along with either datasource or the combination of SID, port number, user name, host name and password.

Level: 1

Type: ERROR

Impact: Process

B2B-52328: Channel {0} with transport {1} should have either password or the combination of private key file and pass phrase.

Cause: SFTP channel does not have required parameter values to connect to SFTP server.

Action: Provide either password or the combination of private key file and pass phrase.

Level: 1

Type: ERROR

Impact: Process

B2B-52329: Web Service outbound flow invocation error.

Cause: An abnormal condition occurred during outbound flow invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52330: Error invoking translation Web Service.

Cause: An abnormal condition occurred during translation Web Service invocation.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52331: Translated content is not available

Cause: B2B metadata or XEngine configuration was invalid.

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52332: Message is discarded and moved to error state with message id {0}

Cause: Message is discarded and moved to a error state based on a user input.

Action: Resubmit the message

Level: 3

Type: ERROR

Impact: Process

B2B-52333: received data from trading partner is too long

Cause: received data from trading partner is too long.

Action: resend hllp message where payload length should be less than or equal to 99994 bytes.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52334: checksum validation failed

Cause: checksum validation failed for received data.

Action: resend hllp message with correct checksum value.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52335: payload length is incorrect in received hllp packed message.

Cause: payload length is incorrect in received hllp packed message.

Action: resend hllp message with correct payload length.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52336: validation of received hllp message failed

Cause: validation of received hllp message failed

Action: resend hllp message

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52337: payload length is too large(>99994 bytes) at client side

Cause: payload length is too large(>99994 bytes) at client side

Action: resend hllp message with payload length less than or equal to 99994 bytes.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52338: Negative Ack Received from trading partner.

Cause: received negative ack from trading partner

Action: resend hllp message

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52339: Large Payload directory is inaccessible

Cause: Specified directory for large payload is inaccessible

Action: Ensure specified directory for large payload exists and it is write enabled

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52340: Un-delivered Sequenced Message has been resubmitted. Moved to ERROR state

Cause: Un-delivered Sequenced Message has been resubmitted. Moved to error state

Action: Please monitor the diagnostic logs for any resultant issues

Level: 3

Type: ERROR

Impact: Process

B2B-52341: Interface Sequence Message discarded. Message id {0}. Dependent Outbound Rows discarded {1}

Cause: Interface Sequence Message discarded.

Action: Please monitor the diagnostic logs for any resultant issues

Level: 3

Type: ERROR

Impact: Process

B2B-52342: WebService API call content is not available

Cause: Abnormal condition occurs when calling webservice api

Action: Review the SOAP Fault for the exact error and correct the same. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53001: Handler is null while registering a Webservice End point

Cause: The handler is null when registering an endpoint.

Action: Provide a valid handler implementation while registering an endpoint. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53002: Unable to find a registered handler for this end point.

Cause: Unable to process the message due to handler identification failure.

Action: Re-register a valid handler for the end point. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53003: Unable to register an endpoint.

Cause: Registration of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53004: Unable to remove a registered end point

Cause: Removal of the webservice end point failed.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53005: Unable to package the payload to a SOAP message

Cause: Packing the payload into a message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53006: Unable to retrieve the payload from the SOAP message

Cause: Unpacking the soap message caused an exception.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53007: No payload component found in the message

Cause: No payload component found in the message

Action: Provide a payload component when enqueuing the message. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53008: Unable to create the SOAP Protocol components

Cause: Unable to create the SOAP Protocol components

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53009: Unable to decode the soap message

Cause: Unable to decode the soap message

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53010: An exception occurred while processing the received message.

Cause: Unable to process the SOAP message received in the transport layer.

Action: Review the log to evaluate the exact cause for failure. Contact Oracle Support Services if the problem persists.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53011: Duplicate message with same message id found in a batch. Changing original message id {0} to new message id {1} and rejecting the message.

Cause: Duplicate message with same message id found in a batch.

Action: Make sure that duplicate messages with same message id are not passed in the same batch.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53012: Invalid argument found. Name or identificationType is null.

Cause: Invalid argument found. Name or identificationType is null

Action: Make sure that name of trading partner and identificationType is passed correctly.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53013: Unable to evaluate Payload XPath Expression

Cause: Provided XPath Expression can not be evaluated.

Action: Make sure that configured XPath Expression to extract Payload is correct.

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53014: No payload or XPath not able to retrieve the payload

Cause: No payload or wrong XPath.

Action: Check the Payload and XPath

Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-53015: Unable to find specified security provider

Cause: Security Provider was not found in the environment.

Action: Verify provider.

Level: 1

Type: ERROR

Impact: Process

B2B-53016: Specified algorithm is not available from the specified provider

Cause: Algorithm was not available from the provider.

Action: Verify algorithm and provider .

Level: 1

Type: ERROR

Impact: Process

B2B-53017: Private key can not be recovered

Cause: Private key could not be recovered.

Action: Check the keystore and private key password.

Level: 1

Type: ERROR

Impact: Process

B2B-53018: KeysStore usage failure

Cause: Problem found in Keystore resource usage.

Action: Check the keystore.

Level: 1

Type: ERROR

Impact: Process

B2B-53019: Transport layer security context initialization failure

Cause: SSLContext was not getting initialized.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists

Level: 1

Type: ERROR

Impact: Process

B2B-53100: Unable to create sequencing entry for message

Cause: An error occurred while creating a sequencing entry for the message

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process

B2B-53101: Unable to update sequencing state for message

Cause: An error occurred while updating the sequencing state for the message

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process

B2B-53102: Failure occurred while persisting messages asynchronously in {0} repository

Cause: An error occurred while persisting messages to the {0} repository asynchronously.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process

B2B-53103: Unable to update Message state in the repository for message id {0}.

Cause: Unable to update Message state in the repository for message id {0}.

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process

B2B-53104: Unable to enqueue event to Event Manager.

Cause: Unable to enqueue event to Event Manager

Action: Review the diagnostic log for the exact error, which begins with the string 'ERROR:'. This error line, along with the preceding lines, will indicate the reason that this exception has been generated. Contact Oracle Support Services if the problem persists.

Level: 1

Type: ERROR

Impact: Process