6 B2B-50006 to B2B-52328

B2B-50006: Exception Received: Cause: B2B receives an exception message 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. If the problem persists, please contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50007: Notification of failure received: Cause: B2B receives an 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. If the problem persists, please contact Oracle Support Services
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. If the problem persists, please contact Oracle Support Services
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50010: Trading partner agreement identification error: Cause: B2B cannot identify a Trading Partner 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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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 b2b.log file 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, please contact Oracle Support Services.
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 b2b.log file 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, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50052: Engine already initialized.: Cause: Attempting to initialize an engine that has already been initialize; Action: Ensure that the engine is stopped before you attempt 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 b2b.log file 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, please contact Oracle Support Services.
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 b2b.log file 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, please contact Oracle Support Services.
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 b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50076: Error loading packaging plug-in.: Cause: Error loading packaging plug-in.; Action: Review the b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50077: Cannot Initialize Transport.: Cause: Cannot Initialize Transport.; Action: Review the b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50078: Cannot Shutdown Transport.: Cause: Cannot shutdown transport.; Action: Review the b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-50079: Transport error: Cause: An error has occurred in transport layer; Action: Review the b2b.log file 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, please contact Oracle Support Services.
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 b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-50081: Duplicated exchange protocol message error: Cause: Duplicated exchange protocol message generated by the trading partner.; 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 of the message.; Action: Review the b2b.log file 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, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-50545: Agreement {0} has expired or not in force as yet. The effective From/To dates are {1} - {2}.: Cause: 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 is present in the message.
Level: 1

Type: ERROR

Impact: Process

B2B-50548: Agreement {0} not in Active state.: Cause: Agreement is 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 a 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 indentifications
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 deliverychannel.
Level: 1

Type: NOTIFICATION

Impact: Process

B2B-50904: ReferTo message not found.: Cause: RefTo B2B MessageID 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 in extracting XPATH value.; Action: Make sure XPATH in document definition is correct and applicable for payload.
Level: 1

Type: ERROR

Impact: Process

B2B-51000: General packaging Error: Cause: Packaging details incorrect.; Action: Correct the packaging details in delivery channel.
Level: 1

Type: INTERNAL_ERROR

Impact: Process

B2B-51001: Packaging fail: Cause: Packaging information are insufficient.; Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51002: Unpacking fail: Cause: Packaging headers are incorrect.; Action: Correct the packaging details in delivery channel.
Level: 1

Type: ERROR

Impact: Process

B2B-51003: Encoding failed: Cause: Encoding type is 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-51004: Decoding failed: Cause: Decoding type is 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-51005: Validating packaging meta data information failed.: Cause: Packaging meta data information are insufficient.; Action: Verify packaging meta data information to pack the message.
Level: 1

Type: ERROR

Impact: Process

B2B-51006: Invalid input parameter: Cause: Packaging input parameters are invalid.; Action: Verify the packaging parameters and packaging meta data.
Level: 1

Type: ERROR

Impact: Process

B2B-51007: Missing packaging meta data information.: Cause: Missing few packaging meta data information.; Action: Verify the packaging meta data Information.
Level: 1

Type: ERROR

Impact: Process

B2B-51008: Circular dependency in packaging meta data information.: Cause: Circular dependency found in packaging meta data 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-51009: Missing one or more packaging elements in packaging meta data information.: Cause: Missing one or more packaging elements in packaging meta data information.; Action: Verify packaging meta data has packaging elements.
Level: 1

Type: ERROR

Impact: Process

B2B-51010: Missing composite packaging element in packaging meta data information.: Cause: None of the composite packaging elements present in the multipart message.; Action: Make sure multi-part message has at least one composite packaging element.
Level: 1

Type: ERROR

Impact: Process

B2B-51011: Invalid packaging meta data information.: 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 by 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 present 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: ERROR

Impact: Process

B2B-51017: Missing encryption information.: Cause: Required envelope information is not available.; 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: 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 is 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 is 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: Attempting to set the signature information when it has already 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 are already set for message.: Cause: Attempting 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: Key store resource location incorrect: Cause: Incorrect key store location specified.; Action: Specify correct key store location.
Level: 1

Type: ERROR

Impact: Process

B2B-51026: Encoding type does not supported: Cause: Encoding type is 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: 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 content type information.: Cause: MIME content type information did not present.; Action: Verify MIME content type header present.
Level: 1

Type: ERROR

Impact: Process

B2B-51055: Missing information for message component.: Cause: Message component information is required.; 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: Required certificate chain did not present.; 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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: 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. If the problem persists, please contact Oracle Support Services.
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. If the problem persists, please contact Oracle Support Services.
Level: 1

Type: 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 key store 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 decrypting S/MIME message.: Cause: General failure 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 is 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 is 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 is 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: CRL missing issuer.; 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 is not correct.; Action: Request a resend from the partner or re-send the message with correct content type.
Level: 1

Type: ERROR

Impact: Process

B2B-51121: Empty recipient list: Cause: No recipient list is present 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 is 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 is not available in the key store.; 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 is 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 is not valid yet because the certificate creation date is 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 key store,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 key store.: Cause: Key Store file is not in correct format, incorrect location or incorrect password.; Action: Make sure the key store is generated properly or the location or password is correct.
Level: 1

