SYMPTOMS
On a server that is running 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 2004:
The Messaging Engine failed to register the adapter for "SOAP" for the receive location "/VirtualDirectory/Name.asmx". 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 "BizTalkMgmtDb" SQL Server database on server "Server" failed with error: "Cannot open database requested in login 'BizTalkMgmtDb'. Login fails.".
Note In this error message,
VirtualDirectory represents the name of the virtual directory for the Web service,
Name represents the Web service name, and
Server represents the server name.
Symptom 2
On a remote server that is running 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 "SOAP" adapter is suspending an outbound message going to destination
URL:"<http://VirtualDirectory/Name.asmx>".
Details: "Server was unable to process request. --> File or assembly name FileName.dll, or one of its dependencies, was not found.".
Notes- In this error message, FileName 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 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:
"Microsoft.BizTalk.DefaultPipelines.XMLReceive" Source:
"Microsoft.BizTalk.Messaging" Receive Location:
"/VirtualDirectory/Name.asmx" Reason: Specified cast is not valid.
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:
- Start Internet Information Services (IIS) Manager.
- Expand the computer name that you want to configure, and then expand Web Sites.
- Right-click the virtual directory for the Web service, and then click Properties.
- On the Home Directory tab, note the application pool for the virtual directory, and then click OK.
- Expand Application Pools.
- Right-click the application pool that you noted in step 4, and then click Properties.
- 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. - Exit Internet Information Services Manager.
- Click Start, click Run, type cmd, and then click OK.
- 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 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.