Microsoft KB Archive/328887

= FIX: XLANG Scheduler May Indicate a Failed Condition in Cluster Administrator =

Article ID: 328887

Article Last Modified on 10/11/2005

-

APPLIES TO


 * Microsoft BizTalk Server 2000 Service Pack 2

-



This article was previously published under Q328887



SYMPTOMS
When BizTalk Server 2000 is running in a properly configured clustered environment, and you move a group from one node to the other, the XLANG Scheduler application may take a long time to go offline. Also, when the application does go offline, it indicates a failed condition in the Administration Microsoft Management Console (MMC) for the cluster. This condition can occur only if an Xlang Scheduler instance is running while the XLANG Scheduler is closing.



CAUSE
This problem occurs because when the XLANG Restart Service is shutting down, it creates an XLANG Scheduler System Manager object to call the ShutdownAll method. In the XLANG Scheduler process, the ShutdownAll method succeeds. However, during the shutdown of the XLANG Scheduler, the COM Services Information thread that is running in the XLANG Scheduler process fails when it tries to query the XLANG Restart Service. The error that is returned is 0x80010108 &quot;The object invoked has disconnected from its clients.&quot; This error is returned to the Service Control Manager and then to the Cluster Service.

When XLANG Scheduler returns an error to the Service Control Manager, this error causes the cluster Administrator to indicate a failed condition. When this occurs, it does not affect the action of moving the cluster group because the Cluster Service is trying to stop the XLANG Scheduler, anyway. Because the XLANG Scheduler will be stopped, the Cluster Service indicates the error, and then continues the group move.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Server service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date          Time    Version      Size     File name      Platform ---  18-Sep-2002   13:56   2.0.2003.0   28,944   Wfsvcmgr.exe   Intel



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB328887

-

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

© Microsoft Corporation. All rights reserved.