The "SOAP" adapter is suspending an outbound message going to destination

Event Type:	Error

Event Source:	BizTalk Server 2004

Event Category:	BizTalk Server 2004 

Event ID:	5754

Date:		15/11/2004

Time:		15:24:02

User:		N/A

Computer:	B000E7F60EAA7

Description:

The "SOAP" adapter is suspending an outbound message going to 

destination URL:"/My.WebService/RetrieveCustomerInfo.asmx". 

Details:"Exception of type System.Runtime.InteropServices.COMException 

was thrown.". 

You just published an web service from your beautiful orchestration and you are expecting that your web service will work like a champ. Suddenly, you are stopped by this error and scratched your head several times trying to figure out what the h... is going on. You should reproduce the error and try to get more detailed exception context. Remember your could turn on the ThrowDetailedError in the web.config file to get more information about the exception.

  <appSettings>

   <add key="ThrowDetailedError" value="True" />

  </appSettings>

Once you turned on this switch, the exception you received from your client application should give you enough information to go about this exception. From my experience, the error is likely due to the transformation of the xml document to the objects in the message pipeline. For example, if you have an integer type element count in your outbound xml document instance you intend to map to a field or property of your object.

 <count>6.0</count>

The floating point number 6.0 will cause a conversion exception: System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info). This will eventually bubble up to throw the mysterious System.Web.Services.Protocols.SoapException.

You need also keep an eye on the possible number overflow. For example, if you have an element mapped to xs:integer which has a value that's not in the range of [-2147483648, 2147483647], you will receive this type of exception as well.