Event ID 24 is logged and you receive parse error messages or translation error messages when you create a document interchange by using the BizTalk Accelerator for HIPAA version 3.0

When you create a document interchange by using the Microsoft BizTalk Accelerator for HIPAA version 3.0, you may receive parse error messages or translation error messages. In this scenario, an event that is similar to the following is logged in the Application log on the computer that is running Microsoft BizTalk Server 2004:

Event Type: Error
Event Source: HIPAA EDI Subsystem
Event Category: BizTalk Server 2004
Event ID: 24
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: Error encountered: ERROR (33), interchange 10018 :
The time format is not valid. Contact the sender.
source format: [5 00401 ,X12-4010]
source document: [(unknown)]
source segment: [data#0,def#3,tag=GS ,name=Functional Group Header]
source element: [def#5,elm#5,comp#0,tag=337,name=Time], value: [14445271], incorrect length. Time of type [TS] must be formatted as [HHMM[SS]] (seconds are optional) (msgnr:0 segnr:0)(line:2 pos:37 filepos:144)

Note You experience this problem even though you have a correct time value according to the Health Insurance Portability and Accountability Act of 1996 (HIPAA) documentation that describes the Time field. This documentation contains the following information:

This problem occurs if your HIPAA document has a time value that contains decimal seconds. For example, this problem occurs if your document contains a time value that is in the following format: According to the HIPAA documentation about the Time field, this time format is correct. However, this time format causes parse errors or translation errors in the BizTalk Accelerator for HIPAA version 3.0. If you use a time format of HHMMSS, your document is processed successfully.

This problem occurs because the BizTalk Accelerator for HIPAA version 3.0 Microsoft SQL Server 2000 tables contain an incorrect definition of the HIPAA TM data type.

To work around this problem, run the following SQL statement in SQL Query Analyzer against the BizTalkHIPAA_EDIDb database:

Microsoft has confirmed that this is a problem in BizTalk Server Accelerator for HIPAA version 3.0.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base: The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.