locked
Undeploy fails due to unresolved assembly reference RRS feed

  • Question

  • I am getting the following error when i try to undeploy a Biztalk assembly:

     

    1 unresolved assembly reference/s.
       at Microsoft.BizTalk.Deployment.BizTalkAssembly.VerifyModuleForRemoval()
       at Microsoft.BizTalk.Deployment.BizTalkAssembly.RemoveNamedModule(String server, String database, String assemblyName, String assemblyVersion, String assemblyCulture, String assemblyPublicKeyToken, ApplicationLog log)
    PerformingEndChangeRequestsWithRollBack
    Failed to delete resource(s).
    Undeployment failed.

    How do i resolve this?

     

     

    Tuesday, June 26, 2007 2:36 PM

Answers

  • Check whether you are undeploying it in the order of dependency

     

    example orchestration might depend on a map which might depend on a schema.

     

    So in this case if you try to remove either map or a schema you'll get the dependency error. In this case you need to undeploy it from reverse order.

    Orchestration, then map, then schema

     

    --
    Regards,
    Saravana Kumar
    http://www.biztalk247.com/v1/
    http://www.digitaldeposit.net/blog
    [Please mark the response as "Answer" if it solves your problem.]

    Tuesday, June 26, 2007 2:52 PM
    Moderator
  • Hi,
    The restart of the VS helps sometimes with the pipeline components .
    Check the related applications. <All Artifacts> application helps you to see the full list of the ports.
     
    Regards,
     
    Leonid Ganeline
     
    Wednesday, June 27, 2007 4:33 PM
    Moderator

All replies

  • Check whether you are undeploying it in the order of dependency

     

    example orchestration might depend on a map which might depend on a schema.

     

    So in this case if you try to remove either map or a schema you'll get the dependency error. In this case you need to undeploy it from reverse order.

    Orchestration, then map, then schema

     

    --
    Regards,
    Saravana Kumar
    http://www.biztalk247.com/v1/
    http://www.digitaldeposit.net/blog
    [Please mark the response as "Answer" if it solves your problem.]

    Tuesday, June 26, 2007 2:52 PM
    Moderator
  • The assembly it is referring to is not a Biztalk assembly. I renamed a bunch of stuff in the Biztalk project and looks like the reference to the old assembly is still somewhere there.  The referenced assembly is a custom pipeline component which again I have renamed. I copied the old custom pileline component dll back to the pipeline components folder but that has not helped.

     

    BTW your paper on Custom Pipeline Components was excellent. Great contribution!

    Tuesday, June 26, 2007 4:42 PM
  • Hi,
    The restart of the VS helps sometimes with the pipeline components .
    Check the related applications. <All Artifacts> application helps you to see the full list of the ports.
     
    Regards,
     
    Leonid Ganeline
     
    Wednesday, June 27, 2007 4:33 PM
    Moderator