Cannot start Reporting Services Service under certain AD accounts
-
Hello. We have an AD account set up which we use to run our Reporting Services instance under. However, following a server reboot, we found that the Service would not start under that account.
The event viewer writes this error when I attempt to start the service using the Service Account
The SQL Server Reporting Services (MSSQLSERVER) service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
The last time this happened, we had to delete the encryption key, meaning we lost our stored credentials. So last time, I deleted the key, temorarily ran the RS Service under my AD account, and manually re-entered the passwords. Eventually, I was able to stop the service and run it under the Service Account credentials.
However, I'm now back to where I was. I can't run the service under the Service Account. I've attempted to delete the encryption key but I'm not convinced it's been deleted:
The Service is running under my AD account and I've had to re-enter lots of connection string details. However, the key difference here, is that I have a backup of the encryption key from last time this happened, and I'm thinking I must be able to restore it, but I don't understand the steps.
Can anyone help with this?
-
I haven't done this in quite awhile, but I will say it sounds like you are just covering over the root of the problem by this workaround.
Is there anything else in any of the logs that around the same time that would indicate an inability to communicate with the domain controller? How often does this happen? Does the password for the service account expire?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
Jack Corbett (9/11/2013)
I haven't done this in quite awhile, but I will say it sounds like you are just covering over the root of the problem by this workaround.Yes, I agree...This is not a permanent solution.
Jack Corbett (9/11/2013)
Is there anything else in any of the logs that around the same time that would indicate an inability to communicate with the domain controller? How often does this happen? Does the password for the service account expire?I've just found this in ReportServerService_09_06_2013_11_07_44.log
ERROR: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: 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. ---> System.Runtime.InteropServices.COMException (0x80090005): Bad Data. (Exception from HRESULT: 0x80090005)
What do you think? have you seen this before?
-
I've never seen this error. Wish I could offer more help.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question -
Robert Graff (9/11/2013)
Jack Corbett (9/11/2013)
I haven't done this in quite awhile, but I will say it sounds like you are just covering over the root of the problem by this workaround.Yes, I agree...This is not a permanent solution.
Jack Corbett (9/11/2013)
Is there anything else in any of the logs that around the same time that would indicate an inability to communicate with the domain controller? How often does this happen? Does the password for the service account expire?I've just found this in ReportServerService_09_06_2013_11_07_44.log
ERROR: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDisabledException: 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. ---> System.Runtime.InteropServices.COMException (0x80090005): Bad Data. (Exception from HRESULT: 0x80090005)
What do you think? have you seen this before?
Try to restore the symmetric key.
http://msdn.microsoft.com/en-us/library/ms157275(v=sql.90).aspx
--
SQLBuddy
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply