Microsoft Dynamics CRM (Archived)

Solution Import Failed - Error Code: 0x80040216

(0) Share

Report

Posted on by Ryan Maclean

3,070

Hi guys,

I'm trying to import a managed solution to my production environment and it fails with the following Error:

Error Code: 0x80040216

Error Text: Form factor code 0 is missing a control declaration

Can anyone shed any light on what might be causing this issue?

For reference, my Sandbox is currently in Dynamics 365, the Production Environment is CRM Online 2016. The solution is being exported for Version 8.1

*This post is locked for comments

I have the same question (0)

All responses (13)

Answers (0)

gman0104 821 on at

Like (0)

Report

Hi i am experiencing the same issue going from Dynamics 365 onpremise Dev to prodiction 8.1 onpremise. The fault is as follows

Form Account 0x80040216 Form factor code 0 is missing a control declaration

Was this reply helpful? Yes No
Suggested answer

Nadeeja Bomiriya 6,804 on at

Like (0)

Report

Hi Ryan,

You can't import a solution from a newer version to an older version.

Was this reply helpful? Yes No
gman0104 821 on at

Like (0)

Report

I thought exporting the solution from 365 as 8.1 would allow you to do this?

Was this reply helpful? Yes No
Nadeeja Bomiriya 6,804 on at

Like (0)

Report

Hmm.. Theoretically, yes.

This error (0x80040216) seems to be a new undocumented error.

http://dyn365apps.com/2017/02/09/quick-reference-dynamics-365-web-service-error-codes/

Was this reply helpful? Yes No
Ryan Maclean 3,070 on at

Like (0)

Report

Has anyone got any advice as to how to resolve this issue?

Was this reply helpful? Yes No
Franglais on at

Like (0)

Report

Does your solution only contain certain components for the selected entities? If so, try making a solution that contains ALL subcomponents for the selected entity. We faced an issue exporting an unmanaged solution from an 8.2 sandbox to an 8.1 production system which Microsoft said we could only fix if we imported all subcomponents for that entity. Not massively helpful if I'm being honest given you don't want to be pulling across everything every time!

Was this reply helpful? Yes No
Suggested answer

Shidin Haridas 3,497 on at

Like (1)

Report

Hi Ryan,

If you are willing to modify the customization zip file directly, then all you have to do is

1. Extract the files in the solution zip.

2. Open solution.xml

3. The very first line of this file should contain two keywords - 'version' & 'SolutionPackageVersion'. Modify them directly to the version of your target CRM tenant.

4. Rezip the files.

5. Try importing now.

PS: I would not recommend this, as this not supported, but as Nadeeja said, " error (0x80040216) seems to be a new undocumented error. "

Was this reply helpful? Yes No
Suggested answer

Nausher Sayeed 522 on at

Like (0)

Report

Hi Ryan,

Check the version(i.e. 8.1) of your solution while exporting. Make sure you select 8.1 .

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have the same issue when exporting a solution from Dynamics 365 On Premise to a CRM On Premise 2016.

Any updates on this?

Was this reply helpful? Yes No
Suggested answer

MDoddio73 1,910 on at

Like (2)

Report

[quote user="Ryan Maclean"]

Hi guys,

I'm trying to import a managed solution to my production environment and it fails with the following Error:

Error Code: 0x80040216

Error Text: Form factor code 0 is missing a control declaration

Can anyone shed any light on what might be causing this issue?

For reference, my Sandbox is currently in Dynamics 365, the Production Environment is CRM Online 2016. The solution is being exported for Version 8.1

[/quote]

Have you found a solution to this issue? If not, I think I found the culprit. In my instance, I was going from 8.2 (Dyn365 Online) to 8.1 on-prem. The "Control" form factor got me thinking about what is missing between 8.2 and 8.1. So on an educated hunch, I went to the entity throwing the error. In the Entity Control tab, I saw that Editable Grids was enabled.

I removed editable grids both on the entity throwing the error and the other entity in the solution that was enabled for editable grids.

This fixed the issue.

Was this reply helpful? Yes No