PRB: Orchestration Schedules Generate Errors When Running on Clustered BizTalk Server (812421)
The information in this article applies to:
- Microsoft BizTalk Server 2002
SYMPTOMSWhen you run BizTalk Server on a cluster, and you use a
clustered XLANG Scheduler resource or a clustered Message Queuing (also known as MSMQ) resource,
you may receive error messages similar to the following in the
application log of the clustered BizTalk Server: | Event Type: | Error | | Event Source: | XLANG Scheduler | | Event Category: | WFBinding | | Event ID: | 23810 | | Date: | 1/7/2003 | | Time: | 2:44:17 PM | | User: | N/A | | Computer: | BIZTALKSERVER | | Description: | |
| The Message Queuing Service is not configured properly. A
queue object could not be opened Instance ID:
{59EE36F4-56FA-4A75-8F84-5705CCDAD348} Port name: CommonPO Queue path:
ServerName\private$\Queue MSMQ object error description: The
Message Queuing service is not available Error Code = 0xc00e000b : XLANG
Scheduler Engine Internals Information: File:
e:\bizet\private\sked\src\runtime\techbind\mq\queue\mqasyncqueue.cpp Line:
1380. |
-or- | Event Type: | Error | | Event Source: | XLANG Scheduler | | Event Category: | WFBinding | | Event ID: | 23809 | | Date: | 1/7/2003 | | Time: | 1:03:46 PM | | User: | N/A | | Computer: | BIZTALKSERVER | | Description: | |
| MQBinder: CreateChannel failed for: Instance ID:
{4AE18DF4-BACE-4C50-ADFC-099A7C1D375F} Port name: CommonPO Queue path:
ServerName\private$\Queue MSMQ object error description: The
queue pathname specified is invalid. Error Code = 0xc00e0014 : XLANG Scheduler
Engine Internals Information: File:
e:\bizet\private\sked\src\runtime\techbind\mq\queue\mqasyncqueue.cpp Line:
1390. |
These errors typically occur when an
XLANG Schedule tries to read from or write to a clustered Message Queuing queue or
when BizTalk Messaging tries to create an instance of an XLANG Schedule from the
clustered XLANG Scheduler resource. CAUSEThis problem may occur if the local instance of the
Message Queuing Service is running, or if any XLANG Scheduler COM+ applications are started
other than the clustered XLANG Scheduler resource.RESOLUTIONVerify that only the clustered instances of the XLANG
Scheduler application and the Message Queuing Service are running on the BizTalk Server
cluster.
To do this, follow these steps: - To verify that the local instance of the Message Queuing Service is
not running, open a command prompt on the computer running BizTalk Server, type the
following command, and then press ENTER:
- To verify that only the clustered XLANG Scheduler resource
is running on the BizTalk Server, follow these steps:
- Open the Cluster Administrator, and then take the XLANG
Scheduler Resource offline.
- Click Start, point to Programs, and then click Administrative Tools. Start the Component Services MMC Snap-in.
- Under My
Computer, expand the COM+ Applications folder.
- Right-click XLANG Scheduler COM+ Application, and
then select the option to Shut Down.
- In the
Cluster Administrator, bring the XLANG Scheduler Resource back online.
STATUS
This behavior is by design.
| Modification Type: | Major | Last Reviewed: | 1/10/2003 |
|---|
| Keywords: | kbprb kberrmsg KB812421 kbAudDeveloper |
|---|
|