Recently, I tried to invoke an orchestration publish as a Web Service, and if you are working with the BizTalk SOAP adapter, you have likely encountered the following cryptic error message:
“Internal SOAP Processing Failure” error.
This error is frustrating because it provides no details about what actually went wrong. It is a generic “catch-all” fault returned to the web service client to prevent the leakage of sensitive system information.
Because the SOAP response is intentionally vague, you must look at the source.
- Log in to the BizTalk Server machine.
- Open the Event Viewer (Windows Logs > Application).
- Look for “Error” entries sourced from BizTalk Server or XLANG/s occurring at the exact same time as the SOAP fault.
Cause
Once you check the Event Viewer, you will likely find one of these three common root causes of SOAP Processing Failures:
- Schema Validation Failure: The incoming XML message does not match the schema expected by the Receive Port. Even a small namespace mismatch will trigger this.
- Permissions (Isolated Host): The user account running the IIS Application Pool (the Isolated Host) does not have the necessary permissions to write to the BizTalk MessageBox or access the required assemblies.
- Map Failures: If a map is configured directly on the Receive Port, any transformation error (like a missing mandatory field) will result in an internal processing failure.
In my case, it was permissions.
Solution
- Find out the identity under which the application pool is running.
- Add this user to both IIS_WPG and BizTalk Isolated Host Users groups.
- Check the permission on the %temp% folder. Ensure either the user running the application pool or the groups the user belongs to have read/write permissions on the %temp% folder.
Don’t let the “Internal SOAP Processing Failure” slow you down. By shifting your focus from the client-side fault to the server-side Event Viewer, you can quickly identify and resolve the underlying integration issue.
Hi Sandro, I also found a post telling me to check promoted properties. Neither solution worked for me, but as soon as I get it to work, I’ll post again. I just wanted to share that second tip. Thank you.