Breaking news from around the world
Get the Bing + MSN extension
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
I'm getting the following error when trying to upgrade our organization from version 8.2 (on premise) to 9.0 (on premise):
Dear DOSTODEVSKY , all,
I'm trying also to upgrade 8.2 to 9 on premise, on tests servers. When importing the organisation from a SQL Backup, i have exactly the same error , which root cause seems to be the following lines. With the same exact ID .
Hi Nicolas, thanks for your feedback. Let me know how it goes.
The organization upgrade from 8.2 to 9.0 for on-premise is not working - broken in multiple ways. There are threads about it here: community.dynamics.com/.../300597 and here: community.dynamics.com/.../300064
Long story short, it's broken, there is a very unsupported workaround for at least one of the issues (go through the second thread for details), and it's been reported to and acknowledged by MS who is working on a fix to be released.
Hi Allison, any idea when the fix will be released?
Nope - they won't give me a timeframe.
I tried importing a new organization from 8.2.3 and the same exception is still being thrown.
Same again. I've upgraded every possible patch, tried to make a lot of cleanup in 8.2 DB, logs in CRM , etc...
But exactly the same error.
Did you try the patch that was released for a particular client :300064?pi61802=4#responses ?
I guess we'll have to wait for the official Microsoft patch and try again.
I applied the aforementioned patch and still getting the same exception.
I think that it has something to do with the organization language (french):
Hello Nicolas Mazurier,
Does your organization language happen to be different than English?
If you are still running into this error when trying to import your 8.2.3.x org into a v9 deployment, you will need to log a support ticket in order to get a critical on demand (COD) setup fix. Eventually this will be part of a self-healing fix but until that is available, you will need to install this fix prior to importing an organization. When you log the ticket, please request the COD for build 220.127.116.1141. Also, include the error from your log file.
Keep in mind that this fix does contain a couple of other setup fixes but is required in order to help workaround the following error. If your crmdmsnapin.log contains the exact reference to the following highlighted below, these instructions should allow you to workaround the error.
12:44:46| Info| Executing: action Bin\Microsoft.Crm.SE.DatabaseActions.dll:Execute with id 1a3f858e-afd4-4423-9f32-77cd0952b727 of type DllMethod to Cleanup orphan label records.. 12:44:46| Info| Cleanup orphan label records. 12:44:46| Info| Action Bin\Microsoft.Crm.SE.DatabaseActions.dll:Execute with id 1a3f858e-afd4-4423-9f32-77cd0952b727 of type DllMethod to Cleanup orphan label records. failed on attempt 2. Retrying in 30 seconds. Exception: Value cannot be null. Parameter name: type 12:45:16| Info| Action Bin\Microsoft.Crm.SE.DatabaseActions.dll:Execute with id 1a3f858e-afd4-4423-9f32-77cd0952b727 of type DllMethod to Cleanup orphan label records. failed on attempt 3. Retrying in 30 seconds. Exception: Value cannot be null. Parameter name: type 12:45:46| Info| CrmAction execution time; UpgradeDatabaseAction; 00:01:20.1309843 12:45:46| Error| Installer Complete: OrganizationUpgrader - Error encountered
Once, you receive the fix, install it on all of the Dynamics servers in the deployment and then reboot if prompted.
After the fix is installed, you will be required to perform additional instructions before importing the org.
1. Browse to the following location on your dynamics server and copy the ServerRelease.xml file.
C:\Program Files\Dynamics 365\LangPacks\1033\Xrm\sql\9
2. Now, browse to the folder of the language code of the org that you are trying to upgrade. For example, if the language code is 1053, browse to C:\Program Files\Dynamics 365\LangPacks\1053\Xrm\sql\9.
3. Rename the file ServerRelease.xml in the file path from step 9. This could be something like ServerRelease.xmlOriginal.
4. Copy the ServerRelease.xml file from step 1 into the file path from step 2.
5. Perform steps 1 through 4 on any other frontend and backend servers in the Dynamics deployment.
6. Finally, start Deployment Manager and import the org. It should complete successfully.
NOTE: The above COD fix 18.104.22.16841 is not required to resolve this issue but is highly recommended to have installed on your Dynamics servers as it does contain a few updates to address other org upgrade errors.
Thank you Shawn, firstly I installed Update 0.2 For Dynamics 365(CRM9.0-Server-KB4458112-ENU-Amd64) then I've done specified steps that you said, import organization is succeed.
Also this error is gone " at Microsoft.Crm.Tools.Admin.ImportOrganizationInstaller.ImportAndUpgrade(OrganizationInfo organizationInfo) ---> System.Exception: Error.ActionFailed Microsoft.Crm.Tools.Admin.UpgradeDatabaseAction ---> Microsoft.Crm.CrmException: Error in Action: Bin\Microsoft.Crm.SE.DatabaseActions.dll:Execute on attempt 3. System.ArgumentNullException: Value cannot be null."
Hi Shawn Nulph,
Thanks for your answer! I tried the workaround after applying the (unofficial) patch and importing our org to version 9 was successful !
Thank you so much for that solution! Installing the 22.214.171.12441 and copying ServerRelease.xml from 1033 folder to my own language folder (1044) helped. Now I can upgrade :D
Business Applications communities