Knowledge Base

FIX: BizTalk Cluster Encounters a Runtime Failure

Article ID: 293343

Article Last Modified on 9/26/2005

APPLIES TO

Microsoft BizTalk Server 2000 Standard Edition

This article was previously published under Q293343

SYMPTOMS

When you run an XLANG schedule that sends and retrieves a document from a private queue, the XLANG Scheduler may generate a runtime error when BizTalk Server attempts to create the queue. When this occurs, an error similar to the following may occur in the Application event log:

Event Type: Error
Event Source:   XLANG Scheduler
Event Category: WFBinding
Event ID:   23809
Date:       10/25/2000
Time:       3:02:39 PM
User:       N/A
Computer:   SAMPSERVER
Description:
MQBinder: CreateChannel failed for: 
Instance ID: {372A34EE-0162-4E7B-B201-87BE1D2DA1F5}
Port name: Port_1
Queue path:SAMPSERVER\Private$\Port_1{97A73983-D6BD-4EF8-9392-E32640A87761}
MSMQ object error description: The  queue pathname specified is invalid.
Error Code = 0xc00e0014

CAUSE

The XLANG Scheduler does not configure the Microsoft Message Queuing (MSMQ) private or public queue as a cluster resource. Not only does this cause a problem when you attempt to create the MSMQ queue, but also when you try to run a BizTalk COM+ application on the virtual server because the MSMQ resource does not belong to the virtual server. All private queues are being created on the node and not on the virtual server.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 1.

Keywords: kbbug kbfix kbbiztalk2000sp1fix kbqfe kbhotfixserver KB293343

Microsoft KB Archive/293343

Contents