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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Error when importing s...
Microsoft Dynamics CRM (Archived)

Error when importing solution

(0) ShareShare
ReportReport
Posted on by Esben Bugge 55

Hi all,

I am trying to import a CRM solution. I get the following error and the import fails:

"Cannot add a Root Component post of type 1 because it is not in the target system"

Can anyone explain what this error means in detail? How can I see which component it cannot add? What does it mean when it says "is not in the target system"? Since last import I have deleted a couple of entities in the target solution as these entities have been recreated in the source solution. Does the error mean that there is some kind of conflict between the old and the re-created entities?

*This post is locked for comments

I have the same question (0)
  • alf Profile Picture
    alf 17,915 on at

    Hi Esben,

    Do both of your servers have the same update rollup ?

    When you exported your solution, did you get any warnings about required components not being included??  This is often the cause of this message where a solution requires entity a or b and it is NOT  found.

  • Suggested answer
    Nizar JLASSI Profile Picture
    Nizar JLASSI 2 on at

    Hi Esben,

    This error looks like an error that I got when I was trying to import a CRM solution.

    The Error was : 

    Cannot add a Root Component 12a9d3f2-8143-47d9-879f-bd9687d29fd8 of type 29 because it is not in the target system.

    When I opened my solution.xml file in the solution and I searched the Guid : 12a9d3f2-8143-47d9-879f-bd9687d29fd8 I found a line like this :

    <RootComponent type="29" id="{12a9d3f2-8143-47d9-879f-bd9687d29fd8}" />

    To know type 29 what means, go to your SDK folder and open EntityMetadata.xlsx file, go to AttributePicklists Tab and filter your LogicalName column with the value : missingcomponenttype, 

    After that, search 29 in the OptionValue column, So 29 = Workflow.

    So, for your case : type = "1" means Entity , and you will find in your solution.xml file a line like this :

    <RootComponent type="1" schemaName="post" />

     

    Now, you should know that all components in <RootComponent> Tag should exist in the customizations.xml file.

    It means that you, or someone else, has edited the customizations.xml file and deleted the <entity> tag that contains <Name LocalizedName="Post" OriginalName="Post">Post</Name> tag.

    So, if you don't need this entity in your solution you should delete the  <RootComponent type="1" schemaName="post" /> tag from the solution.xml file. 

  • Suggested answer
    AAToledano Profile Picture
    AAToledano 92 on at

    Thank you very much, this worked great!

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
JS-09031509-0 Profile Picture

JS-09031509-0 3

#2
AS-17030037-0 Profile Picture

AS-17030037-0 2

#2
Mark Eckert Profile Picture

Mark Eckert 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans