Home Library Learn Samples Downloads Support Community Forums
MSDN Library
Servers and Enterprise Development
BizTalk Server
BizTalk Server 2009
Microsoft BizTalk Server 2009 Help
Technical Reference
Events and Errors
EDI and AS2 Events and Errors
EDI and AS2 Events
A BTS MIME error was encountered when attempting to decode an AS2 message. AS2-From: {0}, AS2-To: {1}, MessageId: {2}, Error: {3}
A failure occurred in processing Edifact message on send port: No agreement for receiver and sender identifier/qualifier pairs
A failure occurred in processing Edifact message on send port: No agreement for receiver and sender identifier/qualifier pairs and no party with name
A failure occurred in processing Edifact message on send port: No Party with name
A failure occurred in processing X12 message on send port: No agreement for receiver and sender identifier/qualifier pairs
A failure occurred in processing X12 message on send port: No agreement for receiver and sender identifier/qualifier pairs and no party with name
A failure occurred in processing X12 message on send port: No Party with name
A persistence exception has occurred during the batch submission in the batching Orchestration
A single Edifact message could not be serialized because a segment had an invalid character
Acknowledgement generation has failed as maximum limit of Edifact transaction set control number has been reached for global settings
Acknowledgement generation has failed as maximum limit of Edifact transaction set control number has been reached for party settings
Acknowledgement generation has failed as maximum limit of X12 transaction set control number has been reached for global settings
Acknowledgement generation has failed as maximum limit of X12 transaction set control number has been reached for party settings
An AS2 message was received that did not contain the AS2-From header
An AS2 message was received that did not contain the AS2-To header
An empty AS2 message was received and suspended
An End Element could not be found at depth
An End Element was found while looking for Start Element
An error occurred when decrypting an AS2 message
An error occurred when validating an AS2 message
An exception has occurred during the batch submission in the batching orchestration
An exception has occurred during the execution of the routing orchestration
An exception has occurred during the execution of the upgrade batch orchestration
An invalid quoted HTTP header encountered
AS2 decoding failed while decrypting a message
Based on the specified delimiter set, no valid Date value could be generated
Based on the specified delimiter set, no valid Digit could be found
Based on the specified delimiter set, no valid ID could be generated
Based on the specified delimiter set, no valid Time value could be generated
Batch message cannot be serialized as there is no party associated with send port
BizTalk Business Activity Monitoring has not been configured for EDI/AS2 status reporting
Character set not supported because the encoding information in UNB1.1 does not match the actual encoding
Component cannot repeat because it has an invalid repetition count
Conditional required data element missing
Configuration error. Synchronous MDN requested on a one way HTTP receive Port
Configuration error. Synchronous MDN requested on one way HTTP send port
Configuration error. The message encryption doesn't match the expected value
Configuration error. The message signature doesn't match the signature configured for this party
Configuration error. The message signing doesn't match the expected value.
Control Number in ISA and IEA do not match
Control schema should have header segments in the correct order
Could not get the database or the server names
Cross field validation rule violated
Data element too long
Data element too short
Decompression failed while processing a compressed AS2 message.
Delimiter set could not be read from the interchange
Delimiters are not unique
Delimiters are not unique, field and component separator are the same
Delimiters are not unique, field and segment separator are the same
Delimiters are not unique, segment and component separators are the same
Disposition-Notification-Option is invalid
Doctype is invalid
Document spec type not found
Duplicate Control Number
Duplicate group control number found
During serialization root node is not placed at start element
Edifact interchange should have contained UNA or UNB as the first segment
Edifact interchange should have contained TransactionSetGroup or FunctionalGroup Xml tags
Edifact interchange Xml serialization failed due to invalid structure, no FunctionalGroup or ServiceSchema
Edifact interchange Xml serialization failed due to invalid structure, no transactionSet or UNE
Error encountered after processing Transaction Set(s) because DocType was not set
Error encountered after processing Transaction Set(s) because the Start element of a Transaction set could not be found
Error encountered during instance generation--field can repeat but repetition delimiter has not been defined
Error encountered during parsing. The Edifact functional group in interchange had the following errors
Error encountered during parsing. The Edifact interchange had the following errors
Error encountered during parsing. The Edifact interchange which did not contain a group had the following errors
Error encountered during parsing. The Edifact transaction set contained in functional group is being suspended with following errors
Error encountered during parsing. The Edifact transaction set contained in interchange (without group) is being suspended with following errors
Error encountered during parsing. The X12 functional group in the interchange had the following errors
Error encountered during parsing. The X12 interchange had the following errors
Error encountered during parsing. The X12 transaction set contained in functional group is being suspended with following errors
Error encountered during serialization. The Edifact functional group had the following errors
Error encountered during serialization. The Edifact interchange had the following errors
Error encountered during serialization. The Edifact interchange which did not contain a group had the following errors
Error encountered during serialization. The Edifact transaction set contained in functional group is being suspended with following errors
Error encountered during serialization. The Edifact transaction set contained in interchange (without group) is being suspended with following errors
Error encountered during serialization. The X12 functional group had the following errors
Error encountered during serialization. The X12 interchange had the following errors
Error encountered during serialization. The X12 transaction set contained in functional group is being suspended
Error encountered in reading delimiters from ISA data
Exclusion Condition Violated
Fatal error encountered in EDI Disassembler
Field separator not found after segment tag id
Functional Group Version Not Supported
Group control number in GS and GE do not match
Group control number violates syntax
Invalid Adler32 checksum encountered
Invalid AS2-From header received
Invalid AS2-From name configured for Party
Invalid AS2-From name encountered during processing
Invalid AS2-To header received
Invalid AS2-To name configured for Party
Invalid AS2-To name encountered during processing
Invalid ASN.1 compressed structure encountered during decompression processing
Invalid ASN.1 ZLib compression field encountered during decompression processing
Invalid Authorization Qualifier
Invalid Authorization Value
Invalid character in data element
Invalid Component Element Separator
Invalid Control Number Value
Invalid Control Standard Identifier
Invalid Control Structure
Invalid Data Element Separator
Invalid Date
Invalid delimiter set because at least one of the delimiters is outside the allowed range
Invalid Interchange Content
Invalid or missing ASN.1 Compressed Data OID encountered during decompression processing
Invalid or missing ASN.1 compressed header encountered during decompression processing
Invalid or missing ASN.1 Data Length field encountered during decompression processing
Invalid or missing ASN.1 Data OID encountered during decompression processing
Invalid or missing ASN.1 ZLib OID encountered during decompression processing
Invalid or missing trailing ASN.1 CMS compressed structure bytes during decompression processing
Invalid ReceiverId
Invalid ReceiverId Qualifier
Invalid Security Qualifier
Invalid Security Value
Invalid Segment Terminator
Invalid SenderId
Invalid SenderId Qualifier
Invalid Test Indicator Value
Invalid Time
Invalid Version Identifier
Invalid VersionId
ISA segment needs to have a minimum length of 108
Loop Occurs Over Maximum Times
Loop repeats less than the minimum allowed number of times
Mandatory data element missing
Mandatory Segment Missing
Max limit of acceptable Edifact functional group control number has reached for Guest settings
Max limit of acceptable Edifact functional group control number has reached for party
Max limit of acceptable Edifact interchange control number has reached for Guest settings
Max limit of acceptable Edifact interchange control number has reached for party
Max limit of acceptable Edifact transaction set control number has reached for Guest settings
Max limit of acceptable Edifact transaction set control number has reached for party
Max limit of acceptable X12 functional group control number has reached for Guest settings
Max limit of acceptable X12 functional group control number has reached for party
Max limit of acceptable X12 interchange control number has reached for Guest settings
Max limit of acceptable X12 interchange control number has reached for party
Max limit of acceptable X12 transaction set control number has reached for Guest settings
Max limit of acceptable X12 transaction set control number has reached for party
Message cannot be serialized as the schema could not be located
Message did not contain UNA and pipeline property for delimiters was incorrect format
Missing or invalid or duplicate Transaction set identifier
Missing or invalid transaction set control number
Missing or invalid Transaction set identifier
No matching transform found for DocType in Send Port
Number of included groups do not match
Number of included segments do not match
Number of included transaction sets do not match
One or more segments in error
Receipt-Delivery-Option value is invalid
Repeats less than required
Repeats more than required
Scheduler was unable to schedule the batch
Schema not found for CLR Namespace and rootName
Schema should have segments in the following order ST .... SE
Segment Exceeds Maximum Use Description
Segment has data element errors
Segment has trailing delimiter(s) at component or sub-component level
Segment Not In Defined Transaction set
Segment Not In Proper Sequence
Segment repeats less than the minimum allowed number of times
Segment should have a name with at least two characters
Structural error encountered during serialization of an interchange XML message
TA1 segment found after a functional group
The AS2 Decoder encountered an exception during processing
The AS2 Decoder failed processing because the MDN indicated the AS2 message failed processing
The AS2 Decoder failed processing because the MDN signing did not match our request
The AS2 Decoder failed processing when validating the MIC value returned in the MDN
The AS2 Decoder was unable to locate the Disposition-Notification-Options HTTP header
The batch element exceeded the maximum configured character count
The batch element is being suspended as it failed validation
The batch settings for party have expired and the batching orchestration is being terminated
The boolean property value is not valid
The byte property value is not valid
The certificate used for signing a message cannot be located in the local certificate store
The certificate used for signing a message has been revoked
The certificate used to decrypt a message has been revoked
The certificate used to encrypt a message has been revoked
The comparison operator is not valid
The double property value is not valid
The EDIFACT acknowledgement was generated by the system. However, it is missing a context property for Delimiter Set. It cannot be serialized
The Edifact Transaction set had a mismatched count in UNT01
The element has an invalid structure
The first element of the batch exceeded the character count release criteria set
The float property value is not valid
The group receiver settings are not configured for party
The hash algorithm specified in the AS2 message is unsupported
The integer property value is not a valid integer
The interchange contained a malformed ISA or the Service schema was not available
The interchange had a structural error in/before the first functional group
The interchange had structural error. A likely cause is invalid segment terminator due to missing Carriage Line and/or Line Feed seperators
The interchange had structural error. Last structurally valid functional group ID was:
The interchange had structural error. The part after the error is being suspended
The loop contains a leaf node. It can only contain other Loops or Segments
The message cannot be routed to the batching orchestration as the Encoding type could not be determined
The party for this AS2 interchange must contain a value for AS2-From
The TA1 contained in interchange had the following errors
The party for this AS2 interchange must contain a value for AS2-To
The property name is not a valid string
The property value is not a valid string
The schema does not contain the root element
The Signing Certificate has not been configured for AS2 party
The value cannot be empty or null for an operator other than Exists
The X12 Transaction set had a mismatched count in SE01
There are no batch elements to send and an empty message cannot be sent as it is not configured for party
There are no batch elements to send for party
There was an authentication failure
This instance is outside the Batching Service window for the partner
This scheduler was unable to schedule the batch
To enable status reporting, run 'BizTalk Server Configuration' and configure EDI/AS2 status reporting feature
Too few data elements found
Too many data elements
Transaction Set Control Number Mismatch
Transaction Set duplicate control number found
Transaction Set Not Supported
Transaction set schema contains one or more of control segments ISA, IEA, GS, GE
Transaction Set Trailer Missing
UNA segment is invalid. It did not contain 6 fields
Unable to access party using party
Unable to access party using qualifier
Unable to access party using send port
Unable to create the entry in the AS2 EDIINT MIC table
Unexpected segment
Unrecognised message type
Unrecognized segment ID
X12 interchange Xml serialization failed due to invalid structure. Looking for TransactionSet or GE, but not found
X12 Message cannot be serialized due to invalid party configuration
Expand Minimize
This topic has not yet been rated - Rate this topic

An empty AS2 message was received and suspended

Details

 

Product Name

BizTalk Server

Product Version

3.6

Event ID

-

Event Source

BizTalk Server EDI

Component

AS2 Engine

Symbolic Name

-

Message Text

An empty AS2 message was received. The message will be suspended.

Explanation

This Error/Warning/Information event indicates BizTalk Server could not process the incoming AS2 message because the message does not contain a body. The body must be separated from the headers by two carriage return/line feeds.

User Action

To resolve this error, do the following:

  • Ensure the sending party adds a body (separated from the headers by two carriage return/line feeds) to the AS2 message before sending it.

Did you find this helpful?
(1500 characters remaining)

Community Additions

ADD
© 2013 Microsoft. All rights reserved.
|
Site Feedback
© 2013 Microsoft. All rights reserved.