Step-by-Step Microsoft CRM 1.2 Migration to CRM 3.0 Part – IV


So, now you have restored the database, corrected the mappings in Deployment.xml and we are ready to install CRM 3.0. Before you actually install CRM 3.0, run Microsoft CRM 3.0 Upgrade Advisor Wizard (CrmUpgradeAdvisor.exe). Advisor Wizard is a diagnostic tool that you can use to determine if your Microsoft CRM 1.2 installation can be upgraded to Microsoft CRM 3.0 and also make sure you have the licensing information. 

You might see some Errors in the Upgrade Advisor report as shown and update the SQL SP3 to SP4;


+ <Error CheckId=”E195606F-7BE7-49dc-9BFB-ADC4F144C79D CheckType=”Microsoft.Crm.Setup.Server.SqlServerValidator GroupId=”Sql Description=”Version message=”Minimum required version is SQL 2000 SP4 (8.0.2026).>

  <MoreInformation />



+ <Error CheckId=”D6E8BA5F-B1E9-40ba-B36C-E06F837FDA92 CheckType=”Microsoft.Crm.Setup.Server.SqlServerValidator GroupId=”Metadata Description=”Version message=”Minimum required version is SQL 2000 SP4 (8.0.2026).>

  <MoreInformation />




The most important thing is to make sure the Windows and SQL Service Pack and HOT FIX level of the production server is similar to that of the test server.

If the versions do not match then an error may occur when you reinstall Microsoft CRM to a new server, “Setup was unable to register the security service.” If you click Ignore to continue the install process you will receive the error, “Error 1053: The service did not respond to the start or control request in a timely fashion.” when trying to start the Microsoft CRM Security Service after a reboot.

This is due to a mis-match in the Service Pack level on the test server as compared to the actual database version which means the Microsoft SQL server specified in the MSCRM registry key is  not equal to Microsoft SQL server that holds the CRM databases. You will find a list of hotfixes installed in the following location: C:\Program Files\Microsoft CRM\Hotfix Keyfiles\Server and all you have to do is to install those hotfixes on the test server. But in case you do not have all those fixes then, there is a cheeky workaround which I found in the NG as follows;

To resolve this, you have to compare the database version with MSCRM registry key with the production server and you will need to modify the registry so that MSCRM database version and registry version match.

1. On the CRM SQL server open SQL Enterprise Manager by clicking Start, click Programs, Click Microsoft SQL Server and then finally click Enterprise manager.

2. Within SQL Enterprise Manager click the + sign to the left of the Databases folder and then click the + to the left of the Your_Organization_Name_MSCRM database.

3. Click on the Tables object beneath the Your_Organization_Name_MSCRM database and then right-click on the table BuildVersion in the right window. Select Open Table and then click Return all rows.

4. Within the BuildVersion table note the values for BuildNumber, MajorVersion, MinorVersion, and Revision. You will need these values later when verify them against the registry.

5. Now go to the Microsoft CRM Server and click Start, click Run, type regedit and click OK.

6. Locate the following subkey:


7. Within the MSCRM subkey find the Database Version registry value, right-click on it and select Modify.

8. The Database Version registry value will look something like the below value:


9. Modify this value to reflect BuildNumber, MajorVersion, MinorVersion, and Revision values that you had noted from the BuildVersion table in step 4.

        a. The MajorVersion will reflect the first number in the above example.
        b. The MinorVersion will reflect the second number in the above example.
        c. The BuildNumber will reflect the third number in the above example.
        d. The Revision will reflect the forth number in the above example.
        NOTE: You will probably only have to modify the Revision number.

10. Click OK.

11. Now right click on CRM_Server_Version registry value and select Modify.

12. Make sure that the CRM_Server_Version registry value matches the value of the Database Version registry value that you just modified.

13. Click OK and close the registry editor.

14. Now on the CRM Server click Start, click Run, type services.msc and click OK.

15. Within the Services window locate the Microsoft CRM Security service, right-click on it and select Start.

One thought on “Step-by-Step Microsoft CRM 1.2 Migration to CRM 3.0 Part – IV

Leave a Reply

Your email address will not be published. Required fields are marked *