We help IT Professionals succeed at work.

Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database ERROR

taylor11
taylor11 asked
on
21,372 Views
Last Modified: 2012-08-13
I'm getting this error on one of my servers in the Event Log every day.

Event ID: 107
Source: Report Server Windows
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

We have a service that restarts via a scheduled task every day, and this error is know to be caused by a service starting or stopping. However, we do not have Reporting Services installed on this server.
How do I get this error to stop?
Comment
Watch Question

I'm having the exact same problem, don't know why and can't find any solutions, yet.

Commented:
Same problem too. But I do have MSSQL 2005 AND MSSQL EXPRESS 2005 installed on the same server. Still no explaination on this event id that show up every minute...
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Commented:
If none of that solves your problem.. Check the System Event log on the server, you may find that the application pool that the report server is running on is hitting it's maximum virtual memory usage and recycling the worker process.  That's what my issue was - we were getting the error when generating larger reports, small ones were fine - we just increased the maximum memory usage limit for recycling the worker process and it worked!

Commented:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

I'm getting the same error...

Commented:
It would be great to mention ther Event ID number as well as the Source. This will facilitate the understanding and the troubleshooting.
 
If you experiment the same problem, just post your question as a new topic. This thread is closed ! It will not attract many experts...
 
Good luck.
I was getting the same error too but found that by setting the SQL Server Reporting Services (MSSQLSERVER) service to "Automatic (Delayed Start)" instead of "Automatic" fixed this (were using W2K8R2 with SQL2K8SP2).

It seems the Reporting service was starting before the database was started.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.