Tallan's Technology Blog

Tallan's Top Technologists Share Their Thoughts on Today's Technology Challenges

BizTalk EDI Invalid Control Standard Identifier ISA11

Kevin Morillo

A short and sweet post for this thursday morning.

While testing a HIPAA 834 Benefits Enrollment and Maintenance EDI Message for a client I came across an error translating the EDI message into an XML message using my EdiReceive pipline.  The ISA 11 value that was specified in the file was “{“.  However, I encountered a suspended message while receiving the message, specifying that:

An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:
Error: 1 (Miscellaneous error)
16: Invalid Control Standard Identifier
Error: 2 (Field level error)
SegmentID: ISA
Position in TS: 1
Data Element ID: ISA11
Position in Segment: 11
Data Value: {
7: Invalid code value.
The sequence number of the suspended message is 1.
An output message of the component "Unknown " in receive pipeline "Microsoft.BizTalk.Edi.DefaultPipelines.EdiReceive, Microsoft.BizTalk.Edi.EdiPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" is suspended due to the following error:      Error: 1 (Miscellaneous error)	16: Invalid Control Standard Identifier
Error: 2 (Field level error)	SegmentID: ISA	Position in TS: 1	Data Element ID: ISA11	Position in Segment: 11	Data Value: {	7: Invalid code value. The sequence number of the suspended message is 1.

Opening the agreement party settings in the Admin Console I verified that my ISA repetition seperator was correctly specified as “{“, however I continued to get this error!

What I did not realize, is that I failed to specify in my receive pipeline that my ISA11 value was supposed to be used as a repetition separator.  After opening my pipeline settings, and changing the “UseISA11AsRepetitionSeparator” to “True“, and resetting my host instances, all was well.

Related Articles

1 Comment. Leave new

Hi Kevin,

I am using EDI834 in BizTalk 2013R2. I tried the solution you mentioned, but still got the same error. Can you please post your thoughts on any other solution for this.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

\\\