Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Error in Reporting Services - Event Error 107:"Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database." Expand / Collapse
Author
Message
Posted Friday, January 4, 2013 5:46 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
Hi,
We are getting error - "Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database." while retrieving the data from the particular database. Can anyone tell us why this problem arise ?

Regards,
Ram
Post #1402826
Posted Friday, January 4, 2013 6:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:51 AM
Points: 5,142, Visits: 4,937
Has anything changed recently?

Report server migration
Database server migration
Encryption keys been restored

Can you run through the SSRS config tool to ensure it is set up as it should be?




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1402833
Posted Friday, January 4, 2013 6:44 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
We first cleaned up the transaction logs - 20 days back and restored the encryption keys recently - 2 days before.
Regards,
Ram
Post #1402851
Posted Friday, January 4, 2013 7:48 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 5:51 AM
Points: 5,142, Visits: 4,937
Restoring the encryption keys will have probably caused it as the keys are out of sync.

Two ways to go it, find the correct encryption key file or delete all encrypted content and then resetup all your data sources and subscriptions.




Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1402884
Posted Friday, January 4, 2013 9:16 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, July 23, 2014 10:49 PM
Points: 90, Visits: 388
Thanks for your help! Is there any other cause for this problem?
Post #1402951
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse