PRB: COM+ Application Programmatically Set As Workflow Host Causes Error

View products that this article applies to.

This article was previously published under Q312714

Expand all | Collapse all

SYMPTOMS

If you try to run a COM+ application that is set to host XLANG Schedules, and the application is not configured with an appropriate DSN, you may receive the following error message:

The database connection could not be established. The following error(s) occurred:
The User/System DSN is either not present or has not been configured to use Windows Authentication.

Back to the top

All XLANG Scheduler System Manager objects must have an associated Data Source Name (DSN) that points to a SQL Server database to support the dehydration and rehydration of long-running business processes.

Back to the top

RESOLUTION

To resolve this problem, create a DSN for the COM+ application that you have configured as a host for XLANG Schedules. To do this, follow these steps:

Right-click the COM+ application, and then click Properties.
Click the XLANG tab, and then click Create DSN.

Back to the top

STATUS

This behavior is by design.

Back to the top

MORE INFORMATION

If you manually set a COM+ application to be a host for XLANG Schedules and you do not specify an appropriate DSN that points to an XLANG persistence database, you receive the following error message:

No DSN Found

To configure a COM+ server application as a host for XLANG schedules, you must first create and configure a DSN for its persistence database.

When you programmatically set a COM+ application to be a host for XLANG Schedules, an XLANG persistence DSN is not verified, and the newly created COM+ XLANG Schedule host cannot host XLANG Schedules until an appropriate DSN is created for it.

It is possible to programmatically set a COM+ application to be a host for XLANG Schedules when you use the BizTalk WKFlow.SysMgr interface. For example, the following script sets the COM+ application named TestWorkflowHost to be a host for XLANG Schedules:

Set oGM = CreateObject("WKFlow.SysMgr")
oGM.IsWorkflowHost("TestWorkflowHost")=True

NOTE: After you programmatically set a COM+ application as a host for XLANG Schedules, you must add a component to the COM+ application to successfully invoke the COM+ application. The component that you add to the application can be any valid registered COM component and does not have to be the WkFlow.SysMgr class.

Back to the top