Microsoft KB Archive/317774

= BUG: SQL Server Generates &quot;Unspecified Error&quot; and &quot;Timeout&quot; Errors =

Article ID: 317774

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q317774



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
The Microsoft SQL Server computer that hosts the Microsoft BizTalk Server XLANG database may generate &quot;Unspecified Error&quot; and &quot;Timeout&quot; errors. Additionally, error messages that are similar to the following are generated in the BizTalk Server Application log:

The state of the XLANG schedule instance could not be saved to the

database. Detailed information is provided in the following message.

Module name: mymodule

Module ID: {EE8FB9FA-AB64-492A-A127-56A1EFDB2C50}

Instance ID: {6B48FF17-791B-474F-8EE2-AD35FF8E5A30}

Database error(s):

Error Code = 0x8004e007 : You made a method call on a COM+ component that

has a transaction that has already committed or aborted.

XLANG Scheduler Engine Internals Information:

File: d:\bts\private\sked\src\runtime\persistence\persist.cpp

Line: 261

Error 2:

An error was encountered while attempting to persist an XLANG schedule

instance. Detailed information is provided in the following message.

Error source: Field name: __Correlation__

HRESULT: 0x80040e14

Module name: mymodule

Module ID: {EE8FB9FA-AB64-492A-A127-56A1EFDB2C65}

Instance ID: {6FE02E74-7FE2-401B-93F3-EC208636257B}

Error Code = 0x80040e14



CAUSE
These errors may occur if the default ActiveX Data Objects (ADO) timeout period is exceeded when BizTalk Server is trying to persist the schedule to the XLANG database.



RESOLUTION
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.

Increase the ADO connection timeout and command timeout values for the XLANG Scheduler to 300 seconds (from the default of 60 seconds) by making the following modifications to the registry:  Start Registry Editor (Regedt32.exe). Locate, and then click the following key in the registry:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0

 On the Edit menu, click Add Key, and then add the following registry key to the registry:

Key name: XLANG Scheduler

 Locate, and then click the following key in the registry:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler

 On the Edit menu, click Add Value, and then add the following registry values to increase the ADO connection timeout value for XLANG:

Value name: ADOConnectionTimeout

Data type: REG_DWORD

Radix: Decimal

Value data: 300

 On the Edit menu, click Add Value, and then add the following registry values to increase the ADO command timeout value for XLANG:

Value name: ADOCommandTimeout

Data type: REG_DWORD

Radix: Decimal

Value data: 300

</li> Quit Registry Editor.</li></ol>

<div class="status_section">

STATUS
This behavior is by design.

<div class="moreinformation_section">

MORE INFORMATION
SQL Server may generate &quot;Unspecified Error&quot; and &quot;Timeout&quot; error messages under the following conditions:
 * You have installed BizTalk Server 2000 Service Pack 1a (SP1a) on a computer that is running Microsoft Windows 2000 SP1 or later.
 * The BizTalk Server databases are hosted on SQL Server 2000.
 * There are connections to SQL Server through a trusted connection using SQL Authentication.
 * SQL Server has connections to it from local and remote computers.
 * There are single-processor and multiple-processor computers.

These errors cause running schedules to fail when they are trying to persist to the database.

Keywords: kbbug kbfix KB317774

-

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

© Microsoft Corporation. All rights reserved.