Active12 months ago

Microsoft Dynamics Crm Online

Get Microsoft Dynamics CRM serial number, A Microsoft Dynamics CRM deployment operates by using a single product key. However, each it Server in a. SuiteCRM has won the BOSSIE Award 20 for the world's best Open Source CRM. The page contains the download information and links for CRM 2013 products. Tip #130: Finding CRM 2013 Trial Key Licenses Once you get to the download page for Microsoft Dynamics CRM Server 2013 for obtain the code to install the onpremise implementation we often neglect to think to look on the page for the trial key license.

I have an installation of Dynamics CRM 2011 that is currently on a trial key. We would like to change to a production license before it expires. Is there somewhere in Deployment Manager or elsewhere that I can see how much time is remaining on the trial?

Arun Vinoth

2821 gold badge3 silver badges15 bronze badges

Saul DolginSaul Dolgin

1 Answer

I think I found the answer after a little more digging so I'll provide that here:

The License Key is tracked in the MSCRM_CONFIG database under the ConfigSettings table according to this thread:

So checking the other columns in the ConfigSettings table I found the InstallOn column. I assume that this is the date that the trial key was applied as part of the installation wizard. The following query will then show how many days are remaining in your trial:

The results will look something like this:

Saul DolginSaul Dolgin

Not the answer you're looking for? Browse other questions tagged licensingmicrosoft-dynamics-crm or ask your own question.

Occasionally when upgrading Dynamics CRM 2011 to CRM 2013, you may receive a warning that 'The Product Key is not compatible' in the environmental diagnostics wizard. If this happens, typicaly you can simply put the IgnoreChecks = 1 in the registry and avoid this issue.

Recently, I was working with a client and despite all my efforts of trying with a CRM 2013 MSDN key, a CRM 2013 VLK key, and the CRM 2013 trial key, I was getting the same error.

Midway through the upgrade, I received this warning:

For those of you hitting on keywords, let me give you the log entry as well.

14:26:50| Info| Executing Install action: Microsoft.Crm.Setup.Server.AddLicenseAction

14:26:51| Error| System.Exception: Action Microsoft.Crm.Setup.Server.AddLicenseAction failed. —> Microsoft.Crm.CrmException: Cannot upgrade to specified license type.

at Microsoft.Crm.Admin.AdminService.LicenseHelper.SaveLicense(LicenseData license, Version expectedExistingBuildVersion)

at Microsoft.Crm.Setup.Server.Utility.ConfigUtility.SaveLicense(String licenseKey, Version licenseSourceVersion)

at Microsoft.Crm.Setup.Common.CrmAction.ExecuteAction(CrmAction action, IDictionary parameters, Boolean undo)

— End of inner exception stack trace —, Error, RetryCancel, Option1

At that point, the only option was to restore the server and databases. Fortunately, CRM was a VM and we had taken the time to snapshot as well as make the database backups.

After a tremendous amount of searching, I finally pushed past all the posts regarding 2nd node installations and found this gem: https://community.dynamics.com/crm/f/117/t/121808.aspx

I give great credit to Rob Kszan for this miraculous discovery. I just wanted to elaborate just a touch on what he has there and how to practically put this in place.

First step, after the server and database restores, was to replace the license key in the MSCRM_CONFIG database. Directly changing the CRM Databases is not supported so MAKE SURE YOU HAVE A BACKUP.

Query the MSCRM_CONFIG database and the ConfigSettings table. Likely there is a single line. You are looking for the LicenseKeyV5RTM column. Replace the value with the CRM 2011 Trial Key : MQM2H-JYYRB-RRD6J-8WBBC-CVBD3. If you open the Deployment Manager at this point, CRM will likely tell you that it is expired. Don't worry.

During the Upgrade, replace the Key with the CRM 2013 Trial Key : CQWW3-TNXBF-HRQWC-CVTW9-M968H and perform the upgrade as you would normally. You'll note that no Product Key incompatibility is noted in the EDW.

Following the Upgrade, I highly recommend that you apply the latest rollup. Once that is in place, open the Deployment Manager and right click on the Micrososft Dynamics CRM on the left navigation and choose Change Product Key. You can now add the correct product key (which is in your VLK media as license.txt).

Hopefully this saves you some heartache and restores. Again, thanks to Rob Kszan for the initial discovery. Cheers!

Microsoft Dynamics Crm Online

Scott Jung @WilyGuy

Microsoft Dynamics Crm 2013 Serial Key