Customer experience | Sales, Customer Insights,...

Solution import was failed.

Like (0) Share

Report

Posted on 24 Jan 2020 15:15:30 by Community Member

Import of app module(s) failed: A managed solution cannot overwrite the AppModuleRoles component with Id=23608193-3e79-41a4-9b3c-0fe31a850ba5 which has an unmanaged base instance. The most likely scenario for this error is that an unmanaged solution has installed a new unmanaged AppModuleRoles component on the target system, and now a managed solution from the same publisher is trying to install that same AppModuleRoles component as managed. This will cause an invalid layering of solutions on the target system and is not allowed.

Can anybody help me out to resolve this issue?

All responses (13)

Answers (0)

JacquesNL 800 on 10 Feb 2020 at 17:58:39

Like (0)

Report

RE: Solution import was failed.

Unfortunately my proposed solution was not helping. Would it help to delete (not remove) the apps from the unmanaged solution and import it at the target solution?
JacquesNL 800 on 10 Feb 2020 at 15:43:52

Like (0)

Report

RE: Solution import was failed.

I can uncheck all roles, but the system puts back the system admin and system customizer role immediatly.
JacquesNL 800 on 10 Feb 2020 at 15:42:45

Like (0)

Report

RE: Solution import was failed.

I was not able to do this because the Model Driven apps where managed.
JacquesNL 800 on 10 Feb 2020 at 15:17:34

Like (0)

Report

RE: Solution import was failed.

I have the solution:

1.

2.
Suggested answer

Charles Abi Khirs 3,569 on 10 Feb 2020 at 15:10:07

Like (0)

Report

RE: Solution import was failed.

Can you try to uncheck the security roles given to the app? the "AppModuleRoles" is mainly related to this.

docs.microsoft.com/.../appmoduleroles
Community Member on 10 Feb 2020 at 15:10:01

Like (0)

Report

RE: Solution import was failed.

For us there was a model driven app which is of type unmanaged type. When we were trying to import the solution which contians the managed model driven app it generated the error. we deleted the model driven app from the UAT env and re imported the app as a managed type.

Kindly accept this as a solution if I am able to help you out.\

Thanks and Regards

Naveen Gupta
JacquesNL 800 on 10 Feb 2020 at 15:03:08

Like (0)

Report

RE: Solution import was failed.

Yes, that I understand. The 'funny' thing is when I search for the GUID in the customizations XML, 0 result.

If I search the GUID with Fetch XML I find the AppModuleRole record which is linked to the Security Role: System Administrator with an unmanaged state in a solution which I can't find. Is there another way to delete these AppModuleRoles?
Suggested answer

Charles Abi Khirs 3,569 on 10 Feb 2020 at 14:36:55

Like (0)

Report

RE: Solution import was failed.

Yes, unless you have referenced the component in a form, relationship... where you can simply remove it from your solution, without editing the file.
JacquesNL 800 on 10 Feb 2020 at 14:30:23

Like (0)

Report

RE: Solution import was failed.

So then we are talking about editing the customizations.xml coming from the source organization?
Suggested answer

Charles Abi Khirs 3,569 on 10 Feb 2020 at 14:24:40

Like (1)

Report

RE: Solution import was failed.

You can open your customizations.xml file and search for the GUID to know where it exists

Community site session details

Solution import was failed.

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

Jonas ”Jones” Melgaard – Community Spotlight

Kudos to the March Top 10 Community Stars!

Leaderboard

Featured topics

Product updates

Community site session details

Solution import was failed.

Helpful resources

News and Announcements

Quick Links

🌸 Community Spring Festival 2025 Challenge 🌸

Jonas ”Jones” Melgaard – Community Spotlight

Kudos to the March Top 10 Community Stars!

Subscribe to this forum!

Select categories

Leaderboard

Featured topics

Product updates