In BizTalk 2004 you will end up with a dehydrated orchestration if the Siebel web service would fail. The reason is that the return error type mentioned in the WSDL is not returned. Instead, and depending on the type of error, HTTP error in this case, you see something like this in the event log
The adapter "SOAP" raised an error message. Details "Client found response content type of 'text/html;charset=UTF-8', but expected 'text/xml'.
The request failed with the error message:
--
<html><head><title>Message:</title></head>
<body>The server you are accessing is either busy or experiencing difficulties. Please close the web browser, start a new one and try logging in again. For further support, please copy and send the full message text to your system administrator.[15:05:39]
<p>
--.".
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Some times I even got something like this:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body xmlns:siebelf="http://www.siebel.com/ws/fault">
<faultcode>Client</faultcode>
<faultstring>There is no active Web Service with operation named 'http://www.CompanyName.co.uk/xml/BBT_Account_And_Address_Inbound:RunProcess4'.(SBL-EAI-04313)</faultstring>
- <detail>
- <siebelf:errorstack>
- <siebelf:error>
<siebelf:errorsymbol />
<siebelf:errormsg>There is no active Web Service with operation named 'http://www.CompanyName.co.uk/xml/BBT_Account_And_Address_Inbound:RunProcess4'.(SBL-EAI-04313)</siebelf:errormsg>
</siebelf:error>
</siebelf:errorstack>
</detail>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>