Microsoft KB Archive/910295

= You cannot call an orchestration that is exposed as a Web service on a server that is running BizTalk Server 2006 or BizTalk Server 2004 =

Article ID: 910295

Article Last Modified on 8/28/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2006 Standard Edition
 * Microsoft BizTalk Server 2006 Developer Edition
 * Microsoft BizTalk Server 2006 Enterprise Edition
 * Microsoft BizTalk Server 2004 Standard Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Partner Edition

-



SYMPTOMS
On a server that is running Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2004, you cannot call an orchestration that is exposed as a Web service. The orchestration is not invoked in the Health and Activity Tracking (HAT) tool. Additionally, you may experience one or more of the following symptoms:

Symptom 1
The following error messages are logged in the Application event log on the server that is running BizTalk Server 2006 or BizTalk Server 2004:

The Messaging Engine failed to register the adapter for &quot;SOAP&quot; for the receive location &quot;/ / .asmx&quot;. Please verify that the receive location is valid, and that the isolated adapter runs under an account that has access to the BizTalk databases.

An attempt to connect to &quot;BizTalkMgmtDb&quot; SQL Server database on server &quot; &quot; failed with error: &quot;Cannot open database requested in login 'BizTalkMgmtDb'. Login fails.&quot;.

Note In this error message,  represents the name of the virtual directory for the Web service,   represents the Web service name, and   represents the server name.

Symptom 2
On a remote server that is running BizTalk Server 2006 or BizTalk Server 2004, the following error message is logged in the Application event log when you call the orchestration that is exposed as a Web service:

The &quot;SOAP&quot; adapter is suspending an outbound message going to destination URL:&quot;&quot;. Details: &quot;Server was unable to process request. --> File or assembly name .dll, or one of its dependencies, was not found.&quot;.

Notes
 * In this error message,  represents the name of a file.
 * Every time that you call the orchestration, the assembly name in the error message changes.
 * No error messages may be logged in the application event log on the server on which the Web service is exposed.

When you call the orchestration that is exposed as a Web service from a client computer that is not running BizTalk Server 2006 or BizTalk Server 2004, you may receive an error message that is similar to the following:

SoapException: Internal SOAP Processing Failure

Symptom 3
The following error message is logged in the Application event log on the server on which the Web service is exposed:

There was a failure executing the receive pipeline: &quot;Microsoft.BizTalk.DefaultPipelines.XMLReceive&quot; Source: &quot;Microsoft.BizTalk.Messaging&quot; Receive Location: &quot;/ / .asmx&quot; Reason: Specified cast is not valid.



CAUSE
These issues occur because of the following causes:

Symptom 1
This issue occurs because the application pool identity that is used by the application pool for the exposed Web service is not a member of the BizTalk Isolated Host Users group.

Note The BizTalk Isolated Host Users group must have permissions on the BizTalkMgmtDb database. The BizTalk Isolated Host Users group is granted permissions on the BizTalkMgmtDb database when you install BizTalk Server 2006 or BizTalk Server 2004.

Symptom 2
This issue occurs because the application pool identity for the exposed Web service does not have the correct read/write permissions. The application pool identity must have permissions to the %systemroot%\Temp folder on the server that runs BizTalk Server 2006 or BizTalk Server 2004 and exposes the Web service.

Web service (.asmx) files are just-in-time (JIT) compiled to create DLLs in the %systemroot%\Temp folder. If the application pool identity does not have permissions to this folder, these DLLs are not created.

These DLLs have random eight-character file names. Therefore, the assembly name in the error message changes every time that you call the orchestration.

Symptom 3
This issue occurs because the Web service proxy is not published correctly.



RESOLUTION
To resolve these issues, use one of the following methods.

Symptom 1
To resolve this issue, configure the application pool identity for the Web service to use a user account that is a member of the BizTalk Isolated Host Users group. To do this on a Microsoft Windows Server 2003-based computer, follow these steps:
 * 1) Start Internet Information Services (IIS) Manager.
 * 2) Expand the computer name that you want to configure, and then expand Web Sites.
 * 3) Right-click the virtual directory for the Web service, and then click Properties.
 * 4) On the Home Directory tab, note the application pool for the virtual directory, and then click OK.
 * 5) Expand Application Pools.
 * 6) Right-click the application pool that you noted in step 4, and then click Properties.
 * 7) On the Identity tab, configure the application pool to use a security account that is a member of the BizTalk Isolated Host Users group, and then click OK.

Note This account must also be a member of the IIS_WPG group.
 * 1) Exit Internet Information Services Manager.
 * 2) Click Start, click Run, type cmd, and then click OK.
 * 3) At the command prompt, type Iisreset /restart, and then press ENTER.

Symptom 2
To resolve this issue, verify that the application pool identity security account has read/write permissions to the %systemroot%\Temp folder on the server that runs BizTalk Server 2006 or BizTalk Server 2004 and exposes the Web service.

Symptom 3
To resolve this issue, use the BizTalk Web Service Publishing Wizard to republish the Web service proxy.



MORE INFORMATION
For more information about how to enable Web services in Microsoft Windows 2000 and in Microsoft Windows XP, visit the following Microsoft Developer Network (MSDN) Web site:

http://msdn2.microsoft.com/en-us/library/ms946959.aspx

For more information about how to debug orchestrations that are published as Web services, visit the following MSDN Web site:

http://msdn2.microsoft.com/en-us/library/ms935219.aspx

