Trading Partner Manager Does Not Correctly Populate the Interchange Control Version Number (822634)


The information in this article applies to:

  • Microsoft BizTalk Server Accelerator for HIPAA 2.0

SYMPTOMS

After you create a new trading partner relationship by using the Trading Partner Manager (TPM) in Microsoft BizTalk Accelerator for HIPAA 2.0, the interchange control version number of the envelope properties may not be populated with the correct value. Sometimes it may not be populated at all.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. 
   Date         Time   Version     Size     File name
   ---------------------------------------------------
   19-Jun-2003  18:54  2.2.0.2185  356,449  A4htpm.dll
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

This problem occurs because the TPM looks in the Description element of the inbound schema definition to populate the envelope properties. The problem may occur if you are using a CUSTOM inbound schema that has no Description element text. The hotfix in this article changes the behavior of the TPM to search the outbound schema for the relevant envelope properties.
Modification Type:MinorLast Reviewed:10/26/2005
Keywords:kbHotfixServer kbQFE kbHotfixServer kbQFE kbfix kbbug KB822634
©2004 Microsoft Corporation. All rights reserved.