redeploy referenced orchestration

Home Page Forums BizTalk 2004 – BizTalk 2010 redeploy referenced orchestration

Viewing 1 reply thread
  • Author
    • #15150

      First unenlist and undeploy the orchestration.
      than go to the properties of the solution and update the assembly version to:

      Then recompile and re-deploy, and see how it goes!

      • #15151

        Hi All
        I have generic error handling orchestration.
        In any orchestration im calling that orchestration to handle my exceptions.
        When I want to change and deploy my error orchestration im getting this error:

        Error 6 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Cannot update assembly \”ErrorHandling, Version=, Culture=neutral, PublicKeyToken=13c7f9a200923443\” because it is used by assemblies which are not in the set of assemblies to update.
        To update the assembly, remove the following assemblies:
        CustomXSL, Version=, Culture=neutral, PublicKeyToken=8c73567b7f53264b
        ERPActions, Version=, Culture=neutral, PublicKeyToken=cbb876e94724b450
        OLMBT, Version=, Culture=neutral, PublicKeyToken=6d157e005499ec4f

        What should I do?
        This assembly is used by other assemblies


        • #15996

          I am experiencing this same situation.  How did you approach solving your problem?



        • #20800

           ‘Resources’ view in the BizTalk administrator (see below).  In here is a list of all of the assemblies that you have deployed and are using in BizTalk.  If look at the Destination Location column you might notice a hard-coded path (although not always the case).

          This is the path the BizTalk Administrator uses for the destination of resources on the BizTalk box where you are going to install the application.
          BizTalk Administrator Resources View
    • #15149

      Two other ideas:
      1) You can just copy the .DLL to the GAC without doing the full \”Deploy\”. If you added or deleted shapes, then this can cause the Orch Debugger to be lacking information, but it works.
      2) If you anticpate lots of changes like this in the future, there is an alternative to the \”Call Orch\” shape. You can send a message to a send port using \”direct binding\”, then receive a response back (also direct binding) via correlation. This is a little harder, but it removes the dependencies so you can redeploy the common orchestration without having to undeploy/redeploy everybody that uses it. The downside is you have to pass everything in the message (can no longer use the pass messages and variables).

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