Microsoft KB Archive/915089

= When you use the BizTalk WSE Web Services Publishing Wizard, fault message details do not appear as expected =

Article ID: 915089

Article Last Modified on 5/15/2006

-

APPLIES TO


 * Microsoft BizTalk Adapter for Web Services

-





SYMPTOMS
Consider the following scenario:
 * In Microsoft BizTalk Server 2004, you add an orchestration that includes a request-response port that has a defined fault message.
 * You use the BizTalk WSE Web Services Publishing Wizard to publish the orchestration as a Web service.

In this scenario, fault message details do not appear as expected in the details section of the SoapException exception body.



WORKAROUND
To work around this behavior, manually create an exception in a catch block in the Web service proxy code that is generated by the BizTalk WSE Web Services Publishing Wizard, and then throw the exception to the client computer. The following sample code demonstrates how to do this. try {               Microsoft.Web.Services2.SoapEnvelope response = this.Invoke(request, &quot;Operation_1&quot;, bodyTypeAssemblyQualifiedName, false, false, cookie); response.Save(@&quot;C:\SoapResponseEnv.xml&quot;); return response; }           catch(SoapException se) {               SoapException se1 = new SoapException(se.InnerException.Message.ToString, SoapException.ClientFaultCode,&quot;http://localhost/FaultMessageProcessing_Proxy/FaultMessageProcessing_FaultMessageOrch_FaultInOut.ashx&quot;,se); throw se1;

}



STATUS
This behavior is by design.



MORE INFORMATION
For more information about how to create and to publish a Web orchestration by using the Microsoft BizTalk Adapter for Web Services Enhancements 2.0, visit the following Microsoft Web site:

http://www.microsoft.com/technet/prodtechnol/biztalk/biztalk2004/planning/walkwse.mspx

Keywords: kbtshoot kbprb kbbtsadapters kbbts KB915089

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.