none
Exception from HRESULT: 0x80C0164A is returned as SOAP fault message RRS feed

  • Question

  • I am using XML disassembler pipeline component  and validating the schema. Also I have enabled  "Include Exception Details in Faults". Right now if there is an error in schema the client / SOAP UI is able to get the exception details this works fine in all the environments.  Now issues in PROD where we have SQL clustered environments and I am getting the below message when schema validation fails. Please advice on this. 

    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">

       <s:Body>

          <s:Fault>

             <faultcode xmlns:a="http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode>

             <faultstring xml:lang="en-GB">Exception from HRESULT: 0x80C0164A</faultstring>

             <detail>

                <ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">

                   <HelpLink i:nil="true"/>

                   <InnerException i:nil="true"/>

                   <Message>Exception from HRESULT: 0x80C0164A</Message>

                   <StackTrace>at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.EndOperation(IAsyncResult result)

       at AsyncInvokeEndEndTwoWayMethod(Object , Object[] , IAsyncResult )

       at System.ServiceModel.Dispatcher.AsyncMethodInvoker.InvokeEnd(Object instance, Object[]&amp; outputs, IAsyncResult result)

       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc&amp; rpc)

       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc&amp; rpc)

       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace>

                   <Type>System.Runtime.InteropServices.COMException</Type>

                </ExceptionDetail>

             </detail>

          </s:Fault>

       </s:Body>

    </s:Envelope>

    Thursday, December 10, 2015 3:20 PM

All replies

  • Hi Suresh ,

    There are couple of things which you can check :

    1 ) BtsActionMapping  for SOAP action Header

    <BtsActionMapping xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
      <Operation Name="OperationXXXName1" Action="OperationXXXName1" />
      <Operation Name="OperationXXXName2" Action="OperationXXXName2" />
    </BtsActionMapping>

    Note : try to make Orchestration logical name same as operation name.

    Also look for https://connectedpawns.wordpress.com/2010/04/09/synchronous-web-services-calls-and-faults/

    Thanks

    Abhishek


    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply

    Friday, December 11, 2015 3:59 AM
  • HI Abhishek

    Am validating the schema in the receive pipeline.

    Regards

    Suresh

    Friday, December 11, 2015 6:32 AM
  • Hi Suresh,

    Thank you for posting in MSDN forum.

    Are you getting this error for all document or for particular message?

    Please provide the steps you are following to get this error.


    Thanks,

    If my reply is helpful please mark as Answer or vote as Helpful.

    My blog | Twitter | LinkedIn

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, December 11, 2015 2:45 PM
    Moderator
  • Hi Kamlesh

    Not for all messages when ever we are testing for invalid xml  we want to send the reason for the error back to the client. But I get an invalid error. This is happening only in PROD env.

    For valid XML the messages are getting passed through

    Not sure what's the issue. Pls advice.

    Saturday, December 12, 2015 9:25 AM
  • Hi Suresh,

    Thank you for confirmation. when you say this is happening only in Prod, have you verified with same message on test/UAT environment? If yes then please provide the result and also the message.

    And I would suggest to check in event viewer for more error information.


    Thanks,

    If my reply is helpful please mark as Answer or vote as Helpful.

    My blog | Twitter | LinkedIn

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Sunday, December 13, 2015 11:08 PM
    Moderator
  • Hi Kamalesh

    From SIT i provided invalid date format and the receive pipeline has catched the error and below is the response.

    This is what I should get in Prod as well but I could not.


    <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
       <s:Body>
          <s:Fault>
             <faultcode xmlns:a="a:InternalServiceFault</faultcode">http://schemas.microsoft.com/net/2005/12/windowscommunicationfoundation/dispatcher">a:InternalServiceFault</faultcode>
             <faultstring xml:lang="es-MX">There was a failure executing the receive pipeline: "" (some message which is have removed) </faultstring>
             <detail>
                <ExceptionDetail xmlns="http://schemas.datacontract.org/2004/07/System.ServiceModel" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
                   <HelpLink i:nil="true"/>
                   <InnerException i:nil="true"/>
                   <Message>There was a failure executing the receive pipeline: "CreatedDateTime' element has an invalid value according to its data type." .</Message>
                   <StackTrace>at Microsoft.BizTalk.Adapter.Wcf.Runtime.BizTalkServiceInstance.EndOperation(IAsyncResult result)
       at AsyncInvokeEndEndTwoWayMethod(Object , Object[] , IAsyncResult )
       at System.ServiceModel.Dispatcher.AsyncMethodInvoker.InvokeEnd(Object instance, Object[]&amp; outputs, IAsyncResult result)
       at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeEnd(MessageRpc&amp; rpc)
       at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage7(MessageRpc&amp; rpc)
       at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)</StackTrace>
                   <Type>Microsoft.BizTalk.Message.Interop.BTSException</Type>
                </ExceptionDetail>
             </detail>
          </s:Fault>
       </s:Body>
    </s:Envelope>

    Monday, December 14, 2015 10:37 AM