Carlos Medina's Blog

If you have(had) any problem when you are(were) publishing orchestrations as Web Services... then you must read this article "You cannot call an orchestration that is exposed as a Web service on a server that is running BizTalk Server 2004"....

The article explains three symptoms, its causes and how we can resolve it.  As part of article, these are the symptoms explained:

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.".

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.".

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.