Entry

Internal Soap Processing Error - when trying to call Orchestration published as web service...

Apr 6th, 2005 22:53
Balaji Ramachandran, http://biztalk-training.com/Default.aspx?tabid=57

1) Check the event log 
2) Turn on more specific error processing on your development machine 
(lookup keyword ThrowDetailedError Switch) 
http://www.msdn.microsoft.com/library/default.asp?url=/library/en-
us/sdk/htm/ebiz_prog_webservices_lqcv.asp 
which tells you to add the following to web.config file: 
3) Go to IIS and put the web service in "Application Prootection = High 
(Isolated)" which will create a new COM+ application. Go to 
admin "Component Services" and set the identify of the COM+ application 
to some user with sufficient priveleges to update Biztalk database(s). 
4) The other reasons could be a disabled receive 
location/not started orchestration. This can be difficult to catch 
sometimes and we are considering a troubleshooting tool for the next 
release which will check all these settings for a given published 
webservice.
5) Usually is security related. Some userid lacks authority. I spent 
about an hour trying various configurations, and the trick that made it 
work was adding ASPNET to BiztalkServerAdmin group and giving ASPNET 
db_owner access to SSO database. Not sure this is wise, but it got me 
past the error.