Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2023 Release Wave 1Check out the latest updates and new features of Dynamics 365 released from April 2023 through September 2023
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | All TechTalks
Has an issue with the SQL server where we pretty much had to rebuild it, All database were able to get re-attached and all applications are working, except MR. The issue we are having now is with Management Reporter. When trying to re-connect the existing database in the configuration console I am receiving the following error:
"Please create a master key in the database or open the master key in the session before performing this operation. The "DecryptData" procedure attempted to return a status of NULL this is not allowed. A status of 0 will be returned instead. Originating procedure, DecryptData.
Saw this https://support.microsoft.com/en-us/help/2744330/error-messages-when-you-restore-a-microsoft-management-reporter-2012-d but without the building blocks I cannot proceed.
I do now know the key for this and do not have the building blocks.
Any help would be appreciated./
You refer to no. 8 in the website that you shared, right?
The building blocks contain the rows, columns, reporting trees and report setups that you have made in the past.
If you have not designed any new report then there might be nothing available there and you don't have to worry about this step.
Is there no sql back up of MR you can restore, and then refresh the data? or recover the password?
MR should have its own SQl instance because its configuration is different.
When you move the database to another server, you lose the ability to automatically decrypt and open the database master key because the local server key will most likely be different. If you can't decrypt the database master key, then you can't decrypt anything else that depends on it (certificates, symmetric keys, etc).
The problem occurs for example when restoring an MR database.
It can also occur when the Management Reporter database is in an availability group Always On (Availability group) when you switch the Management Reporter database to the secondary server, it will not be able to decrypt the data of the database. Consequently, the DataMart database disappears from the console and the following error message appears in the event log:
For MR :
The problem is that the Service Key (SMK) of the second SQL server is not able to decrypt the Database Master Key (DMK) located in a database Management Reporter since it was encrypted with the Key Service the primary server. Because SQL is not able to open the DMK, it therefore cannot open the certificate, etc .
There links may help"
I recommend to add a new password on the production system using ALTER MASTER KEY (msdn2.microsoft.com/.../ms186937.aspx) in case the original password is truly lost.
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'SQLAuthority' ALTER MASTER KEY ADD ENCRYPTION BY SERVICE MASTER KEY
The REGENERATE option should be used only when you want to have a new master key in the database
ALTER MASTER KEY DROP ENCRYPTION BY SERVICE MASTER KEY.
When SQL requires a Database Master Key (DMK) to encrypt or decrypt a key, SQL tries to decrypt the DMK from the Service Master Key (SMK). If this fails,then SQL checks whether the password to open the DMK is in sys.master_key_passwords.
Add the password to the DMK ManagementReporter catalog sys.master_key_passwords for all servers in the group.
EXEC sp_control_dbmasterkey_password @db_name = N'ManagementReporter ' ,
@password = xxxxxxxxx ' , @action = Do not add' ;
The RESTORE MASTER KEY with FORCE option to replace the DBMK - needs care - make sure you have backed up any important data you have modified. The service master key is the root of the SQL Server encryption hierarchy. The service master key directly or indirectly secures all other keys in the tree. If a dependent key cannot be decrypted during a forced restore, data that is secured by that key will be lost.
Business Applications communities