web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / CRM 8.2 to 9.0 upgrade...
Customer experience | Sales, Customer Insights,...
Suggested Answer

CRM 8.2 to 9.0 upgrade encryption key error

(0) ShareShare
ReportReport
Posted on by thomas.s 122

Hi,

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.

Thanks

I have the same question (0)
  • Suggested answer
    Prasanna Lakshmi T J Profile Picture
    Prasanna Lakshmi T J on at

    Hi Thomas,

    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

    use MSCRM_CONFIG

    Delete   from OrganizationProperties where Id = '<ORG ID>' and ColumnName IN('SymmetricKeyPassword' , 'SymmetricKeySource')

    --Remove key from DB

    use ORG_MSCRM

    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

  • Mayank Pujara Profile Picture
    Mayank Pujara 830 on at

    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..

    dynamicscrmgirl.wordpress.com/.../

    blog.martinlund.it/.../

    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..

  • thomas.s Profile Picture
    thomas.s 122 on at

    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.

  • Prasanna Lakshmi T J Profile Picture
    Prasanna Lakshmi T J on at

    Hi Thomas,

    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.

  • thomas.s Profile Picture
    thomas.s 122 on at

    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 9.0.9.4( on premise) , upgraded from 8.2.13.21(on premise)

    Sql Version:  Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)

  • Suggested answer
    thomas.s Profile Picture
    thomas.s 122 on at

    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.

    support.microsoft.com/.../sql-server-2017-cannot-decrypt-data-encrypted-by-earlier-versions

    This helped to activate the key.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 73 Super User 2025 Season 2

#2
Gerardo Rentería García Profile Picture

Gerardo Rentería Ga... 43 Most Valuable Professional

#3
Daniyal Khaleel Profile Picture

Daniyal Khaleel 32 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans