BUG: Configuring Data Source Name for More Than One XLANG Schedule Host at a Time Causes COM+ Explorer to Stop Responding (312730)


The information in this article applies to:

  • Microsoft BizTalk Server 2000
  • Microsoft BizTalk Server 2002
This article was previously published under Q312730

SYMPTOMS

If you try to start the ODBC Data Source Administrator for more than one XLANG Schedule host simultaneously from the same Microsoft Management Console (MMC) interface, the COM+ Explorer experiences a deadlock condition and it stops responding.

CAUSE

This deadlock condition occurs when two threads with two separate window handles launch the ODBC SQLManageDataSources function in the same MMC.exe process.

RESOLUTION

To work around this issue:
  • Complete the configuration for the first COM+ XLANG application before you start the configuration for another COM+ XLANG application.
  • If you need to be able to configure two COM+ applications that host XLANG Schedules concurrently, you must do this from two separate instances of the COM+ Explorer MMC interface.

STATUS

Microsoft has confirmed that this is a problem in Microsoft BizTalk Server 2002.

MORE INFORMATION

You have to configure COM+ Applications that host XLANG Schedules with a data source name (DSN) to point to the XLANG Schedule persistence database. To configure the DSN for a COM+ Application that hosts XLANG Schedules, you must launch the ODBC Data Source Administrator by clicking the Configure DSN button on the XLANG tab from the Properties page of the COM+ Application.

Steps to Reproduce the Behavior

  1. Launch the COM+ Explorer MMC interface.
  2. Expand the COM+ Applications folder under My Computer, right-click the COM+ Application that is a host for XLANG Schedules, and then click Properties.
  3. On the XLANG tab, click to select the This application is a host for XLANG schedule instances check box, and then click Configure DSN.
  4. Repeat steps 2 and 3 for another COM+ Application that hosts XLANG Schedules.
  5. The MMC becomes deadlocked and you have to use Task Manager to quit the MMC.
Modification Type:MajorLast Reviewed:6/4/2003
Keywords:kbbug kbnofix KB312730
©2002 Microsoft Corporation. All rights reserved.