Microsoft KB Archive/301508

= FIX: XLANG Errors Occur When You Run BizTalk Server under a High Load Condition =

Article ID: 301508

Article Last Modified on 9/30/2003

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Standard Edition

-



This article was previously published under Q301508



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
When the BizTalk Server is operating under a high load condition, error messages that are similar to the following may appear in the Application event log of your BizTalk Server:

Event Type: Error Event Source:  XLANG Scheduler Event Category: Engine Event ID:           12322 Date:      6/18/2001 Time:      1:45:51 PM User:       N/A Computer:           BIZTALKSERVER Description: The state of the schedule instance could not be saved to the database. Detailed information is provided in the following message.

Module name: Test Module ID: {B8139565-B637-4DA7-A8B4-13F009573418} Instance ID: {F52521A4-6355-48D9-9695-82B07DF35681} Database error(s): [Microsoft][ODBC SQL Server Driver]Timeout expired

Error Code = 0x80040e31 :

XLANG Scheduler Engine Internals Information: File: d:\bts\private\sked\src\runtime\persistence\persist.cpp Line: 263

-or-

Event Type: Error Event Source:  XLANG Scheduler Event Category: (3) Event ID:           12355 Date:      6/18/2001 Time:      1:27:39 PM User:       N/A Computer:           BIZTALKSERVER Description: The XLANG Scheduler engine was unable to load a required module. This may have been due to compilation/semantic errors with the module. Detailed information is available in the following message:

Error Description: [Microsoft][ODBC SQL Server Driver]Timeout expired

Module name: Test Module ID: {92625420-D282-4EEF-A92A-67775FE7E4BE} Instance ID: {6E0A19F5-4701-468E-8533-0A90FD824E15}



CAUSE
This error can be caused if the default ADO timeout period is exceeded when BizTalk is attempting 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 ActiveX Data Objects (ADO) Connection timeout and Command timeout for the XLANG Scheduler to 300 seconds (from the default of 60 seconds) by making the following Registry entries:

 Start Registry Editor (Regedt32.exe). Locate and 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 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

</li> 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.

Keywords: kbbug kbfix KB301508

-

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

© Microsoft Corporation. All rights reserved.