Answered by:
Cannot add solution components without roots

Question
-
we are trying to import a default solution from out QA system to (a copy of) the production system
the QA server was a clone of the production a few months ago with many customization having been made since then. The organization was upgraded from CRM 4 to 2011 two years ago and rollup 8 was applied to both environments
There are other warnings on the import, but I am not sure if they are critical at this point. when we import the solution, we get the following error
17:07:09.82
Root Components Insertion
Failure
0x8004F018
This item is not a valid solution component. For more information about solution components, see the Microsoft Dynamics CRM SDK documentation.
it seems that the error translates to: Cannot add solution components without roots. This item is not a valid solution component.
These messages are not very helpful. but how can we tell which component it is referring to? what are Root components?
Thursday, May 2, 2013 2:49 PM
Answers
-
we never did. what I ended up doing was creating 6 separate solutions, one for web resource, one for processes, one for security, one for plugins, one for schema, one for reports (I think that was all of them) and imported those
- Marked as answer by biconix Friday, August 16, 2013 6:47 PM
Friday, August 16, 2013 6:47 PM
All replies
-
I don't know... Where did you get this solution. It seems like someone may have injected something into it and made it invalid.
Jamie Miley
Check out RBA Today!
Check out my about.me profile!
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!Thursday, May 2, 2013 2:53 PMModerator -
this is an unmanaged solution (the default solution) that we created ourselves. we exported it from out QA system. it contains many customizationsThursday, May 2, 2013 2:56 PM
-
pardon my ignorance, but what are InsideView and Polaris? I have never heard of them (if they are some sort of managed solutions, we do not have them)Thursday, May 2, 2013 3:03 PM
-
My mistake, wrong thread
Jamie Miley
Check out RBA Today!
Check out my about.me profile!
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!Thursday, May 2, 2013 3:08 PMModerator -
-
we never did. what I ended up doing was creating 6 separate solutions, one for web resource, one for processes, one for security, one for plugins, one for schema, one for reports (I think that was all of them) and imported those
- Marked as answer by biconix Friday, August 16, 2013 6:47 PM
Friday, August 16, 2013 6:47 PM -
Thanks for letting me know. I will try separating them out as well.
Thanks!
DB
Debbie Bird
Friday, August 16, 2013 7:24 PM -
I hate this error, I've been fighting it for a few hours now and I can't find the 'component' that is missing from the RootComponents. No Guid, No Object Type, makes it nearly impossible to find.
I did find a couple of RootComponents that weren't in the customizations.xml. I could export & import theses items without problem, just not with the default solution.
Saturday, June 27, 2015 10:54 PM -
I know my post is a little late, but I've previously run into this issue using CRM Online.
In my case I was trying to import a default solution into a new CRM Online Instance Organisation. The new version of CRM Online was running on a slightly newer version that when the customization's were exported.
I have found that using a single solution to export works as long as that single solution contains only my own custom entities + only the OOTB components that I have actually changed (Leave out any OOTB entitiy that has not been modified).
I suspect the issue is that default solution contains references to system components that can be exported but are none the less included in the customisation file.
Thursday, July 16, 2015 9:45 AM