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

Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database. Expand / Collapse
Author
Message
Posted Monday, May 18, 2009 11:21 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 17, 2010 11:02 AM
Points: 347, Visits: 777
Hi ,

Iam getting the below error daily once at different timings.How can I diagnose the cause of this error?

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 5/16/2009
Time: 11:53:21 PM
User: N/A
Computer: ABC
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.

Post #719286
Posted Monday, May 18, 2009 11:25 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, April 13, 2014 12:23 PM
Points: 3,433, Visits: 14,411
Are you running SSRS and the relational engine in separate boxes? What account is used to run SSRS and Asp.net because SSRS 2005 is Asp.net dependent.

Kind regards,
Gift Peddie
Post #719289
Posted Monday, May 18, 2009 11:36 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 17, 2010 11:02 AM
Points: 347, Visits: 777
Both the database engine and reporting services are running on the same box.

Database engine and Sql Server Reporting Services are running under Local system
Where can I check Under which account ASP.net is running?I checked the web service identity in reporting services configuration, inthat it shows ASP.net is running under NT Authority\Network service

1. Default website->properties ASP.net version 1.1.4322
2.Reports->properties ASP.net version 2.0.50727
3..Reportserver->properties ASP.net version 2.0.50727
Post #719296
Posted Monday, May 18, 2009 12:13 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, April 13, 2014 12:23 PM
Points: 3,433, Visits: 14,411
Both the database engine and reporting services are running on the same box.

Database engine and Sql Server Reporting Services are running under Local system


You need to run SSRS on Network service account because the local systems account does not have access to network resources. Go to configuration manager and right click go to properties and you can change the account there.

Where can I check Under which account ASP.net is running?


Right click go to properties on the default website site then directory security.

1. Default website->properties ASP.net version 1.1.4322


This could be a problem because SSRS require .NET 2.0 as the default. This is not good because SSRS 2005 expect your IIS to be running .NET 2.0 so you need to change the default website to .NET 2.0 and then add the code below which is an application Start element to your default website Asp.net Web.Config file. I have also added the relevant link so you could understand supportedruntime definition in all .NET applications.

 <Start> element

<supportedRuntime version="1.1.4322" />

http://msdn.microsoft.com/en-us/library/w4atty68.aspx

2.Reports->properties ASP.net version 2.0.50727
3..Reportserver->properties ASP.net version 2.0.50727


Go to the location below and run the utility aspnet_regiis after you have made all the changes please run tests in a sandbox before applying to production.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727


Kind regards,
Gift Peddie
Post #719319
Posted Monday, May 18, 2009 1:10 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, December 30, 2009 5:10 PM
Points: 6, Visits: 10
You need to run SSRS on Network service account because the local systems account does not have access to network resources. Go to configuration manager and right click go to properties and you can change the account there


if this is the case, I should get the error all the time right? but Iam get only once in a day...

I recently upgraded reporting service 2000 to 2005. I did not change anything after the upgrade. The reports are running fine, so far I did not get any complaints. But in the event viewer, Iam seeing this error daily once.
Post #719354
Posted Monday, May 18, 2009 1:18 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, April 13, 2014 12:23 PM
Points: 3,433, Visits: 14,411
I still think if you have resources for a test box you need to make the changes I recommend, that is if you have the time before SSRS just stop working because your system is confused. You should think about it.

Kind regards,
Gift Peddie
Post #719359
Posted Friday, May 29, 2009 4:05 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 17, 2010 11:02 AM
Points: 347, Visits: 777

I changed the Default website->properties ASP.net version 1.1.4322 to 2.0.50727 and now Iam getting the same error by every 2 days or sometimes after 3 days

Event Type: Error
Event Source: Report Server Windows Service (MSSQLSERVER)
Event Category: Management
Event ID: 107
Date: 5/20/2009
Time: 10:23:18 PM
User: N/A
Computer: ABC
Description:
Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.But the error repeating???

But Ican browse the urls and able to view the reports

http://servername/reports, http://servername/reportserver
Post #726108
Posted Friday, May 29, 2009 4:18 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Sunday, April 13, 2014 12:23 PM
Points: 3,433, Visits: 14,411
Your error is documented with many possible solutions so check below and see if you any of the issues are relevant to you.

http://msdn.microsoft.com/en-us/library/aa337324(SQL.90).aspx



Kind regards,
Gift Peddie
Post #726111
Posted Tuesday, June 23, 2009 1:14 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, September 22, 2009 4:41 AM
Points: 49, Visits: 177
Hi;
I am getting a similar issue with my reporting server. The workaround we have found is going to the report manager and deleting the temp folder. This is only a temporary solution. Please let me know if you have been able to resolve your issue.
Regards
Shivam
Post #739942
Posted Monday, July 27, 2009 2:05 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, January 11, 2012 11:48 AM
Points: 1, Visits: 47
We've been having a similar problem today. We have multiple clients that connect to the same report server. The failure message reported to the user in the report viewer was the vague '..internal error occurred on the report server....etc'. However, it was very inconsistent. Some clients were working fine and some were not, then they would connect, then suddenly they could not. The Event Viewer on the reporting server reported the 'cannot connect to the report server database' error. We rebooted the report server and got temporarily relief but then the problem cropped up again.

Looking through the reporting services log files I found that one of the reports being run had logged a datasource error (ambiguous column). I have fixed the ambiguous column error and am hoping that the other issues magically disappear but am a little wary as it is strange that a datasource error would cause the report server to not be able to connect to the report server database.

Previously I'm almost certain that datasource errors (embarassing as it is) were displayed to the user in the report viewer window so I'm not sure why all we're getting now is the 'internal error occured'. Quite a bit less helpful!
Post #760342
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse