Error Codes for AS4
0000.3005 Error relating bizdoc with Document ID {0} to bizdoc with Document ID {1} as {2}.
Explanation: An error occurred while retrieving the user message related to the receipt or error signal from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3004 Error updating Processing Status to {0} and User Status to {1} for bizdoc with Document ID {2} and Internal ID {3}. Error message: {4}.
Explanation: Error updating Processing Status and User Status for a message document in Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3003 Error retrieving partnerId from Trading Networks for External Id Value {0}, Type {1}. Error message: {2}.
Explanation: An error occurred while retrieving the partnerId parameter from Trading Networks.
Action: Ensure the partner profile in Trading Networks is configured correctly.
0000.3002 Error while saving bizdoc for message with Message Id {0} in Trading Networks. Error message: {1}.
Explanation: An error occurred while saving the message in Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3001 Validation error for TPA with AgreementID {0}: The mandatory keystore parameters required for Security are not set in the partner TPA.Details: {1}
Explanation: One of the security parameters specified in the error message is not configured in the TPA.
Action: Configure the mandatory security parameters in the TPA and try again.
0000.3000 Error occurred during startup of WmAS4 package. Error message: {0}.
Explanation: An error occurred while starting the WmAS4 package.
Action: See the error message for details, fix the reported issue, and restart Integration Server.
0000.0006 The message partition channel {0} is empty.
Explanation: A pull request was received for the specified MPC but this MPC contains no messages.
Action: Ensure that there are messages in the specified MPC.
0000.0103 Message with MessageId {0} does not comply with the security parameters configured in the TPA. Error message: {1}.
Explanation: The processor determined that the message's security methods, parameters, scope or other security policy-level requirements or agreements were not satisfied.
Action: Ensure the security parameters in the partner TPA are configured correctly.
0000.0102 Decryption failed for message with MessageId {0}. Error message: {1}.
Explanation: The security module could not decrypt the encrypted data reference that the security header intended for the SOAP actor.
Action: Confirm that the private key configured for the Enterprise in the Integration Server keystore is correct.
0000.0101 Signature verification failed for message with MessageId {0}. Error message: {1}.
Explanation: The security module could not validate the signature in the security header that was intended for the SOAP actor.
Action: Ensure the public certificates configured for the trading partner in the Integration Server keystore are correct.
0000.3042 Validation error for TPA with AgreementID {0}: If security needs to be enabled, one of the following parameters needs to be set in the TPA: policy file, userNameToken, sign, or encrypt.
Explanation: Security is enabled but the required security parameters are not configured in the TPA.
Action: Configure at least one of the parameters specified in the error message.
0000.3008 Internal error. Error processing input \n {0}.
Explanation: An internal error occurred.
Action: Contact Software AG Global Support.
0000.3009 Error retrieving TPA for senderID {0} receiverID {1} agreementID {2} from Trading Networks. Error message: {3}.
Explanation: An error occurred while retrieving the TPA from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3011 Error retrieving bizdoc with Internal ID {0} from Trading Networks. Error message: {1}.
Explanation: An error occurred while retrieving the bizdoc from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3012 Error retrieving bizdoc with Document ID {0} from Trading Networks. Error message: {1}.
Explanation: An error occurred while retrieving the bizdoc from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3013 Error retrieving content part {0} from bizdoc with Internal ID {1} from Trading Networks. Error message: {2}.
Explanation: An error occurred while retrieving content part from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3014 Error retrieving message with MessageId {0} referenced by {1} {2} from Trading Networks. Error message: {2}.
Explanation: An error occurred while retrieving the message from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3015 Error persisting message {0} in Trading Networks. Error message: {1}.
Explanation: An error occurred while persisting the message in Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3017 Error while retrieving leg with label {0} from TPA with AgreementID {1} for service {2} and action {3}.
Explanation: An error occurred while retrieving the specified leg from the designated TPA.
Action: Ensure that the leg specified in the message is configured in the designated TPA.
0000.3020 Error while retrieving TPAs. Error message: {0}.
Explanation: An error occurred while retrieving the module's TPAs from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3021 Error retrieving TPA for mpc {0} and Agreement ID {1} from Trading Networks.
Explanation: The module was unable to retrieve the TPA while generating or processing a pull signal.
Action: Ensure at least one TPA is configured in Trading Networks with the Message Partition Channel specified in the message.
0000.3022 Authorization information for {0} is not configured for the TPA with AgreementID {1}.
Explanation: An error occurred while retrieving authorization information for the initiator or responder from the TPA with the agreement ID specified in the error message.
Action: Ensure that the required authorization information is configured in the TPA.
0000.3023 Error while retrieving content for the MIME attachment referenced by Content-ID {0}. Error message: {1}.
Explanation: An error occurred while retrieving the content for the MIME attachment.
Action: For a generated user message, ensure the partInfo and partContent parameters of the submit service are valid. For a received user message, consult with the trading partner who sent the message to resolve the error.
0000.3024 Error retrieving content from the SOAP Body referenced by id {0}. Error message: {1}.
Explanation: An error occurred while retrieving the payload content from the SOAP body.
Action: For a generated user message, ensure the partInfo and partContent parameters of the submit service are valid. For a received user message, consult with the trading partner who sent the message to resolve the error.
0000.3025 Error while retrieving content for the external resource referenced by the URL {0}. Error message: {1}.
Explanation: An error occurred while retrieving payload content from the URL.
Action: For a generated user message, ensure the partInfo and partContent parameters of the submit service are valid. For a received user message, consult with the trading partner who sent the message to resolve the error.
0000.3028 Validation error for TPA with AgreementID {0}. Parameter {1} is not configured.
Explanation: In the specified TPA, a required parameter has not been configured.
Action: In the specified TPA, configure the required parameter.
0000.3029 Validation error for TPA with AgreementID {0}. Leg with label {1} is not configured.
Explanation: The specified leg is not configured in the TPA.
Action: In the TPA, configure the leg specified in the message.
0000.3030 Validation error for TPA with AgreementID {0}. Parameter {1} is not configured in leg with label {2}.
Explanation: In the designated TPA, a mandatory leg parameter is not configured for the leg specified.
Action: In the TPA, configure the leg parameter specified in the message.
0000.3031 Validation error for TPA with AgreementID {0}. Parameter protocol/address within leg with label {1} is an invalid URL.
Explanation: In the designated TPA, the protocol/address value is not configured with a valid URL for the leg specified.
Action: In the TPA, configure the protocol/address parameter as a valid URL for the leg specified.
0000.3032 Validation warning for TPA with AgreementID {0}. Parameter businessInfo/service within leg {1} must be configured as a URI.
Explanation: In the specified TPA leg, the businessInfo/serviceType parameter is not configured and the businessInfo/service parameter is not configured as a URI.
Action: In the specified TPA leg, ensure that either the businessInfo/serviceType parameter is configured or the businessInfo/service is configured with a valid URI.
0000.3033 Validation error for TPA with AgreementID {0}. Parameter businessInfo/service within leg {1} must be configured with the value "http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/service".
Explanation: In the specified TPA leg, the businessInfo/action parameter is configured with the value "http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/test", but the businessInfo/service parameter is not configured as "http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/service" as required.
Action: In the specified TPA leg, ensure that the values of the businessInfo/action parameter and the businessInfo/service parameter are consistent with the ebMS version 3.0 specification.
0000.3034 Internal Error: Error during initialization of logger, JournalLog Handler could not be retrieved.
Explanation: Logger initialization failed.
Action: Contact Software AG Global Support.
0000.3035 Error loading AS4 config file "packages/WmAS4/config/config.cnf". Error message: {0}.
Explanation: There was an error loading the config.cnf file.
Action: Ensure the config.cnf file is at the specified location. If it is not present, contact Software AG Gobal Support.
0000.3036 Failed to retrieve TPA for fromPartyId {0}, fromPartyIdType {1}, toPartyId {2}, toPartyIdType {3}, and pmodeId {4}. Error message: {5}.
Explanation: The TPA for the specified parameters could not be retrieved.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3037 Error while loading policy file {0}.
Explanation: The specified policy file, which is used for security purposes, could not be loaded.
Action: Ensure that the content of the policy file has the correct syntax.
0000.3038 Error retrieving message for RefToMessageId {0} from Trading Networks. Error message: {1}.
Explanation: An error occurred while retrieving the user message from Trading Networks.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3039 Error while processing the {0} message with messageId {1}. Error message: {2}.
Explanation: An error occurred while retrieving the TPA for the specified message.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3040 P-Mode authorization for pull signal failed for the mpc {0}. The authorization parameters do not match.
Explanation: P-Mode authorization failed because the authorization check failed.
Action: In the TPA, ensure the Initiator username and password are configured correctly.
0000.3041 P-Mode authorization for pull signal failed. The input message has PMode authorization parameters, but the PMode authorization in the TPA is disabled.
Explanation: The input message contains P-Mode authorization parameters, but P-Mode authorization in the TPA is disabled.
Action: In the TPA, set the security/pmodeAuthorize parameter to true to enable P-Mode authorization.
0000.3058 Validation error for TPA with AgreementID {0}. Parameter errorHandling/report/asResponse within leg must be set to false to enable splitting.
Explanation: The errorHandling/report/asResponse parameter within the leg is not set to false as required to enable splitting.
Action: Set errorHandling/report/asResponse to false and configure errorHandling/report in the leg.
0000.3059 Validation error for TPA with AgreementID {0}. Parameter pmode/splitting/fragmentSize should be greater than zero
Explanation: Parameter pmode/splitting/fragmentSize is not greater than zero.
Action: Set the value of fragmentSize to a positive, non-zero integer.
0000.3060 Validation error for TPA with AgreementID {0}. Parameter security/receipt/replyPattern within leg with leg requestUM must be configured to callback for splitting
Explanation: The security/receipt/replyPattern parameter within the requestUM leg is not configured to callback for splitting.
Action: Within the requestUM leg, configure security/receipt/replyPattern as callback and configure security/receipt/replyTo with the address to which the receipt should be sent.
0000.3043 Error while processing the security for the message. Error message {0}.
Explanation: An error occurred while processing the security of the message.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3045 Error while setting the algorithm suite for security. Error message {0}.
Explanation: An error occurred while configuring the security parameters.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3044 Error while retrieving the Integration Server keystore details for keystore alias {0} and key alias {1}.
Explanation: An error occurred while retrieving the Integration Server keystore details.
Action: Ensure the specified ISKeystoreAlias and keyAlias parameters are configured correctly in Integration Server.
0000.3049 Error updating UserStatus of bizdoc with Internal ID {0} to {1}. Error Message: {2}.
Explanation: An error occurred while updating the user status of the bizdoc.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3051 Error adding content for {0} to SOAP Body. Error message: {1}.
Explanation: An error occurred while adding an input payload to the SOAP Body.
Action: Ensure that the payload has XML-structured content.
0000.3052 The partInfo input parameter is not configured for partContent [{0}]. The specified partContent will not be added as a payload part in the outbound ebMS message.
Explanation: There is no value for the partInfo input parameter, which acts as metadata for the partContent parameter. The module cannot resolve the location for partContent, so partContent is ignored and omitted from the message.
Action: Provide a value for the partInfo parameter for the partContent specified in the warning message.
0000.3027 Validation warning for TPA with AgreementID {0}.Parameter {1} is not configured in leg with label {2}.
Explanation: Validation of the TPA identified by the AgreementID has failed for reasons specified by the error message.
Action: See the error message and rectify the TPA accordingly.
0000.3036 Encountered error while retrieving PMode for fromPartyId {0}, fromPartyIdType {1}, toPartyId {2}, toPartyIdType {3}, fromRole {4}, toRole {5}, service {6}, action {7}, agreementRef {8}, and pmodeId {9}. Error details: {10}
Explanation: The TPA for the specified parameters could not be retrieved.
Action: See the error message for details and take appropriate action to resolve the problem.
0000.3053 Validation error for TPA with AgreementID {0}. Parameter errorHandling/report/receiverErrorsTo must be configured in leg with label requestUM, when the errorHandling/report/asResponse parameter is configured as false.
Explanation: The errorHandling/report/asResponse parameter is configured as false (that is, errors are be reported on the back channel); however, the address to which errors should be reported is not configured in the requestUM leg.
Action: In the requestUM leg, configure the errorHandling/report/receiverErrorsTo parameter to indicate the address to which errors should be reported.
0000.3054 Validation error for TPA with AgreementID {0}. Parameter errorHandling/report/receiverErrorsTo within leg with label requestUM contains an invalid URL.
Explanation: The errorHandling/report/receiverErrorsTo parameter within the leg with label {1} contains an invalid URL.
Action: Ensure that the errorHandling/report/receiverErrorsTo parameter within the requestUM leg in the TPA specified by the error message contains a list of comma separated valid URLs.
0000.3055 Validation error for TPA with AgreementID {0}. Parameter security/receipt/replyTo must be configured in leg with label requestUM, when the security/receipt/sendReceipt is configured as true and the security/receipt/replyPattern parameter is configured as callback.
Explanation: The security/receipt/sendReceipt is configured as true and the security/receipt/replyPattern parameter is configured as callback, but the security/receipt/replyTo parameter in the requestUM leg is not configured.
Action: Configure the security/receipt/replyTo parameter in the requestUM leg for the TPA specified by the error message.
0000.3056 Validation error for TPA with AgreementID {0}. Parameter security/receipt/replyTo within leg with label requestUM contains an invalid URL.
Explanation: The security/receipt/replyTo parameter within the requestUM leg contains an invalid URL.
Action: Configure the security/receipt/replyTo parameter within the requestUM leg of the TPA specified by the error as a valid URL.
0000.3057 Validation error for TPA with AgreementID {0}. Parameter security/receipt/replyPattern within leg with label requestUM must be configured to callback for One-Way/Pull
Explanation: The security/receipt/replyPattern parameter in the requestUM leg is not configured as callback, as required for the One-Way/Pull MEP.
Action: Configure the security/receipt/replyPattern parameter as callback.
0000.3066 There is no requestUM leg with mpc {0}. The mpc name configured in the requestSM leg and requestUM leg should be same
Explanation: The mpc configured in the requestSM leg of the TPA does not match the mpc configured in the request UM leg of the TPA.
Action: Edit the TPA so that the value of BusinessInfo/mpc in the requestSM leg and the value of BusinessInfo/mpc in requestUM leg are the same.
0000.3067 TPA configuration Error. Password should not be null or empty for the username {0}.
Explanation: The username is set but the password is null or empty.
Action: Set the password parameter to a non-empty value.
0000.3074 as4.payload.large.threshold is configured as {0}. The property must be configured to a value greater than 16KB. The module will use a threshold value of 16KB instead.
Explanation: The as4.payload.threshold property is less than 16KB.
Action: Configure the as4.payload.threshold property to greater than 16KB.
0001.3000 An error occurred while generating Receipt for the received UserMessage which has messageId {0}. Error message {1}.
Explanation: An error occurred while generating the receipt for the received user message.
Action: See the error message for details and take appropriate action to resolve the problem.
0001.3001 Error while processing the received message with messageType {0}, messageId {1}. Error message: {2}.
Explanation: An error occurred while processing the received message.
Action: See the error message for details and take appropriate action to resolve the problem.
0001.3002 Non-Repudiation check for received Receipt with messageId {0} failed. URI {1} in the UserMessage with messageId {2} does not have a match.
Explanation: The non-repudiation check failed.
Action: Consult with the trading partner to ensure the partner sent the correct non-repudiation information.
0001.3004 Received a duplicate message with messageId {1}.
Explanation: A duplicate message was detected.
Action: Notify the trading partner that the message sent was a duplicate.
0001.3005 Invalid ebMS Header error. Error Message: The Messaging element must contain at least one of the child elements UserMessage or SignalMessage.
Explanation: The inbound message's ebMS message header does not contain a UserMessage or SignalMessage element.
Action: Notify the partner that the message header was incomplete.
0001.3006 Invalid ebMS Header error. Error message: The SignalMessage element must contain at least one of the child elements PullRequest or Error or Receipt.
Explanation: The SignalMessage element of the inbound message does not contain at least one of these elements: PullRequest, Error, or Receipt.
Action: Notify the trading partner that a message with an invalid SignalMessage element was received.
0001.3007 EBMS processing error. Error Message: Either the UserMessage/PartyInfo element is missing from the ebMS header or the element is encrypted.
Explanation: The module is unable to retrieve the UserMessage/PartyInfo element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3008 EBMS processing error. Error Message: Either the UserMessage/PartyInfo/From element is missing from the ebMS header or the element is encrypted.
Explanation: The module is unable to retrieve the UserMessage/PartyInfo/From element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3009 EBMS processing error. Error Message: Either the UserMessage/PartyInfo/From/PartyId element is missing from the ebMS header or the element is encrypted.
Explanation: The module is unable to retrieve the From/PartyId element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3010 Inconsistent value error. Error Message: The UserMessage/PartyInfo/From/PartyId element cannot be empty.
Explanation: The module is unable to retrieve a value from the PartyId element of the inbound message's ebMS header.
Action: Notify the message sender.
0001.3011 EBMS processing error. Error Message: Either the UserMessage/PartyInfo/To element is missing from the ebMS header or the element is encrypted.
Explanation: The module is unable to retrieve the UserMessage/PartyInfo/To element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3012 EBMS processing error. Error Message: Either the UserMessage/PartyInfo/To/PartyId element is missing from the ebMS header or the element is encrypted.
Explanation: The module is unable to retrieve the To/PartyId element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3013 Inconsistent value error. Error Message: The UserMessage/PartyInfo/From/PartyId element cannot be empty.
Explanation: The module is unable to retrieve a value from the From/PartyId element from the inbound message's ebMS header.
Action: Notify the message sender.
0001.3014 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/AgreementRef element is required by the module to identify the agreement for processing an inbound message.
Explanation: The UserMessage/CollaborationInfo/AgreementRef element is missing.
Action: Notify the message sender.
0001.3015 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/AgreementRef value is required by the module to identify the agreement for processing an inbound message.
Explanation: The UserMessage/CollaborationInfo/AgreementRef value is missing.
Action: Notify the message sender.
0001.3016 Feature not supported error. Error Message: Processing of Bundled messages is not currently supported.
Explanation: Processing of bundled messages is not supported currently.
Action: Contact Software AG Global Support for any inquiries regarding support of this feature.
0001.3018 Invalid ebMS Header error. Error Message: {0}.
Explanation: Validation of the ebMS header has failed due to the reason specified in the error message.
Action: Notify the message sender.
0001.3019 EBMS validation error. Error Message: {0}.
Explanation: The EBMS header validation process failed for reasons other than an invalid header.
Action: Report the problem described in the error message to Software AG Global Support.
0001.3020 Inconsistent value error: Error Message: The content of the From/PartyId element MUST be a URI if the PartyId/@type attribute is not present.
Explanation: The content of the PartyId element is not a valid URI as defined in the specification.
Action: Notify the message sender that the PartyId element does not conform to ebMS specification.
0001.3021 Inconsistent value error: Error Message: The content of the To/PartyId element MUST be a URI if the PartyId/@type attribute is not present.
Explanation: The content of the PartyId element is not a valid URI as defined in the specification.
Action: Notify the message sender that the PartyId element does not conform to ebMS specification.
0001.3022 Inconsistent value error: Error Message: The content of the AgreementRef element MUST be a URI if the AgreementRef/@type attribute is not present.
Explanation: The content of the AgreementRef element is not a valid URI as defined in the specification.
Action: Notify the message sender that the AgreementRef element does not conform to ebMS specification.
0001.3023 Inconsistent value error: Error Message: The content of the Service element MUST be a URI if the Service/@type attribute is not present.
Explanation: The content of the Service element is not a valid URI as defined in the specification.
Action: Notify the message sender that the Service element does not conform to ebMS specification.
0001.3025 EBMS processing warning. Warning Message: Either the From/PartyId/@type attribute is not present or attribute is empty.
Explanation: The module is unable to extract the From/PartyId/@type attribute value from the ebMS header of the inbound message.
Action: Notify the message sender to set the From/PartyId/@type attribute with the appropriate value.
0001.3026 EBMS processing warning. Warning Message: Either the To/PartyId/@type attribute is not present or attribute is empty.
Explanation: The module is unable to extract the To/PartyId/@type attribute value from the ebMS header of the inbound message.
Action: Notify the message sender to set the From/PartyId/@type attribute with the appropriate value.
0001.3027 Incoming Message does not comply with the security parameters configured in the TPA. Error message: {0}.
Explanation: The content of the element specified in the incoming message is not compatible with the expected content based on the associated TPA.
Action: Notify the message sender.
0001.3028 Processing mode mismatch error. Error Message: The expected content of the element {0} is {1}, the actual content is {2}.
Explanation: The content of the element specified in the error message is not compatible with the expected content based on the associated TPA.
Action: Notify the message sender.
0001.3029 Processing mode mismatch error. Error Message: The Messaging/eb:UserMessage/eb:MessageProperties element is expected with the required properties {0}.
Explanation: The content of the element specified in the error message is not compatible with the expected content based on the associated TPA.
Action: Notify the message sender.
0001.3030 Processing mode mismatch error. Error Message: The Messaging/eb:UserMessage/eb:MessageProperties element is expected to contain the required property {0}.
Explanation: The content of the element specified in the error message is not compatible with the expected content based on the associated TPA.
Action: Notify the message sender.
0001.3031 Security processing warning. Warning Message: Skipping security processing for the message of type {0} with messageId {1} as the TPA leg is not available.
Explanation: The module cannot process the received message's security headers because it can't retrieve a TPA leg to process the received Error or Receipt signal. If the SignalMessage/MessageInfo/RefToMessageId element is present, however, the module continued to process the message.
Action: Check the error logs to see if there was an error resolving the TPA or retrieving a TPA leg.
0001.3033 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/Service element is missing or encrypted.
Explanation: The UserMessage/CollaborationInfo/Service element is missing or encrypted.
Action: Notify the message sender.
0001.3034 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/Service value is missing.
Explanation: The UserMessage/CollaborationInfo/Service value is missing.
Action: Notify the message sender.
0001.3035 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/Action element is missing or encrypted.
Explanation: The UserMessage/CollaborationInfo/Action element is missing or encrypted.
Action: Notify the message sender.
0001.3036 EBMS processing error. Error Message:The UserMessage/CollaborationInfo/Action value is missing.
Explanation: The UserMessage/CollaborationInfo/Action value is missing.
Action: Notify the message sender.
0001.3037 No ebMS Error generated for the message in error {0}.
Explanation: A message was received in error but the module did not generate an ebMS error.
Action: None.
0001.3038 Unable to retrieve errorHandling parameters for the message in error {0}. Error message: the TPA leg is not available.
Explanation: The module was unable to retrieve the TPA leg for the message in error, so it cannot report the generated ebMS error.
Action: None.
0001.3039 Error while decompressing the received payload part {0}, Error message: {1}
Explanation: Decompressing the payload failed.
Action: Ensure the incoming payload is formatted correctly, is compressed, and is not corrupted.
0001.3040 The received fragment with groupID {0} has the MessageSize set. MessageSize has already been received by a previous fragment of this group. Rejecting this fragment group.
Explanation: The fragment group is rejected. More than one fragment in the group has MessageSize configured.
Action: Consult with the trading partner to ensure that only one fragment in the group has MessageSize configured.
0001.3041 The received fragment with groupID {0} has the FragmentCount set. FragmentCount has already been received by a previous fragment of this group. Rejecting this fragment group.
Explanation: The fragment group is rejected. More than one fragment in the group has the FragmentCount parameter configured.
Action: Consult with the trading partner to ensure that only one fragment in the group has FragmentCount configured.
0001.3042 The received fragment with groupID {0} has the MessageHeader set.MessageHeader has already been received by a previous fragment of this group. Rejecting this fragment group.
Explanation: The fragment group is rejected. More than one fragment has MessageHeader configured.
Action: Consult with the trading partner to ensure that only one fragment in the group has MessageHeader configured.
0001.3043 The received fragment with groupID {0} has the Action parameter set. Action parameter has already been received by a previous fragment of this group. Rejecting this fragment group.
Explanation: The fragment group is rejected. More than one fragment in the group has the Action parameter configured.
Action: Consult with the trading partner to ensure that only one fragment in the group has the Action parameter configured.
0001.3044 The received fragment with groupID {0} has the CompressionInfo parameter set. CompressionInfo parameter has already been received by a previous fragment of this group. Rejecting this fragment group.
Explanation: The fragment group is rejected. More than one fragment in the group has CompressionInfo configured.
Action: Consult with the trading partner to ensure that only one fragment in the group has CompressionInfo configured.
0001.3045 The fragment received is a duplicate fragment. A frament with the same messageID is received before.
Explanation: The fragment group is rejected. The group contains duplicate fragments.
Action: Notify the trading partner that duplicate fragments were received.
0001.3046 The received fragment with groupID {0} has the FragmentNum value greater than the FragmentCount. Rejecting this fragment group.
Explanation: The fragment group is rejected. At least one of the fragments received has a FragmentNum value that exceeds the value of FragmentCount.
Action: Consult with the trading partner to ensure that the FragmentNum value for all fragments is not greater than the FragmentCount.
0001.3047 The received fragment with groupID {0} has the FragmentCount value which is lesser than the FragmentCount received by a previous fragment. Rejecting this fragment group.
Explanation: The fragment group is rejected. The value of FragmentCount for this fragment is less than the value of FragmentCount for a fragment received previously.
Action: Consult with the trading partner to ensure the correct FragmentCount values were sent.
0001.3048 The received fragment belongs to the group {0}. This is a rejected group. The fragment is rejected.
Explanation: The fragment is rejected. It belongs to a rejected group.
Action: Consult with the trading partner and take appropriate action.
0001.3049 The received fragment belongs to the group {0}. This is a completed group. The fragment is rejected.
Explanation: The fragment is rejected. It belongs to a completed group.
Action: Consult with the trading partner and take appropriate action.
0001.3050 The received fragment belongs to the group {0}. The JoinInterval time has expired. All the fragments of this group will be rejected.
Explanation: The fragment is rejected. It belongs to an expired group.
Action: Consult with the trading partner and take appropriate action.
0001.3093 No PMode is configured for senderID {0} and receiverID {1} with agreementRef {2}.
Explanation: The TPA for the specified parameters could not be retrieved.
Action: See the error message for details and take appropriate action to resolve the problem.
0001.3094 Duplicate key found while updating cache {0} with key {1} for PMode ID {2}. PMode ID {3} has same cache entry.
Explanation: There are duplicate key entries in the sender ID, receiver ID, from role, to role, agreementRef, service and action PMode parameters within the cache.
Action: Check the related TPAs and modify it accordingly.
0001.3095 Unable to retrieve certificate for hostInternal ID {0}, partnerInternal ID {1}, and signCertificate ID {2}.
Explanation: The signing certificate is not configured for the respective partners.
Action: Make sure to configure the signing certificate in the partner profiles of the respective partners in Trading Networks.
0001.3096 No private key is configured for hostInternal ID {0}, partnerInternal ID {1}, and signCertificate ID {2}.
Explanation: The signing certificate's private key is not configured for the host.
Action: Make sure to configure the private key in the partner profiles for the host in Trading Networks.
0001.3097 Unable to retrieve certificate for hostInternal ID {0}, partnerInternal ID {1}, and encryptCertificate ID {2}.
Explanation: The encryption certificate is not configured for the respective partners.
Action: Make sure to configure the encrypt certificate in the partner profiles of the respective partners in Trading Networks.
0001.3098 No private key is configured for hostInternal ID {0}, partnerInternal ID {1}, and encryptCertificate ID {2}.
Explanation: The decryption certificate's private key is not configured for the host.
Action: Make sure to configure the private key in the partner profiles for the host in Trading Networks.
0001.3099 Encountered validation error for TPA with AgreementID {0}. Either security/receipt/replyPattern must be set to response or receptionAwareness/retry must be enabled when errorHandling/report/missingReceiptNotifyProducer is enabled.
Explanation: The TPA parameters for MEP are configured incorrectly.
Action: In the TPA, configure the correct paramters for the specified MEP.
0001.3101 Encountered validation error for TPA with Agreement ID {0}. Both requestUM and replyUM legs must be configured for Two-Way/Push Push MEP.
Explanation: You must configure both, requestUM and replyUM legs for Two-Way/Push Push MEP in TPA.
Action: Configure both, requestUM and replyUM legs for Two-Way/Push Push MEP in TPA.
0001.3103 Unable to create bizdoc for the doc id {0}, payload id {1}, and mimeType {2}. Details: {3}
Explanation: Document is not recognized by the system as it may not be supported.
Action: Ensure that you have the respective document type installed and enabled.
0001.3104 Encountered validation error for TPA with AgreementID {0}. The security/receipt/sendReceipt parameter must be configured to true if the errorHandling/report/missingReceiptNotifyProducer parameter is configured as true.
Explanation: The TPA parameters for MEP are configured incorrectly.
Action: In the TPA, configure the correct paramters for the specified MEP.
0002.3001 The wm.ip.estd.as4.msh:submit service failed to process the input pipeline {0}. Error message {1}.
Explanation: The submit service failed to send the message.
Action: See the error message for details and take appropriate action to resolve the problem.
0002.3003 Error while processing the retry parameters. The module will continue as though retry parameters are not set. Error message: {0}.
Explanation: The retry parameters specified are invalid. The module will continue as though no retry parameters are set.
Action: See the error message for details and take appropriate action to resolve the problem.
0002.3011 There was an error while processing the content for payload {0}. Error message: {1}
Explanation: When executing the wm.ip.estd.as4.msh:submit service, processing part of the content provided in the partContent input parameter failed.
Action: See the error message for details and take appropriate action. Also, verify the partContent mapping.
0002.3012 There was an error while large payload handling for the payload {0}. Error message: {1}
Explanation: Handling the large payload failed.
Action: See the error message for details and take appropriate action.
0002.3013 Unsupported content format for payload {0}. The module provides support for payload content as stream only
Explanation: The wm.ip.estd.as4.msh:submit service failed because part of the content provided in the partContent input parameter is not formatted correctly.
Action: Ensure that the content provided in the partContent input parameter is a stream.
0002.3017 {0} is a required input field. Specify a value for this field
Explanation: No value is set for the mandatory field specified in the error message.
Action: Define a value for the field specified in the error message.
0002.3018 One or more of the entries of partContent input passed to the 'submit' service is null
Explanation: One or more of the entries of the partContent parameter is missing input for the partInfo parameter.
Action: Ensure that input is specified for the partInfo parameter for each of the partContent entries.
0002.3020 An error in the input to the 'submit' service. The number of entries in the partContent and partInfo inputs do not match
Explanation: The number of entries in the partContent and partInfo are not the same.
Action: Ensure that the number of entries in the partContent and partInfo parameters are the same.
0002.3030 Encountered error while sending message using PModeID {0} with Part ID {1}. Compression of the SOAP body for the AS4 message is not supported.
Explanation: The AS4 message cannot be delivered as a SOAP body because the compression of the payload is enabled.
Action: Send the payload as an attachment or disable the compression.
0002.3031 Encountered error while sending message using PModeID {0}. PartInfo should not be empty if there are multiple partContent fields.
Explanation: The AS4 message cannot be delivered because partInfo is empty.
Action: Add partInfo for each of the partContent fields.
0003.3061 Compression type PMode ID mismatch for message Id {0} with payload ID {1}. Expected {2} but received {3}.
Explanation: There is compression type PMode ID mismatch due to unexpected behavior.
Action: Either update the TPA parameter payloadService>compressionType with the respective compression type or ask your partner to send the payload accordingly.