FIX: You can't use a nonstandard qualifier in identity and agreement for an EDIFACT Service schema extension in BizTalk Server

Symptoms

Assume that you implement an Electronic data interchange (EDI) exchange in Microsoft BizTalk Server. To use a nonstandard qualifier for your trading partner, you do the following:

• Create a new Visual Studio BizTalk project.

• Add the EDIFACT Service schema extension that's provided by BizTalk Server Setup.By default, this schema is saved in the following location:
  
  

  C:\Program Files\Microsoft BizTalk Server nnnn\XSD_Schema\EDINote In this path, nnnn is the version number of BizTalk Server that you have installed. The schema name is "Edifact_ServiceSchemaExtension.xsd."
  

• Open the schema, and then add the value that you want for the UNB2.2 and UNB3.2 segments. For example, add "ZZ" as the value.

• Deploy the schema.

• Create a new party recipient by using a new profile and a new identity, as follows:
  
  

  • Create a new identity by using custom enumeration ("ZZ," as specified in step 3).

  • Create an Agreement by using the newly created identity ("ZZ").

• Create a new party sender by using a new profile and a new identity.

• Create a new agreement between the two parties.

• In the agreement, set UNB2.2 and UNB3.2 as "ZZ."

In this situation, you may receive the following error message:

Resolution

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

References

For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.

For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and Service Pack support.