Home Dashboard Directory Help
Search

The report server cannot decrypt the symmetric key by Teo Lachev


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


13
0
Sign in
to vote
Type: Bug
ID: 322557
Opened: 1/16/2008 6:13:36 AM
Access Restriction: Public
0
Workaround(s)
view
12
User(s) can reproduce this bug

Description

Reporting Services has the propensity of losing the encryption key and returning
"The report server cannot decrypt the symmetric key used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. Check the documentation for more information. (rsReportServerDisabled) Get Online Help Bad Data. (Exception from HRESULT: 0x80090005)"

Details
Sign in to post a comment.
Posted by VenkatKokulla on 7/19/2011 at 12:05 AM
Hello,



Do you happen to have a backup of your encryption key? If not, follow these steps:



Open Reporting Services Configuration Manager

Connect to your RS server

Select 'Encryption Keys' from the left pane

Press the 'Delete' button to get rid of your encrypted content



After doing this, you will need to re-set the connection strings and stored credentials on your reports.



Also, I'd be sure to make a backup of the encryption key afterwards.



If you do have a backup, press the 'Restore' button instead of the 'Delete' button.



Hope this helps.

Venkat
Posted by lukek on 11/10/2010 at 7:32 AM
happens regulalry for me too - the server isnt used much - reapplying the key (even after regenerating it) fixes it for a while

crypto!ReportServer_0-17!f74!11/10/2010-15:27:03:: i INFO: Importing existing encryption key
library!ReportServer_0-17!f74!11/10/2010-15:27:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException (0x80090005): Bad Data. (Exception from HRESULT: 0x80090005)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ImportSymmetricKey(Byte[] symKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---
library!ReportServer_0-17!f74!11/10/2010-15:27:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException (0x80090005): Bad Data. (Exception from HRESULT: 0x80090005)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ImportSymmetricKey(Byte[] symKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass1.<Run>b__0(Object state)
at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state)
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody callback)
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
--- End of inner exception stack trace ---
runningjobs!ReportServer_0-17!f74!11/10/2010-15:27:03:: e ERROR: Error in timer Running Requests DB : Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. ---> System.Runtime.InteropServices.COMException (0x80090005): Bad Data. (Exception from HRESULT: 0x80090005)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at RSManagedCrypto.RSCrypto.ImportSymmetricKey(Byte[] symKeyBlob)
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Library.ConnectionManager.<GetEncryptionKey>b__2()
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.<>c__DisplayClass1.<Run>b__0(Object state)
at System.Security.SecurityContext.Run(SecurityContext securityContext, ContextCallback callback, Object state)
at Microsoft.ReportingServices.Diagnostics.RevertImpersonationContext.Run(ContextBody callback)
at Microsoft.ReportingServices.Library.ConnectionManager.ConnectStorage()
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
--- End of inner exception stack trace ---
at Microsoft.ReportingServices.Library.RunningJobsDb.GetMyRunningJobs()
at Microsoft.ReportingServices.Library.RunningJobDbTimer.DoTimerAction()
at Microsoft.ReportingServices.Diagnostics.TimerActionBase.TimerAction(Object unused)
Posted by emu78 on 5/27/2010 at 7:44 AM
Same problem (SQL Server 2005)! Problem seems to be caused by a simple restart of the machine...
Incredible there's no hotfix for that...

I can provide log file if necessary....
Posted by William Lowers on 2/9/2010 at 6:04 AM
I installed SSRS 2008 SP1 and have this issue. I have changed the service account but cannot change it back cause it tells me I need to backup the encryption key. The kicker here is it tells me that I cannot back it up and to delete all encrypted data and try again. My server is a fresh install so there is NO DATA on the server at all.

This is very frustrating... also the link provided by Microsoft is for SSRS 2000 which I had looked into but does not seem to pertain to SSRS 2008 so I do not consider it a valid solution at all.

PLEASE FIX THIS
Posted by Ivan.Z. _ on 9/15/2009 at 2:05 AM
I have the same issue on SQL 2008 and have also never changed the user account (it runs under NT AUTHORITY/NETWORK SERVICE). It seems that this happens after machine restart (it is development machine under Win XP).

I could attach the logs, but i don't see where.
Posted by vinod kushwaha on 3/12/2009 at 11:50 AM
I had installed SQL Server 2008 as Network Service Account but Now I have changed it to LocalSystem Account. I am having this problem. How can I eliminate this problem?
Posted by billpesi on 3/5/2009 at 8:05 AM
I can also tell you that on 2 seperate instance of RS2005 that this is happening and the account associated with RS has NOT changed.
Posted by Edward Forgacs on 11/13/2008 at 4:29 AM
Well, I have never *EVER* changed the account Reporting Services runs under, and I have had this bug probably 10 times, starting with the original version of RS (SQL 2000). It does definately seem that if you don't use RS for a while (which sometimes happens with my local development copy), it blows up when you try to start it.

The frequency of this bug seems to have definately got worse with SQL 2008 as this is the third time I have fixed it since installing 2008.
Posted by Seba8282 on 9/10/2008 at 11:06 AM
This issue happens because the service start up account has changed, the following article must solve the issue:

http://support.microsoft.com/kb/842421

But the logs requested must be sent for further analysis.
Posted by Teo Lachev on 2/22/2008 at 4:34 AM
Lukasz,

I'll keep an eye on this issue with CTP6 and re-open it if I can repro. Thank you.
Posted by Microsoft on 2/21/2008 at 8:02 PM
Thank you for filing this bug. Since we did not receive any log files in connection with this issue, we do not have sufficient information to investigate further.

Thanks,
-Lukasz
Posted by Microsoft on 1/22/2008 at 9:27 AM
Thank you for filing this issue. To help us diagnose, please attach the report server log files to the connect item.

Thanks!
Sign in to post a workaround.