By Edmund Zhao
This article provides helpful information on how to config and consume BizTalk Web Services.
***
Lots of BizTalk developers were facing similar problems when they built their own .NET test applications to test the web services generated by BizTalk Web Services Publishing Wizard. The debugging process stopped at “this.Invoke()”, and usually there will be an error message of “Internal SOAP Processing Failure”. If you check the event log, you will also see an error similar to “The Messaging Engine failed to register the adapter for SOAP for the receive location ...asmx. Please verify that the receive location is valid, and that the isolated adapter runs under an account that has access to the BizTalk databases.”
The first thing you can do is to check the status of your orchestration in BizTalk Explorer. Make sure the orchestration is properly bound to its corresponding web ports, and it is enlisted and started. If the status of your orchestration is ok, most likely it’s a security issue on the machine you are running the web services and BizTalk orchestration.
Here are some tips to help you solve the issues.
Q: Should I turn off anonymous access to the web service project?
A: No, otherwise you will receive “The request failed with HTTP status 401: Access Denied.” error.
Q: Should I change the default namespace “http://tempurl.org/” of my web service to match the real URL of the web service?
A: No, it’s not necessary. But it will be a good practice to rename it to be something meaningful.
Q: I’m running my test on Windows 2003 and I received “Internal SOAP Processing Failure” error. What should I do?
A: 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 of %temp% folder. Make sure either the user running the application pool or the groups this user belongs to has read/write permission on %temp% folder.
Q: I’m running my test on Windows XP and I received “Internal SOAP Processing Failure” error. What should I do?
A: Add user “ASPNET” into “BizTalk Isolated Host Users” group. Check the permission of %temp% folder. Make sure either ASPNET or “BizTalk Isolated Host Users” group has read/write permission on %temp% folder. If your %temp% folder is on FAT32, don’t worry about the permission.
A good reference for you to understand more details is an MSDN article BizTalk Server 2004 and Web Services.
Source URL:
http://geekswithblogs.net/edmundzhao/archive/2005/12/14/63105.aspx