Microsoft KB Archive/894919

From BetaArchive Wiki

Article ID: 894919

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



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:

256986 Description of the Microsoft Windows Registry


SYMPTOMS

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:

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'

Note In this error message, FullPathandFileName is the full path name and file name of your custom EDI schema.

RESOLUTION

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:

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:

Prerequisites

Microsoft BizTalk Server 2004 Service Pack 1 is required.

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
   -------------------------------------------------------------
   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 instructions

To install this hotfix, follow these steps:

  1. Run the Setup.exe file.
  2. Restart the BizTalk Base EDI service.
  3. Manually copy the Genins.exe file to your EDI\Subsystem folder.
  4. Start the BizTalk service.
  5. Start the BizTalk Base EDI service.
  6. At a command prompt, run the following command:

    COMPEIF.EXE

  7. Restart the BizTalk Base EDI service.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EDI Subsystem for Microsoft BizTalk Server\4.0\DatabaseDeleteTimeOut


To do this, follow these steps.

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.

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EDI Subsystem for Microsoft BizTalk Server\4.0

  3. On the Edit menu, click New, and then click DWORD Value.
  4. Type DatabaseDeleteTimeOut, and then press ENTER.
  5. Right-click DatabaseDeleteTimeOut, and then click Modify.
  6. In the Edit DWORD Value dialog box, click Decimal, and then type the value that you want for the timeout value in seconds.

    Note For example, to enter a value of 5 minutes, type 300 as the decimal value.
  7. On the File menu, click Exit.

For more 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 kbprb kbbiztalk2004presp2fix kbhotfixserver KB894919