Solution Import error "This solution cannot be uninstalled because the ProcessTrigger with id..."

(0) Share

Report

Posted on by rskadk1

886

Im suddenly facing import issues when importing from test environment to production environment. I export the solution as a managed solution from test environment and then import it into production environment.

But I now get the error: "This solution cannot be uninstalled because the ProcessTrigger with id a480b103-e2c5-e511-8104-005056b617b4 is required by the CaseManagement solution. Uninstall the CaseManagement solution and try again."

In test I have adjusted some business rules and im pretty sure that it's these that are causing the errors. But how can I get it imported into production so existing rules in production are replaced by the new ones with corrections?

---

--> I read something in this thread https://community.dynamics.com/crm/f/117/t/180593?pi51685=2#responses

"The problem is solved by deleting the target Business Rules, finally if you are importing a new versión of them, there would not be a problem to do this, so delete all business rules and import them again using your updated solution"

But if I follow this procedure in production environment and delete them I cannot delete them from a managed solution. I guess I will need to create a unmanaged solution in production and add the related entity and then delete them from there? Or what should I do? And is there any drawbacks by deleting them?

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (0)

Community Member on at

Like (0)

Report
Hello,

I have the same error and you can delete a business rules or an other managed composent on the personalization.

Was this reply helpful? Yes No
Suggested answer

Rawish Kumar 13,758 on at

Like (0)

Report

Hi there,

you are right if you try to delete the component from customization it will say it is required by a managed solution - you have to remove the dependency : i will suggest you to follow below approach :

community.dynamics.com/.../how-to-delete-components-from-managed-solution-in-dynamics-crm-2016-without-using-holding-solution

Was this reply helpful? Yes No
rskadk1 886 on at

Like (0)

Report

I'm using 2015 and there cannot benefit from the way 2016 is working. But what I don't understand is why it's necessary to remove the business rule. Why won't CRM just overwrite the current when importing the managed solution, instead of giving me the error?

Was this reply helpful? Yes No
Jan Gracelin Jeno 150 on at

Like (0)

Report

This is a product bug in 2015 and it is fixed in the update.

Some business rules may cause this issue.

Resolution:

Raise a ticket to microsoft, they will suggest to comment the business rules in customizations.xml as a workaround.

We had the same problem and it worked.

Don't do this without microsoft's assistance.

Hope this helps!!

Was this reply helpful? Yes No
rskadk1 886 on at

Like (0)

Report

Hi Jan,

Thanks for your answer. Good that other have the same issue. In regards to the solution they provide, will it still be possible to import changes in business rules from test to production without the error? Or to they comment it out, so the changes are not imported?

Was this reply helpful? Yes No
Jan Gracelin Jeno 150 on at

Like (0)

Report

Could you please give your crm version?

Was this reply helpful? Yes No
rskadk1 886 on at

Like (0)

Report

CRM 2015

Was this reply helpful? Yes No
Jan Gracelin Jeno 150 on at

Like (0)

Report

Version number

Was this reply helpful? Yes No
rskadk1 886 on at

Like (0)

Report

Hi Jan, It's CRM 2015 v. 7.0.1.1.129

Was this reply helpful? Yes No