Dynamics Community Forum Thread Details

We faced problem while upgrading from CRM 2013 to CRM 2015

Case History

- Our CRM Organization was originally upgraded from CRM 4.0 to 2011 and then to 2013, it hold some of our customizations in addition to Managed solutions like Adxstudio

-While we were trying to upgrade from 2013 to 2015 the upgrade didn’t go smoothly with Adxstudio Solution, and because we didn’t depend on it currently so we tried to uninstall it,

-After Uninstalling the Server we tried to upgrade to CRM 2015 it should an error regarding some dependencies to the Adxstudio, when we checked the 2013 Environment we found that some of the Adxstudio entities and components still exist although the uninstall showed no error.

-We tried to re install the Adxstudio we got the attached error.

Current CRM Status

-we have managed components linked to deleted managed solution and have dependencies to other system entities

-we cannot re import Adxstudio

-We cannot upgrade to 2015

-Many entities should be removed with the deleted solution bust still exists

What we expect

-We need to upgrade to CRM 2015 then to CRM 2016 then to 365 (On Premise)

Hi Khalil,

You need to find out what these dependencies to remove them from your solution. Try to export your customisations and go through the XML. Also, make sure you have the right rollup to allow you to upgrade.

Have you considered a different upgrade so instead of "in-place" upgrade that you are doing, you go for a new instance upgrade where you export your solution and components into a new CRM 2015 instance?

There are three different upgrade options:

Migrate by using a new instance of SQL Server. We recommend this option for upgrading Microsoft Dynamics CRM Server 2015. Although this option requires a different computer for Microsoft Dynamics CRM and a different instance of SQL Server, it provides the least amount of potential downtime for users since the existing deployment can remain functioning until the upgrade is completed and verified.
Migrate by using the same instance of SQL Server. This option requires a different computer for Microsoft Dynamics CRM Server 2016, but will upgrade in-place the configuration and default organization databases using the same instance of SQL Server. If issues occur during the upgrade, you must roll back to the previous version to avoid significant downtime.
In-place upgrade. Although this option doesn’t require a different computer for Microsoft Dynamics CRM Server 2016 or a different instance of SQL Server, it poses the greatest risk if upgrade issues occur because a roll back and reinstall of the previous version of Microsoft Dynamics CRM will be required to avoid potential downtime.

You can see more details here:

https://technet.microsoft.com/en-gb/library/hh699673.aspx

https://technet.microsoft.com/en-us/library/hh699716.aspx

Hope this helps! Please mark as verified answer if you found this response helpful

Quick Links

Leaderboard