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 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
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 upgraded from CRM 8.2 to CRM 9.0 (onpremise). When i tried to enter data encryption key of the database from CRM 8.2 i am getting below error message:
Message: Encryption Symmetric Key password does not exist in Config DB.
Crm Exception: Message: Cannot decrypt existing encrypted data (Entity='EmailServerProfileBase', Attribute='IncomingPassword') using the current encryption key. Use 'activate' encryption key to set the correct encryption key
I can still confirm that i am using the same key from the CRM 8.2. Anyone see any workaround to get rid of this issue or what causing this issue in CRM 9.0.
I would suggest you to try the workaround to get rid of the issue.
Note: Before trying the mitigation request you to take a full backup of the database and perform the steps
Delete from OrganizationProperties where Id = '<ORG ID>' and ColumnName IN('SymmetricKeyPassword' , 'SymmetricKeySource')
--Remove key from DB
drop symmetric key CrmSymmetricKey1
--Reset all values to null in CRM DB
Update EmailServerProfileBase set IncomingPassword = null, OutgoingPassword = null
Update MailBoxBase set Password = null
Update queuebase set emailpassword = null
Update usersettingsbase set emailpassword = null
update LocalConfigStoreBase set Value=null where Value is not null
update ServiceEndpointBase set SASKey=null where SASKey is not null
update ServiceEndpointBase set SASToken=null where SASToken is not null
this error generally comes in couple of scenario
1. if source db key does not match the destination CRM database..
2. if user does not correct permission (not part of relevant security AD group)
refer some related article below for this..
one more work around is do delete all credential information queue password etc ... and then system might allow to reset this key again... I remember doing this years ago but can't remember exactly which list of attributes needs to be cleared for this right now..
Thanks guys for the suggestions. I know the key and its just restored database for the upgrade, i can still see from my existing environment that the key is correct. I made sure that the user is a member of the PrivUserGroup. But after the upgrade in CRM 365 key is empty and its not taking existing key as well.
We understand your concern.
There seems to be a encryption change in SQL Server 2017 which might lead to the above issues.
Please share the version number of the CRM and SQL servers, that will help us to identify the reason for the issue.
Thanks for looking into this issue. This is only happening with the upgraded organization. The default organization is working fine with out any issues.
Version number of CRM is 220.127.116.11( on premise) , upgraded from 18.104.22.168(on premise)
Sql Version: Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)
This issue is fixed. There is an encryption algorithm change in SQL 2017 compared to other versions of SQL. So we need to apply below CU as per the URL.
This helped to activate the key.
Business Applications communities