FIX: BizTalk Messaging Service Does Not Process the Document Instances in BizTalk Server Accelerator for HIPAA 2.0 (822013)



The information in this article applies to:

  • Microsoft BizTalk Server Accelerator for HIPAA 2.0

SYMPTOMS

BizTalk Messaging Service may not successfully process Health Insurance Portability and Accountability Act of 1996 (HIPAA) documents. When you try to validate the document instance against the XML schema by using BizTalk Editor, you may receive the following error message:
The XML document has failed validation for the following reason:

Attribute '<AttributeName>' has an invalid value according to the DTD/Schema.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next update that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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 hotfix 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     Size    File name
   ----------------------------------------------------------------------
   23-Apr-2003  00:44   153,917  835_v1_wpc_multiple.xml
   23-Apr-2003  00:49   162,429  835_v1_wpc_multiple_env.xml
   23-Apr-2003  00:41   153,883  835_v1_wpc_single.xml
   23-Apr-2003  00:54   162,395  835_v1_wpc_single_env.xml
   23-Apr-2003  01:35   643,300  837institutional_v1_wpc_multiple.xml
   23-Apr-2003  01:37   651,812  837institutional_v1_wpc_multiple_env.xml
   23-Apr-2003  01:33   643,203  837institutional_v1_wpc_single.xml
   23-Apr-2003  01:32   651,715  837institutional_v1_wpc_single_env.xml
   23-Apr-2003  01:29   558,593  837professional_v1_wpc_multiple.xml
   23-Apr-2003  01:19   567,105  837professional_v1_wpc_multiple_env.xml
   23-Apr-2003  01:25   558,496  837professional_v1_wpc_single.xml
   23-Apr-2003  01:14   567,008  837professional_v1_wpc_single_env.xml
   22-Apr-2003  18:58    95,858  270_v1_wpc.xml
   22-Apr-2003  18:50   104,370  270_v1_wpc_env.xml
   22-Apr-2003  22:49   153,806  271_v1_wpc.xml
   22-Apr-2003  20:01   162,318  271_v1_wpc_env.xml
   22-Apr-2003  23:48   227,470  278request_v1_wpc.xml
   23-Apr-2003  00:13   235,982  278request_v1_wpc_env.xml
   23-Apr-2003  00:18   236,909  278response_v1_wpc.xml
   23-Apr-2003  00:31   245,421  278response_v1_wpc_env.xml
   22-Apr-2003  16:53   162,513  835_v2_wpc_multiple.xml
   22-Apr-2003  16:49   162,479  835_v2_wpc_single.xml
   22-Apr-2003  18:05   628,906  837institutional_v2_wpc_multiple.xml
   22-Apr-2003  18:03   628,809  837institutional_v2_wpc_single.xml
   22-Apr-2003  17:49   557,425  837professional_v2_wpc_multiple.xml
   22-Apr-2003  17:41   557,328  837professional_v2_wpc_single.xml
   23-Apr-2003  01:49   103,801  270_v2_wpc.xml
   22-Apr-2003  16:16   161,837  271_v2_wpc.xml
   22-Apr-2003  16:27   250,846  278request_v2_wpc.xml
   22-Apr-2003  16:31   295,805  278response_v2_wpc.xml                                   

STATUS

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

Modification Type:MinorLast Reviewed:10/25/2005
Keywords:kbHotfixServer kbQFE kberrmsg kbfix kbQFE KB822013 kbAudDeveloper