BizTalk 2010 AS2 Identifier with spaces RRS feed

  • Question

  • I have a trading partner that has spaces in their AS2 Identifier. When I try to create an agreement in BizTalk 2010 it tells me there are invalid characters in the AS2-To and AS2-From fields for the corresponding directions. We were able to work with this partner in Biztalk 2006 with no issue. Does anyone know if this is a limitation or if there is a workaround?
    Thursday, October 28, 2010 4:35 PM

All replies

  • hi Larry,

    I need to clarify what you mean when you said it worked with BizTalk 2006.  We didn’t have the current EDI engine with 2006.  So are you comparing to the Covast EDI Adapter or the full Accelerator?


    Just a quick check against AS2 standard.  Per AS2 RFC4130


    6.2.  AS2 System Identifiers


       To aid the receiving system in identifying the sending system,

       AS2-From and AS2-To headers are used.


              AS2-From: < AS2-name >

              AS2-To: < AS2-name >


       These AS2 headers contain textual values, as described below,

       identifying the sender/receiver of a data exchange.  Their values may

       be company specific, such as Data Universal Numbering System (DUNS)

       numbers, or they may be simply identification strings agreed upon

       between the trading partners.



          AS2-text = "!" /           ; printable ASCII characters

                     %d35-91 /       ; except double-quote (%d34)

                     %d93-126        ; or backslash (%d92)


          AS2-qtext = AS2-text / SP  ; allow space only in quoted text


          AS2-quoted-pair = "\" DQUOTE /  ; \" or

                           "\" "\"       ; \\


          AS2-quoted-name = DQUOTE 1*128( AS2-qtext /

                                          AS2-quoted-pair) DQUOTE


          AS2-atomic-name = 1*128AS2-text


          AS2-name = AS2-atomic-name / AS2-quoted-name


       The AS2-From header value and the AS2-To header value MUST each be an

       AS2-name, MUST each be comprised of from 1 to 128 printable ASCII

       characters, and MUST NOT be folded.  The value in each of these

       headers is case-sensitive.  The string definitions given above are in

       ABNF format [14].

    Regards, Imelda I
    Thursday, November 4, 2010 3:44 PM
  • I meant to say 2006R2
    Thursday, November 4, 2010 3:47 PM
  • Are you comparing to the Covast EDI Adapter or the full Accelerator?

    I guess this is the main question...


    Regards, Imelda I
    Thursday, November 4, 2010 3:58 PM
  • The full Accelerator
    Thursday, November 4, 2010 3:59 PM
  • Thank you, we will do further reseach and testing and will get back to you shortly.
    Regards, Imelda I
    Thursday, November 4, 2010 4:15 PM
  • Have you tried it with quotes? does that also fail?
    Regards, Imelda I
    Thursday, November 4, 2010 4:26 PM
  • Yes, that also fails.
    Thursday, November 4, 2010 4:27 PM
  • Hi Larry,


    I am sorry, we cannot provide you with a solution at this point.

    What we can for this issue, is to have you open a support case so, we can report this issue to the dev group. 

    Keep in mind that if we can prove that the issue is a bug its free to you.   

    Please visit the below link to see the various paid support options that are available to better meet your needs. http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone

    Regards, Imelda I
    Friday, November 5, 2010 4:14 PM