Dynamics Community Forum Thread Details

I am facing an issue while importing a Dynamics CRM 8.2 On-Premise organization on a new server before upgrading it to Dynamics 365 v9.1.

Environment Details:

Source Environment: Dynamics CRM 8.2 On-Premise Production
Target Environment: New Server for Org Import and Upgrade to v9.1

Scenario:

I took a full SQL backup of the current Production organization database.
Restored the database on a new server.
Tried importing the organization using Deployment Manager.

Organization import fails with the below error:

Error:
[Error][2] Message: Importing solution threw an unforeseen exception
Source : Microsoft.Crm.Extensibility
Method : Execute
Error : Could not update parent report link for the child report 4ec85c59-7d04-e711-90e6-00155db8745a
Stack Trace : at Microsoft.Xrm.Tooling.PackageDeployment.CrmPackageCore.ImportCode.BaseImportCustomizations.ExecuteImportSolution(ConfigSolutionFile Sol, String sSolutionImportFilePath)

Observations:

I searched the failing GUID across the entire organization database but could not find any record/reference for this GUID.

Additional Findings:

We have an old managed solution named "BUGSXFixes" deployed around 2018.
This solution contains:
Reports
Entities
Plugins
JavaScript
Other customizations

We suspect there may be stale/corrupted managed solution metadata or report metadata causing the organization import failure.

To resolve this, we are planning the below approach:

Create a new solution in the current Production environment.
Add all the same components that are present in the old solution "BUGSXFixes", including:
Reports
Entities
Plugins
JavaScript
Workflows
Other custom components
Export this newly created solution as a Managed solution.

Import the Managed solution back into the same current Production environment without deleting the old solution initially.

The expectation is that CRM will create a fresh managed solution layer and refresh/rebuild the component metadata and report metadata internally.
After successful import and validation, take a fresh backup of the Production organization database.
Restore the backup on the new server.
Retry the Organization Import process again.

Goal:

The main goal of this approach is to refresh the managed solution metadata and report component metadata so that the Organization Import process can complete successfully on the new server.

Also, I would like to understand whether this approach can potentially break the current Production environment in any way.

Since we are:

creating a new solution from the same current Production environment,
adding the same existing components already present in Production,
and importing the Managed solution back into the same environment without deleting the old solution initially,

our expectation is that CRM should only create an additional managed solution layer and refresh the metadata internally.

Could this approach cause any issues such as:

duplicate components,
report issues,
plugin/workflow impact,
managed layer conflicts,
or any Production instability?

Has anyone tried a similar approach before for resolving stale managed metadata or report metadata issues during Organization Import/Upgrade scenarios?

Categories:

Dynamics 365 general

Power Platform integration