Article ID: 894919 - View products that this article applies to.
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/ )Description of the Microsoft Windows Registry
In Microsoft BizTalk Server 2004, when you try to compile a BizTalk Server project that contains an Electronic Data Interchange (EDI) schema in Microsoft Visual Studio .NET 2003, the compilation is unsuccessful and you receive an error message that is similar to the following:
Note In this error message, FullPathandFileName is the full path name and file name of your custom EDI schema.
FullPathandFileName.xsd Can not execute DELETE FROM dbo.codset WHERE envr LIKE '%850\_004010\_DEFAULT\_X\_%' ESCAPE '\'Timeout expired
FullPathandFileName.xsd Error in inserting document definition: Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__codset__2D27B809'. Cannot insert duplicate key in object 'codset'
FullPathandFileName.xsd Error in inserting document definition: Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__elmnts__145C0A3F'. Cannot insert duplicate key in object 'elmnts'
FullPathandFileName.xsd Error in inserting document definition: Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__segcon__30F848ED'. Cannot insert duplicate key in object 'segcon'
FullPathandFileName.xsd Error in inserting document definition: Error = [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY constraint 'PK__sgmnts__164452B1'. Cannot insert duplicate key in object 'sgmnts'
A supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesMicrosoft BizTalk Server 2004 Service Pack 1 is required.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 ------------------------------------------------------------- 08-Mar-2005 18:43 4.0.2140.5 35,328 Compeif.exe 03-Feb-2005 18:43 897,916 Edi.sql 07-Oct-2003 00:21 155,136 Edibtsmmc.msc 08-Mar-2005 18:43 4.0.2140.0 17,920 Edimmcresdll.dll 08-Mar-2005 18:43 4.0.2140.11 241,664 Edimmcsnapin.dll 08-Mar-2005 18:43 4.0.2140.198 851,968 Esp.dll 08-Mar-2005 18:43 4.0.2140.13 172,032 Esproxy.dll 08-Mar-2005 18:42 4.0.2140.23 81,920 Esp_btsoma.dll 08-Mar-2005 18:42 4.0.2140.25 118,784 Esp_cli.dll 08-Mar-2005 18:43 4.0.2140.2 22,016 Esp_err.dll 08-Mar-2005 18:43 4.0.2140.26 23,040 Esp_files.dll 08-Mar-2005 18:42 4.0.2140.49 86,016 Esp_gen.dll 03-Feb-2005 18:38 3,002 Esp_ini.template 08-Mar-2005 18:43 4.0.2140.28 23,040 Esp_sqlsrv2000.dll 08-Mar-2005 18:43 4.0.2140.25 23,552 Esp_srv.exe 08-Mar-2005 18:42 4.0.2140.187 372,736 Esp_trans.dll 08-Mar-2005 18:43 4.0.2140.16 33,280 Esp_voyager.dll 08-Mar-2005 18:44 4.0.2140.1 176,128 Genins.exe 03-Feb-2005 18:39 12,362 Grants.sql 18-Jun-2004 19:24 488,650 Live.eif 10-Mar-2005 21:08 4.0.2140.0 65,536 Microsoft.biztalk.adapter.edi.common.dll 10-Mar-2005 21:08 4.0.2140.0 110,592 Microsoft.biztalk.adapter.edi.manager.dll 10-Mar-2005 21:08 4.0.2140.0 32,768 Microsoft.biztalk.adapter.edi.receiver.dll 10-Mar-2005 21:08 4.0.2140.0 49,152 Microsoft.biztalk.adapter.edi.resourcer.dll 10-Mar-2005 21:08 4.0.2140.0 20,992 Microsoft.biztalk.adapter.edi.sspi.dll 10-Mar-2005 21:08 4.0.2140.0 36,864 Microsoft.biztalk.adapter.edi.transmitter.dll 10-Mar-2005 21:08 4.0.2140.0 11,264 Microsoft.biztalk.extension.edi.errortext.dll 10-Mar-2005 21:08 4.0.2140.0 643,072 Microsoft.biztalk.extension.edi.hatplugin.dll 10-Mar-2005 21:08 4.0.2140.0 94,208 Microsoft.biztalk.extension.edi.schemaeditor.dll 07-Oct-2003 13:12 18,904 Receivehandler.xsd.tmpl 15-Feb-2005 22:08 148,864 Receivelocation.xsd.tmpl 07-Oct-2003 12:47 9,870 Sendhandler.xsd.tmpl 15-Feb-2005 22:06 193,134 Sendporttransport.xsd.tmpl 08-Mar-2005 18:43 4.0.2140.5 7,680 Trigcon.exe 05-Feb-2004 18:25 82 Updateedi.bat 07-Oct-2004 22:10 578,312 Updateedi.sql 08-Mar-2005 18:43 4.0.2140.5 180,224 Validins.exe 08-Mar-2005 18:44 4.0.2140.60 696,320 Xsd2edi.exe
Installation instructionsTo install this hotfix, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix increases the default timeout value from 30 seconds to 30 minutes. Additionally, this hotfix introduces a new registry entry that lets you change the default timeout value to a value that you specify in the registry entry. To change the default timeout value, you must add the following registry entry:
To do this, follow these steps.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EDI Subsystem for Microsoft BizTalk Server\4.0\DatabaseDeleteTimeOut
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 894919 - Last Review: November 15, 2007 - Revision: 2.7
Contact us for more help
Connect with Answer Desk for expert help.