Personalized Community is here!
Quickly customize your community to find the content you seek.
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
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 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 | Upcoming TechTalks
I'm doing a new install of CRM 2015 and creating the first org. Part way through the installation I'm getting the error above. The full error is:
This is a fresh install of SQL 2014 on a Win2K12R2 server, and the only thing present thus far is the CRM database. It has never been used in any sort of replication (referenced in other solutions).
When I do "select * from sys.asymmetric_keys" the name "MSCRMSQLCLRKEY" does not exist. I have confirmed the DLL is present in the DATA folder on the SQL server.
I have tried to add the key as mentioned in other solutions:
IF NOT EXISTS (SELECT * FROM sys.asymmetric_keys WHERE name = 'MSCRMSqlClrKey') BEGIN CREATE ASYMMETRIC KEY MSCRMSqlClrKey FROM EXECUTABLE FILE = 'E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\Microsoft.Crm.SqlClr.Helper.dll'; END
and I get:
Msg 15396, Level 16, State 1, Line 1An asymmetric key with name 'MSCRMSqlClrKey' already exists or this asymmetric key already has been added to the database.
I'm stuck at this point. I can Ignore the error and the installation will complete, but the error appears again when I try to import my CRM2013 database to this instance.
Any suggestions / ideas as to how to troubleshoot and resolve this issue? Any help is appreciated.
Check if select count(*) from sys.asymmetric_keys returns 0
No, it returns 4 values, but as noted above none have the name "MSCRMSQLCLRKEY"
Could you please inform me whether you have GP server as well ? And if yes, is the database of the GP server on the same SQL server which is of the CRM 2015 server ?
Your response is awaited!
Thanks & Regards,
Microsoft Dynamics CRM
I am receiving the same error message. This is the second time I have encountered this error on two separate installations. Both of the installations have had the GP DB on the same SQL server as I am attempting to install CRM.
I received a SQL Script to run on the MASTER DB from Microsoft Support the first time I encountered the issue and plan on using it again. I would like to know what it is that is causing the issue and how I can avoid it in the future. Is it something tied to GP?
I am experiencing the same problem but with CRM 2013 installation (upgrade from 2011 to 2015 through 2013). I learned that the SQL server I have for this exercise had a GP database previously. Your answer refers to a specific script which has to be run in such case. Can you please provide the script if you have one.
In my case, I found there were 2 asymmetric keys which were belonging to GP. GP database was not hosted on that SQL server anymore, so after deleting the logins for those asymmetric keys and dropping both keys from the master database, the CRM installation continued with no errors.
Are you able to post the script or what it does? I too am having this issue and installing it on the same SQL as our GP databases...Thanks
The script I received ended up not doing anything. In the end I was told to ignore the error which allowed me to continue with the installation. I have yet to notice any issues as a result of this. The other bit of information that I found stated that this is not an issue if you install CRM first and then GP.
Ok I will try it out. Thanks for responding
I ran into this as well with a CRM 2015 installation that was pointed to a SQL Server instance that contained Dynamics GP 2015. I contacted Microsoft CRM support and verified that this error is only thrown in this scenario because both Dynamics GP 2013 and later and Microsoft Dynamics CRM are using the exact same login name, 'MSCRMSqlClrLogin'. If you add the HKLM\Software\Microsoft\MSCRM\IgnoreChecks as a reg_dword key with a value of 1 on the Microsoft CRM Server, you can get by this error message and provided you don't have any other blocking errors, should see no problems from having ignored this particular error.
Business Applications communities