Microsoft KB Archive/822634

= Trading Partner Manager Does Not Correctly Populate the Interchange Control Version Number =

Article ID: 822634

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Accelerator for HIPAA 2.0 Standard Edition

-



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 hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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.

Additional query words:

Keywords: kbhotfixserver kbqfe kbhotfixserver kbqfe kbfix kbbug KB822634

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.