failed to deploy

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › failed to deploy

Viewing 1 reply thread
  • Author
    Posts
    • September 25, 2006 at 10:13 PM #15838
      community-content

        My biztalk solution includes 3 project, one for schema&map, one for pipeline, and another for orchestration. 

        I changed a schema and then deploy the project, it was working fine.

        Then i change a pipeline to point to the newly deployed shema, and deploy the pipeline project, got errors like below:

        Error 20 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Unable to install the "C:\Documents and Settings\zWSLBizTalk\Local Settings\Temp\1\BT\PID532\BizTalkAssembly\92751483f119d517524521d4aa7b02e7\Myassembly.dll" assembly into the Global Assembly Cache.
        Exception: A file load exception occurred while attempting to install the assembly into the Global Assembly Cache. This error may occur if the assembly is delay signed, or if assembly was renamed after creating/signing.

         I didn't change assembly name….

        Does anybody know what's the cause?

         Thanks a lot
           
         

      • September 26, 2006 at 1:53 PM #15853
        community-content

          I figured it out, it's caused by non-exists reference path in project.

          Right click the project > Properties, in the Pop-uped the window, go to the "Referenced Paths", check if there's any path not exists anymore, this will happen when you move the solution to another machine.

          Delete those path and deploy it, everything's working fine. 🙂

          • March 5, 2007 at 11:22 AM #17859
            community-content

              After attempting to fix the referenced paths and the app still doesn't deploy – go to the Global Assemble Cache (\windows\assembly\ on Server 03) and uninstall the most recent version of the assembly.  If it will not uninstall of a process using it, the Host Instance may need to be stopped.

              Doing this allowed me to deploy the app after making a change to a schema.

              • March 7, 2007 at 8:33 AM #17880
                community-content

                  For what it's worth, I've seen instances in BT 2006 where you yank the assemblies, uninstall (via Control Panel) the application and delete the application from the BT Admin Console, and the new app (version) STILL won't deploy.  We are using a VM Ware server, so you can just imagine Microsoft's response.

                  The solution is to perform the above three steps, then bounce the server, then install the new app.  TIP: Once you have all your bindings configured, if you export the bindings and save them, when you install your new version it's a simple matter to import the bindings file and you can then avoid the whole config business.

                  Hope this helps.
                   

                  • March 11, 2008 at 7:10 PM #19050
                    community-content

                      Also make sure that you do not have any breakpoints set in an orchestration. Even if there are no orchestration instances running anymore, assemblies may remain loaded making it impossible to unload the associated assembly from the GAC.  This is also true for dependent assemblies.  

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