Missing Components Error While Importing Managed Solutions

“Do the Right thing, in the First attempt”. This was advise of one my mentors which has helped me a lot to progress in my career. I always tend to follow the best practices in my work and stick to the recommended approach despite the fact that it is not always feasible. I have lost count of late sittings I have done to use “Managed Solutions” in my work (Sounds familiar? 🙂 ) and some of these nights taught me a lot.
In one of my early works, I encountered the following scenario:
  1. In my Development environment, I created a new Unmanaged Solution with a new publisher (to identify who made changes). I added some components to the solution.
  2. While adding components I received the standard warning of “Missing components” to be added to the solution which I ignored. This was an expected action because my destination UAT environment already had the missing components so I was not expecting any dependency issue.
  3. I exported my solution with the new publisher as a “Managed Solution”.
  4. When I tried to import the managed solution in the UAT environment (in which already had all missing components), I received the below error.

After a some search, I learned the following: “The import of a managed solution will FAIL due to missing dependencies if imported solution publisher is different than the publisher who owns the missing components“. So you will have two options:
  1. Either add all missing components while you export your unmanaged solution as managed solution to ensure the platform does not try to find missing components from other solutions.
  2. Change the publisher of your unmanaged solution before export as managed solution and ensure that all missing components in your solution are under the same publisher name in your new environment. 


Choose your Reaction!
Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.