Web service clients may encounter an error with the exception text "Internal SOAP Processing Failure" when consuming (calling) published BizTalk Web services.

Published Web services return the following generic exception when the Web service client encounters an error:

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[] parameters, Type[] outParameters, Int32 bodyPartIndex, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[] outHeaderTypes, String[] outHeaderNamespaces, SoapUnknownHeader[] unknownHeaders, SoapUnknownHeader[]& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Boolean spsSsoRequired)

The most common cause of this error is when you do not have an adequate security configuration on the server. Another common cause is when the ASP. NET worker process does not have permission to the access the %temp% directory.

 Security  By default, Internet Information Services has anonymous access turned off for the published Web service for security reasons.

Note  If you do not enable anonymous access, ensure that you supply valid credentials when you consume (call) your published BizTalk Web service. You can enable anonymous access for your Web service by using Internet Information Services Manager.

If you use Internet Explorer to test your published Web service, you might encounter this error.

User Action

Check the event viewer and HAT to get more information about the possible causes of the error.

Check your security configurations. You must have BizTalk Isolated Host installed. Verify that you have enabled receive HTTP and SOAP handlers. For information about enabling BizTalk Web services and security configurations, see Enabling Web Services.

If you are getting an access denied error to the %temp% directory, verify that you have the correct permissions set. Verify that your receive locations are correctly configured. For more information about troubleshooting BizTalk receive locations, see Unable to Create BizTalk Receive Locations.

You can also get more specific exception information to help you debug your published Web service. For more information about debugging your published Web service, see Debugging Published Web Services.

To test your published Web service, you should use a simple client such as a C# or Visual Basic .NET client to submit data to your Web service.

See Also

Troubleshooting Published Web Services