Type: ERROR

Impact: Process

B2B-51195: Failed to get key-pair from key store: Cause: Unable to retrieve key pair from the key store.; Action: Verify that the key store 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-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-51509: Create message error: component- {0}.: Cause: Failed to create message components.; Action: Verify all componenets of the message.
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 time stamp.: Cause: Time stamp was not in the correct format.; Action: Correct time-stamp 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 host and 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 Host matches with ToService field of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51562: Mismatch in the service of host and 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 Host matches with FromService of the trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51563: Mismatch in the role of host and 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 Host matches with ToRole field of trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-51564: Mismatch in the role of host and 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 Host matches with FromRole field of 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 non empty.
Level: 1

Type: ERROR

Impact: Process

B2B-51573: Payload file does not follow the naming convention that is expected. Expect format is <FromPartyName>_<MessageID>.<Extension> e.g. Sun_1234235.dat: Cause: Payload file did not follow the naming convention that is expected.; Action: Expect 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 is not installed.; Action: Make sure XEngine is installed.
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 specified in party ID.: Cause: No type 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 this ebMS message is incorrect.: Cause: Content type set for this ebMS message is 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 is 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 is 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 defected 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 is 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 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 be present 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 does not have the element {0}.: 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-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 is not present.; 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 is 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 is 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 is 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 does 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: effectiveFromDate {0} should be less than effectiveToDate {1} in agreement {2}.: Cause: effectiveFromDate should be less than effectiveToDate.; Action: Make sure the effectiveFromDate is lesser 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 participant must be a host in an agreement {0}.: Cause: None of the participant 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} is not in sync with the corresponding definition in trading partner {3}.: Cause: Document type name and document protocol version used in agreement was 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: Check participant in agreement is referring 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 refers 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} is not sync with trading partner identification.: Cause: Participant identification type and value was not sync with trading partner identification.; Action: Make sure the value and type given in identification reference in participant is sync with trading partner identification.
Level: 1

Type: ERROR

Impact: Process

B2B-52274: Participant {0} can have only one exchange identifier.: Cause: Participant can have zero or 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 {1}: 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 key store.: Cause: Given certificate alias did not exist in key store.; Action: Verify certificate alias is present in key store.
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 is 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 URL.: Cause: HTTP transport protocol did not have URL.; Action: Make sure HTTP transport protocol has an 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 possible 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 trading partners, document type and document protocol version.; Action: Make sure only one agreement deals these trading partner with document type and document protocol combination.
Level: 1

Type: ERROR

Impact: Process

B2B-52292: In agreement {0}, trading partner {1} must have a delivery channel.: Cause: Trading partner did not have delivery channel to send out bound message.; Action: Make sure in 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 only the internal delivery channel.: Cause: Host refers other than internal delivery channel.; Action: Make sure Host is not referring 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 channels.; Action: Make sure only one delivery channel present 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 packaging protocol element.: Cause: Packaging protocol reference refers other than packaging protocol element.; Action: Verify packaging protocol reference refers Packaging protocol Element.
Level: 1

Type: ERROR

Impact: Process

B2B-52298: Transport URL {0} already used in system.: Cause: More than once same end point used in system.; Action: Make sure same end point 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 node.; Action: Target system has element with the same id, change id of importing node.
Level: 1

Type: ERROR

Impact: Process

B2B-52301: MDSReference {0} is not referring the trading partner.: Cause: MDSReference is not referring the trading partner.; Action: Make sure given reference is pointing trading partner.
Level: 1

Type: ERROR

Impact: Process

B2B-52302: MDSReference {0} is not referring an agreement.: Cause: MDSReference is not referring an agreement.; Action: Make sure given reference is pointing an agreement.
Level: 1

Type: ERROR

Impact: Process

B2B-52303: Compressed file expected to import.: Cause: Given file is 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 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 partner 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 log for more details.: Cause: Unknown exception identified in validation engine.; Action: Check the b2b.log file or contact Oracle Support Services.
Level: 1

Type: INCIDENT_ERROR

Impact: Process

B2B-52310: {0}: XML is not well-formed.: Cause: Given XML content is 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 is 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 is 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 b2b.log file or contact Oracle Support Services.
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 meta data found to import.: Cause: No meta data identified in recommended package.; Action: Check given import file has meta data in correct package.
Level: 1

Type: ERROR

Impact: Process

B2B-52322: Mandatory field {0} is missing in {1}.: Cause: Meta data might be imported without all mandatory fields.; Action: Import meta data 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 delivarychannel.
Level: 1

Type: ERROR

Impact: Process

B2B-52324: Listening Delivery channel {0} has duplicate end point {1}: Cause: Already a delivery channel has same end point, hence new delivery channel can not be activated with same end point.; 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: Exception happened in the SOA Composite.; Action: Correct the error in the Fabric Composite.
Level: 1

Type: ERROR

Impact: Fabric

B2B-52326: Transport protocol with https url has to have valid keystore location and password in host: Cause: Valid keystore location and password may not be 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 paramter values to connect to AQ Queue.; Action: Please 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 paramter values to connect to SFTP server.; Action: Please provide either password or the combination of Private key file and Pass phrase.
Level: 1

Type: ERROR

Impact: Process