Exception while accessing Published Orchestration

I have published an orchestration using Biztalk Web Services Publishing Wizard and while trying to access the published orchestration, I am getting the below exception

System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure
  at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[ parameters, ParamInfo[ inParamInfos, ParamInfo[ outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[ outHeaderTypes, String[ outHeaderNamespaces, SoapUnknownHeader[ unknownHeaders, SoapUnknownHeader[& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object cookie)
  at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[ parameters, ParamInfo[ inParamInfos, ParamInfo[ outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[ outHeaderTypes, String[ outHeaderNamespaces, SoapUnknownHeader[ unknownHeaders, SoapUnknownHeader[& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled)
  at ExposeWebService.Microsoft_Samples_BizTalk_ExposeWebService_ProcessClientRequest_SOAPPort.Operation_1(ClientRequest MessagePart_1)

 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: 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, ParamInfo[ inParamInfos, ParamInfo[ outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[ outHeaderTypes, String[ outHeaderNamespaces, SoapUnknownHeader[ unknownHeaders, SoapUnknownHeader[& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled, Object cookie)
  at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.Invoke(String functionName, Object[ parameters, ParamInfo[ inParamInfos, ParamInfo[ outParamInfos, Int32 bodyPartIndex, String bodyType, ArrayList inHeaders, ArrayList inoutHeaders, ArrayList& inoutHeaderResponses, ArrayList& outHeaderResponses, Type[ outHeaderTypes, String[ outHeaderNamespaces, SoapUnknownHeader[ unknownHeaders, SoapUnknownHeader[& unknownHeaderResponses, Boolean oneway, Boolean spsSsoEnabled)
  at ExposeWebService.Microsoft_Samples_BizTalk_ExposeWebService_ProcessClientRequest_SOAPPort.Operation_1(ClientRequest MessagePart_1)

Please tell me, If any one know how to resolve the exception.

Hello Sidhu,

we've had the same problem for  weeks now. I couldn't find anything, even with trying any recipes I was able to find on the Internet or in books. Right now our guess is that it has to do either with authentification or a very basic problem with the network. I sure hope someone knows the reason for this error.

Regards, Michael 

Michael,

Finally, I found the issue with this. In my system the account under which asp.net is running doesn't have credentials to login to BiztalkMgmtDB. Once I updated it with the user account under which BiztalkIsolatedHost is running, the exception disappeared.

 You can change the user account of asp.net from machine.config file's ProcessModel tag.

Check once if it also helps you.

Hello Sidhu,

unfortunately I already did this while following directions from a book. I hope I can find the reason for this soon...

Regards, Michael

Michael, 

What is the exception sequence you are getting in event log?

Sidhu,

sorry for taking so long. There's a major VM problem here, so I haven't had a chance to connect to my BTS installation for a long time.

The exception sequence you asked for was something like the error message itself. I searched the internet for a solution but noone seems to have that particular problem.

Regards, Michael