This morning, SCOM alerted us that our Analysis Services database for our Test instance of SCSM is corrupted:

Summary 

Analysis Services cannot instantiate the key used in the Analysis Services database for encryption.

Causes 

There is data corruption in the Analysis Services database.

Properties for the Analysis Services service account have been changed outside of SQL Server Configuration Manager.

Resolutions 

Restore the Analysis Services database from backup

In SQL Server Configuration Manager, reset the service account properties

The database cryptographic key could not be loaded: \\?\I:\SSAS\DB\SMTSTDWASDataBase.0.db\0.CryptKey.bin

I recently restored a backup that I took (unfortunately I don't have that backup anymore because the restore happened over a week ago and I didn't have any errors until today.)

Any easy solutions to get this DB back online and operational?

Hi,

Sorry, after some tests and searching, I can't find a better way to solve this problem.

Otherwise, your question seems to be related to SQL. You may also choose to post there to get more effictive help.

https://social.technet.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlanalysisservices

I opened a case with Microsoft for this.  We ended up rebuilding the AS database using this document to fix the issue.

http://blogs.technet.com/b/thomase/archive/2014/11/24/how-to-rebuild-your-analysis-database.aspx

One thing to note was that after the rebuild, the cubes were still erroring when trying to process.  I solved this by re-entering the "Impersonation" account info for the DataSource.

I opened a case with Microsoft for this.  We ended up rebuilding the AS database using this document to fix the issue.

http://blogs.technet.com/b/thomase/archive/2014/11/24/how-to-rebuild-your-analysis-database.aspx

One thing to note was that after the rebuild, the cubes were still erroring when trying to process.  I solved this by re-entering the "Impersonation" account info for the DataSource.

• Marked as answer by Xin GuoMicrosoft contingent staff, Moderator 22 hours 25 minutes ago

I opened a case with Microsoft for this.  We ended up rebuilding the AS database using this document to fix the issue.

http://blogs.technet.com/b/thomase/archive/2014/11/24/how-to-rebuild-your-analysis-database.aspx

One thing to note was that after the rebuild, the cubes were still erroring when trying to process.  I solved this by re-entering the "Impersonation" account info for the DataSource.

• Marked as answer by Xin GuoMicrosoft contingent staff, Moderator Wednesday, September 09, 2015 8:47 AM

Hi,

Glad to hear that and thanks for your feedback.

Have a nice day.