BizTalk Orchestrations exposed as web services broken

Home Page Forums BizTalk 2004 – BizTalk 2010 BizTalk Orchestrations exposed as web services broken

Viewing 1 reply thread
  • Author
    • #12530

      I know this is going to be tricky issue to troubleshoot, but any insight that you may have would be great. We have a test development server that we use for testing new orchestrations and the such. Well, I have just noticed that any orchestrations we publish as web services on this box have quit working. I’m thinking it’s something BizTalk related because all our web services have quit working. Anything that attempts to utilize these web services generates an exception that \”The Application has timed out or is timing out.\” I’ve checked all the obvious settings…the account the Application Pool is using is the BizTalk Isololated Host user account. That account is a member of BizTalk Isolated Host Users group and the IIS_WPG group. Is there anything obvious (or maybe not so obvious) that I’m missing here. I’ve spent 2 days trying to figure this out using the obvious tools (Process Explorer, Registry Monitor, File Monitor).


    • #12531

      Oops, just wanted to say that the posting above is from me. I just forgot to login 🙂

      • #12532

        The 2 computers can ping each other. This particular web service is invoking BizTalk, which is ok, but then when BizTalk is done and is supposed to return data back to the web service, it just halts and times out. We are not rebuilding the web services deployed as orchestrations, we are just moving them over to the test box. I know the web services deployed as orchestrations do work because if I move them over to our production servers, they function normally. It seems to me like something in BizTalk is broken, but I don’t know what part that might be. Thanks!

        On the client that consumes the web service it fails on this line of code, waiting for the reply back from the web service: object[] results = this.Invoke(\”AcceptCompositonRequest\”, new object[]

        Also, this gets logged to the Event Log every time an orchestration exposed as a web service gets called.

        Event Type: Error
        Event Source: SQLSERVERAGENT
        Event Category: Alert Engine
        Event ID: 318
        Date: 12/15/2005
        Time: 8:55:20 AM
        User: N/A
        Computer: XXXXXX
        Unable to read local eventlog (reason: The data area passed to a system call is too small).

        For more information, see Help and Support Center at

        Not very informative, but seems to be related since it happens every time I call a BizTalk Orchestration web service

        • #12533

          Well, I have resolved this issue. The problem was this box was unpatched, so I applied the Windows Server 2003, BizTalk Server 2004, and SharePoint services service packs. After doing that, my web services are working…but the Service Pack for BizTalk brought up another interesting issue which I have to ponder for a while and will probably post on later 🙂 Thanks for the help!


          • #12534

            Since this is on another computer, is there any domain issue between the two? Can they both ping each other?

            Or are you are trying to call the web service locally?

            Are you moving existing web services over to the new computer or are you rebuilding them on the new server? In you are not rebuilding them; you might want to try that just to make sure that works. Maybe there is something hard coded in the web services.

            Just some thoughts.

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