Odd problem with web service communication

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Odd problem with web service communication

Viewing 1 reply thread
  • Author
    Posts
    • May 23, 2008 at 12:33 AM #19727
      community-content

        Hello,

        I’m still working on a solution to establish even the simplest communication with a webservice. I’ve created a WS from an orchestration. I am able to insert a web reference and use the schema provided (for simplicity I just alter some values before sending the xml back). After some fighting and much reading I’m stuck with the following error message after starting the application:

        Uncaught exception (see the ‘inner exception’ below) has suspended an instance of service ‘SQLtoWSS.SQLpollerType(0f84bc35-161d-84aa-18c8-20e89e34cfab)’.
        The service instance will remain suspended until administratively resumed or terminated.
        If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.
        InstanceId: 197a149c-b42d-4a7b-a5c9-9acedfbc541e
        Shape name:
        ShapeId:
        Exception thrown from: segment -1, progress -1
        Inner exception: System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure —> System.Runtime.InteropServices.COMException (0xC0C01666): The Messaging Engine failed to register the adapter for "SOAP" for the receive location "/PassT/SQLtoWSS_PassThroughWS_WScomm.asmx". Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
           at Microsoft.BizTalk.TransportProxy.Interop.IBTTransportProxy.RegisterIsolatedReceiver(String url, IBTTransportConfig callBack)
           at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.RegisterIsolatedReceiver()
           at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.InternalInvoke(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, Object cookie)
           — End of inner exception stack trace —
           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 SQLtoWSS.SQLtoWSS_PassThroughWS_WScomm.Operation_1(MaterialInformation part)
        Message ID: {399071EA-2931-4D5B-B04B-BDAA9BD1EEA3}
        Instance ID: {FC77DE12-AFAB-4E6E-B909-5451C8C4666B}
        Error Description: System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure —> System.Runtime.InteropServices.COMException (0xC0C01666): The Messaging Engine failed to register the adapter for “SOAP” for the receive location “/PassT/SQLtoWSS_PassThroughWS_WScomm.asmx”. Please verify that the receive location exists, and that the isolated adapter runs under an account that has access to the BizTalk databases.
           at Microsoft.BizTalk.TransportProxy.Interop.IBTTransportProxy.RegisterIsolatedReceiver(String url, IBTTransportConfig callBack)
           at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.RegisterIsolatedReceiver()
           at Microsoft.BizTalk.WebServices.ServerProxy.ServerProxy.InternalInvoke(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, Object cookie)
           — End of inner exception stack trace —
           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 SQLtoWSS.SQLtoWSS_PassThroughWS_WScomm.Operation_1(MaterialInformation part)

               
        Exception type: XlangSoapException
        Source: Microsoft.XLANGs.BizTalk.Engine
        Target Site: Void VerifyTransport(Microsoft.XLANGs.Core.Envelope, Int32, Microsoft.XLANGs.Core.Context)
        The following is a stack trace that identifies the location where the exception occured

           at Microsoft.BizTalk.XLANGs.BTXEngine.BTXPortBase.VerifyTransport(Envelope env, Int32 operationId, Context ctx)
           at Microsoft.XLANGs.Core.Subscription.Receive(Segment s, Context ctx, Envelope& env, Boolean topOnly)
           at Microsoft.XLANGs.Core.PortBase.GetMessageId(Subscription subscription, Segment currentSegment, Context cxt, Envelope& env, CachedObject location)
           at SQLtoWSS.SQLpollerType.segment1(StopConditions stopOn)
           at Microsoft.XLANGs.Core.SegmentScheduler.RunASegment(Segment s, StopConditions stopCond, Exception& exp)

        I let the isolated host log on as “biztalk”, the user which has admin permissions – I wanted to succeed and then try a more restricted account. I’m very unexperienced with administrative issues and couldn’t find anything pointing to my problem. At least nothing that solved this. Has anyone got a clue what’s wrong with my system ? I still suspect some problems with permissions to be the reason for this.

         

        Kind regards, Michael

      • May 23, 2008 at 5:50 AM #19728
        community-content

           Hi Michael,

          I have seen that error many times.  It usually means one of two things:

          1. The web service application pool does not have access to the BizTalk databases.  If this is the case, you can fix the issue by opening the IIS administraton console, opening the properties page for the web service application pool, clicking on the identity tab, and specifying the proper account.
          2. The receive location URL does not match the URL of the web service.  For example if your web service is located at:  http://localhost/VirtualDir/Service.asmx, the receive location URL would be /VirtualDir/Service.asmx.

          Hope this helps!

           

          • May 23, 2008 at 6:50 AM #19731
            community-content

              Hello ruselw,

              This sounds like something that might lead to a solution. Right now I’m busy, but I will try it out on monday.

              Thank you for the quick reply !

               

              Regards, Michael

              • May 26, 2008 at 11:36 PM #19755
                community-content

                  Hello again,

                  sorry, but I’m still stuck on this. When configuring BTS 2006 R2 (after installation) I used an administrator account named biztalk. This is overkill, but I wanted no problems from this side. Furthermore it’s just a testing system.

                  So this is the account which is used for the application pool (I just took the “BAMAppPool”) the service is running under. According to the two possible sources of my problem I had to check the receive location url which is identical to the path of the web service. So this could be the reason, but I use a combined receive/send port. Maybe because of that I always get the error ‘An invalid value for property “URI”‘ when trying to enter the web service URL in the form mentioned above.

                  Can someone see where my mistake lies ?

                   

                  Regards, Michael

                  • May 27, 2008 at 1:55 AM #19757
                    community-content

                      Well, now I’m getting:

                      “System.Web.Services.Protocols.SoapException: Internal SOAP Processing Failure —> System.Runtime.InteropServices.COMException (0xC0C0164B): Exception from HRESULT: 0xC0C0164B
                         at …”

                      Why does BTS create a send port with my logical port when everyone on  the net discusses receive port settings ? It seems all right, since the first message from my orchestration goes out, but still… What’s more, the automatically generated port when using the “Web Services Publishing Services” is also defined as a receive port, so I can’t use it in my calling project.

                      I have the slight suspicion I’m getting something terribly wrong here.

                      Regards, Michael

                      • May 27, 2008 at 3:30 AM #19758
                        community-content

                          Finally, I’ve done it ! Adding the receive port to the web service orchestration helped. (Blushing)

                          Some time ago I’ve read something on the web about the problem with xml schemas I get now that I want to use the XML standard pipeline instead of pass through. No sweat. So thank you very much for your precious time !

                           

                          Kind regards, Michael

                  • December 17, 2008 at 4:13 PM #21416
                    community-content

                      Thanks for this one. I didn’t think of the URL mismatch – I had a typo that was hard to spot but your most made me take a closer look.

                • Author
                  Posts
                Viewing 1 reply thread
                • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.