Microsoft KB Archive/889164

= FIX: The edi_datatype property is set to &quot;A&quot; when the value should be &quot;AN&quot; in BizTalk Server 2004 =

Article ID: 889164

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Standard Edition
 * Microsoft BizTalk Server 2004 Partner Edition
 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Service Pack 1

-





SYMPTOMS
In Microsoft BizTalk Server 2004, you may change the EDI Datatype property to &quot;String&quot; in an EDI schema in the XSD Editor that is in visual studio .NET 2003. If you do this, you may notice in the XSD view pane that the edi_datatype property is changed to &quot;A&quot; when it should be &quot;AN&quot;. Additionally, if you try to validate the schema after you make this change, you receive an error message that is similar to the following:

Description: BEG

Is wrongly defined in: Segment element datatype is not recognized



CAUSE
This problem occurs because &quot;A&quot; is not a valid EDI Datatype property (edi_datatype) in an EDI schema. Therefore, when you try to validate the EDI schema, the validation is unsuccessful.

Note When you change the EDI Datatype property to &quot;String&quot;, the EDI Schema Editor Extension sets the property to &quot;A&quot; when it should be &quot;AN&quot;.



Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

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

Prerequisites
To apply this hotfix, you must have Microsoft BizTalk Server 2004 Service Pack 1 installed on your computer.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) 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 ---  18-Nov-2004  22:48  4.0.1136.5       35,328  Compeif.exe 07-Oct-2003 00:21                  155,136  Edibtsmmc.msc 18-Nov-2004 22:47  4.0.1136.0       17,920  Edimmcresdll.dll 18-Nov-2004 22:47  4.0.1136.11     241,664  Edimmcsnapin.dll 18-Nov-2004 22:46  4.0.1136.198    851,968  Esp.dll 18-Nov-2004 22:46  4.0.1136.13     172,032  Esproxy.dll 18-Nov-2004 22:46  4.0.1136.23      81,920  Esp_btsoma.dll 18-Nov-2004 22:45  4.0.1136.25     118,784  Esp_cli.dll 18-Nov-2004 22:47  4.0.1136.2       22,016  Esp_err.dll 18-Nov-2004 22:48  4.0.1136.26      23,040  Esp_files.dll 18-Nov-2004 22:45  4.0.1136.49      86,016  Esp_gen.dll 18-Nov-2004 22:48  4.0.1136.28      23,040  Esp_sqlsrv2000.dll 18-Nov-2004 22:48  4.0.1136.25      23,552  Esp_srv.exe 18-Nov-2004 22:46  4.0.1136.186    372,736  Esp_trans.dll 18-Nov-2004 22:48  4.0.1136.16      33,280  Esp_voyager.dll 18-Nov-2004 22:48  4.0.1136.1      176,128  Genins.exe 18-Jun-2004 19:24                  488,650  Live.eif 23-Nov-2004 02:16  4.0.1136.0       65,536  Microsoft.biztalk.adapter.edi.common.dll 23-Nov-2004 02:16  4.0.1136.0      110,592  Microsoft.biztalk.adapter.edi.manager.dll 23-Nov-2004 02:16  4.0.1136.0       32,768  Microsoft.biztalk.adapter.edi.receiver.dll 23-Nov-2004 02:16  4.0.1136.0       49,152  Microsoft.biztalk.adapter.edi.resourcer.dll 23-Nov-2004 02:16  4.0.1136.0       20,992  Microsoft.biztalk.adapter.edi.sspi.dll 23-Nov-2004 02:16  4.0.1136.0       36,864  Microsoft.biztalk.adapter.edi.transmitter.dll 23-Nov-2004 02:16  4.0.1136.0       11,264  Microsoft.biztalk.extension.edi.errortext.dll 23-Nov-2004 02:16  4.0.1136.0      643,072  Microsoft.biztalk.extension.edi.hatplugin.dll 23-Nov-2004 02:16  4.0.1136.0       94,208  Microsoft.biztalk.extension.edi.schemaeditor.dll 18-Nov-2004 22:48  4.0.1136.5        7,680  Trigcon.exe 05-Feb-2004 18:25                       82  Updateedi.bat 07-Oct-2004 22:10                  578,312  Updateedi.sql 18-Nov-2004 22:47  4.0.1136.5      180,224  Validins.exe 18-Nov-2004 22:48  4.0.1136.35   1,347,584  Xsd2edi.exe Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Additional installation instructions
After you extract the package, follow these steps to install this hotfix:  Run the Setup program to install the main files. After the Setup program is finished, click Start, click Run, type the following command, and then click OK:



Note Replace  with the disk drive where BizTalk Server 2004 is installed. Manually copy the Genins.exe file from the extracted package location to the following folder:

\Program Files\Microsoft BizTalk Server 2004\EDI\Subsystem

 Restart the BizTalk Base EDI service.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_section">

Steps to reproduce the behavior

 * 1) Open an existing XML Schema or create a new XML Schema in visual studio .NET 2003.
 * 2) In the Properties pane, set the Schema Editor Extension property to Covast EDI Schema Editor Extension.
 * 3) Create a new Child Field Element, set the EDI Datatype property to Date, and then change the EDI Datatype property to String.

Note In the XSD view pane, note that the edi_datatype property has changed to &quot;A&quot; when it should be &quot;AN&quot;.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional query words: BTS2004

Keywords: kbbug kbfix kbqfe kbhotfixserver kbbiztalk2004-2006swept KB889164

-

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

© Microsoft Corporation. All rights reserved.