When you attempt to run an XLANG Schedule on a computer running BizTalk Server, the following error may occur in the Application log:
Event Type: Error
Event Source: BizTalk Server
Event Category: Document Processing
Event ID: 324
Date: 4/12/2001
Time: 4:43:06 PM
User: N/A
Computer: BizTalkServer
Description:
An error occurred in BizTalk Server.
Details:
------------------------------
Failed to load the MSMQ runtime (MQRT.DLL)
The server encountered a transport error while processing
the messaging port "Test", which uses a transport component
with a ProgID of "BizTalk.BPOActivation.1".
All retry transmissions failed.
The specified module could not be found.
The server could not finish processing messaging port "Test".
Suspended Queue ID: "{B773BC8C-8FE4-4129-82FE-0661EF9AF077}"
The specified module could not be found.
In some circumstances, the Microsoft BizTalk Server XLANG Scheduler application may access violate and generate an error with a description that is similar to the following:
ERROR:
***********
A COM+ internal exception occurred. Contact Microsoft Product Support
Services to report this error, and provide them with the information
in the following message.
Exception: C0000005
Address: 0x1000501C
Call stack:
BTSShim + 0x501C
SkedCore + 0x17A400
SkedCore + 0x1793A9
SkedCore + 0x173820
SkedCore + 0x172A3C
SkedCore + 0x12D20B
SkedCore + 0xF8FF5
SkedCore + 0x7E5E8
SkedCore + 0x540F7
SkedCore + 0x7F992
SkedCore + 0x7E323
SkedCore + 0xBD1E3
SkedCore + 0xBA8A1
SkedCore + 0x540F7
SkedCore + 0xBC8FF
SkedCore + 0x8933C
SkedCore + 0x86A83
SkedCore + 0x540F7
SkedCore + 0x88AC9
SkedCore + 0x8CFFD
SkedCore + 0x8A1EE
SkedCore + 0x5425C
SkedCore + 0x541F0
ntdll!RtlSetThreadPoolStartFunc + 0x124 ntdll!RtlSetThreadPoolStartFunc +
0x5C7 KERNEL32!TlsSetValue + 0xF0