| Event Id | 12355 |
| Source | XLANG Scheduler |
| Description | The XLANG Scheduler engine was unable to load a required module.This may have been due to compilation/semantic errors with the module. |
| Event Information | "According to Microsoft: 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: 1. Start Registry Editor (Regedt32.exe). 2. Locate and click the following key in the registry: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0 3. On the Edit menu, click Add Key, and then add the following registry key to the registry: Key name: XLANG Scheduler 4. Locate and click the following key in the registry: \HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler 5. 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 6. 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 7. Quit Registry Editor. " |
| Reference Links | XLANG Errors Occur When You Run BizTalk Server under a High Load Condition |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.