Microsoft Dynamics CRM (Archived)

CRM 2011 Import Solution error after rollback to Update Rollup 16 from Update Rollup 17

(0) Share

Report

Posted on by mathieu_gumez

155

Hi All,

We updated our installation of CRM 2011 to Rollup 17.

We were affected by the bug described there :

https://community.dynamics.com/crm/f/117/t/128100.aspx

We then rolled back CRM 2011to Rollup 16.

And now we cannot import a updated managed solution on one of our organizations, the import fails with the following error:

Crm Exception: Message: There should not be more than one component instance for a solution being upgraded. Solution id: blablabla, ErrorCode: -2147220970

It fails when processing a custom entity not modified by the update (similar to something mentionned in this old post).

And the strange thing is, the same solution is correctly imported in another organization on the same server.

Has anyone else had a similar issue ? Or any idea on a correction/workaround/etc. ?

Regards,

Mathieu

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

Dave Ireland on at

Like (0)

Report

Hi Mathieu;

The issue with the deployment manager breaking in RU17 was resolved in RU18. (Microsoft did create a hotfix for this issue - you can see my blog here: www.salentica.com/crm-2011rollup-17-breaks-deployment-manager )

Are you able to go back to RU17 and then to RU18?

Was this reply helpful? Yes No
mathieu_gumez 155 on at

Like (0)

Report

Hi, sorry for the late update...

We went back to RU17 and then to RU18. We can now import solution with the last update.

We reextracted the solution from the updated dev organization and tried to import it in the test organization. Unfortunately, We still get the 'only one component instance' error when importing the solution.

Seems like the successive roll up / back / up messed with the data...

Is there any tool or SQL script that can help pinpoint the source of the error ?

Was this reply helpful? Yes No
Suggested answer

Kamakshi Parate on at

Like (0)

Report

Hello Mathieu,

Could you please share the error message that you receive while importing the solution?

Also share the log file with Screenshot of the error message.

Thanks,

Kamakshi Parate

Microsoft Dynamics™ CRM Support Engineer

Was this reply helpful? Yes No
mathieu_gumez 155 on at

Like (0)

Report

Hello Kamakshi,

We opened a ticket and are currently working with the support to solve the problem.

I'll post some feedbacks for the community once it's done.

Was this reply helpful? Yes No
C.Schulte 70 on at

Like (0)

Report

Hello mathieu_gumez,

we have a customer with the same problem.

They had RU18 and couldn't import an update of a managed solution.

They rolled back to RU16 and the problem still occurs.

The error-message in the import-log is:

"There should not be more than one component instance for a solution being upgraded. Solution id: blablabla"

If you have a solution, please inform us.

Was this reply helpful? Yes No
Verified answer

mathieu_gumez 155 on at

Like (0)

Report

Hello all,

It appears, in our case, that some localized labels were created in the organization database, with the ID mentionned in the error message. Look for them in LocalizedLabelView.

Those labels were not present in dev database, only in the test platform.

Deleting them solved the problem and doesn't seem to alter the CRM operations.

But take some precautions and try the correction on a test platform before fiddling with data on a prod platform.

Was this reply helpful? Yes No
yleclerc 1,549 on at

Like (0)

Report

Hi Mathieu,

How did you figure out which localized labels were the problem?

Error Message:

There should not be more than one component instance for a solution being upgraded. Solution id: xxxxxxxxx

We looked up the database and that solution contains over 16,000 labels... How can we identify the ones that have to be deleted?

Was this reply helpful? Yes No