Customer experience | Sales, Customer Insights,...

Solution import was failed.

(0) Share

Report

Posted on 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?

I have the same question (0)

All responses (13)

Answers (0)

Suggested answer

Charles Abi Khirs 3,569 on at

Like (0)

Report

Hello,

Based on the error, you are trying to import a managed solution that contains some components previously imported as unmanaged which is not allowed because "This will cause an invalid layering of solutions on the target system".

Option 1: Import the component already exists on the target system using an unmanaged solution

Option 2: Delete the unmanaged solution previously imported where the component exists and then import your managed solution in the target system

Was this reply helpful? Yes No
Suggested answer

AJ-22040756-0 on at

Like (0)

Report

Hi Partner

This is by design, from the description it seems you have an unmanaged version of AppModuleRoles in Target system, now you are trying to import a managed solution with the same AppModuleRoles. This is not supported,

Instead, you can import the unmanaged solution again or Delete the unmanaged AppModuleRoles and import the managed solution.

Was this reply helpful? Yes No
JacquesNL 800 on at

Like (0)

Report

Hi, I have the same problem. Where can I find the AppModuleRoles component so I can delete it?

Was this reply helpful? Yes No
Suggested answer

Charles Abi Khirs 3,569 on at

Like (1)

Report

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

Was this reply helpful? Yes No
JacquesNL 800 on at

Like (0)

Report

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

Was this reply helpful? Yes No
Suggested answer

Charles Abi Khirs 3,569 on at

Like (0)

Report

Yes, unless you have referenced the component in a form, relationship... where you can simply remove it from your solution, without editing the file.

Was this reply helpful? Yes No
JacquesNL 800 on at

Like (0)

Report

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?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

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

Was this reply helpful? Yes No
Suggested answer

Charles Abi Khirs 3,569 on at

Like (0)

Report

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

docs.microsoft.com/.../appmoduleroles

Was this reply helpful? Yes No
JacquesNL 800 on at

Like (0)

Report

I have the solution:

1.

2.

Was this reply helpful? Yes No