Fix for CRM 2013 SP1 UR3 The product key is not compatible with the installed version of Microsoft Dynamics CRM

Today, when I setup the secondary front end server of the existing CRM 2013 system with SP1 UR3, I encounter the following error message.

The product key is not compatible with the installed version of Microsoft Dynamics CRM.

When I searched around the web with the error message, this is the first article in the results and the issue is quite similar to mine.
http://blogs.msdn.com/b/atif/archive/2012/01/22/the-product-key-is-not-compatible-with-installed-version-of-microsoft-dynamics-crm.aspx

But trying out the resolution in the post didn't actually resolve my issue. May be it is the separate issue for CRM 2011.


After searching a bit further, I came across the following forum thread.
https://community.dynamics.com/crm/f/117/t/124102
In the forum thread, Abacuse mentioned about the solution to integrate rollup to the RTM version.

Since my existing CRM 2013 system was installed with SP1 UR3, I extracted the UR3 of CRM 2013 SP1 file "CRM2013-Server-KB3016464-ENU-amd64.exe" with Winrar in one of the folders.
After extracting, find the only .msp file in the extracted folder and note it down for next step.

Then, create the config XML file with the name "SetupConfig.xml" in the same location as SetupServer.exe of the CRM Server installation folder.
This is the content of my config XML file and the file path of the .msp file need to be changed accordingly.
 <CRMSetup>  
  <Server>  
  <Patch update="true">C:\CRM Installer\SP1 UR3\CRM2013-Server-KB3016464-ENU-amd64\server_kb3016464_amd64_1033.msp</Patch>  
  </Server>  
 </CRMSetup>  

After that, open the command line and change directory to the CRM Server installation folder and run the following command based on the name of the .xml file which was created in the previous step.
SetupServer.exe /config SetupConfig.xml

If you follow the steps correctly, the setup should start with the following screen instead of normal setup first page.



If the Setup is using the patch from the same rollup as the existing CRM instance, the product key compatibility error will not be shown anymore.

Comments

Popular Posts