web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Solution Packager error "Following root components are not defined in customizations"

(0) ShareShare
ReportReport
Posted on by

I'm attempting to push an updated version of an existing solution up into another environment. When using SolutionPackager (Version 8.2.0.820), I'm able to sucessfully extract both the managed and unmanaged solution so I can save it into Git. When trying to run the extract operation I get the following errors.

Following root components are not defined in customizations:
  Type='Dashboard', Id (or schema name)='{2fed44d1-ae68-4a41-bd2b-f13acac4acfa}'.
  Type='Dashboard', Id (or schema name)='{57d9b1f2-ce52-48b4-869d-e05b481a90bb}'.

Upon trying to import the solution into the other environment it fails at the Root Components Insertion step with the following error.

0x8004F024 Cannot update solution 'MySolution' because it is a managed solution.

I've tracked down the two IDs to being the main form for Contact and the main form for a custom entity. Doing some research on the error message, I've confirmed that the IDs are listed in Solution.xml under <RootComponents> and there is an XML file for them under FormXml/main for the respective entity types.

I tried running SolutionPackager with verbose error logging. There were no extra warnings and it showed it was seeing files with those IDs while processing the files.

For a bit of background on my changes. I've changed a field on Contact to no longer be required,updated some of the views to display the email field, and included a sitemap. Both of these forms were included in the previous version of my solution (no changes made to either one).

Does anyone know what could be causing it not to properly see those two items in the solution?

*This post is locked for comments

I have the same question (0)
  • yleclerc Profile Picture
    1,549 on at

    Same problem here. Was not happening before upgrading to 8.2.

    Did you find a solution?

  • Suggested answer
    yleclerc Profile Picture
    1,549 on at

    We have been having problems with a custom entity when we import it in production. That entity was included in the problematic solution. When removed from the managed solution, import went fine.

    I'm just hoping we won't need to make some changes to this entity.

  • Community Member Profile Picture
    on at

    I never did find exactly what the cause of the issue was. I ended up importing our current PROD version of the solution into the sandbox and re-adding the new components a couple at a time (it was a relatively small release). After adding each lot we tried importing the solution into PROD expecting it fail on a certain component, but it never did. Once everything was re-added to the solution we were able to properly import it into PROD.

    I still receive the "Following root components are not defined in customizations:" message when using Solution Packager, but it doesn't seem to be causing issues.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans