February 18, 2010 at 11:38 am
We have SSRS and the database engine on the same box with the following configuration
Microsoft SQL Server Reporting Services Version 9.00.3042.00.
Microsoft Windows NT 5.2.3790 Service Pack 2
We are getting the following exception in the reportserverservice log file. All your help is appreciated.
ReportingServicesService!library!3!2/17/2010-03:40:19:: 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. ---> System.InvalidOperationException: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.ReportingServices.Library.ConnectionManager.OpenConnection()
--- End of inner exception stack trace ---
Thanks
Manoj
February 18, 2010 at 7:17 pm
Please check out these articles:
http://www.sqlservercentral.com/Forums/Topic673151-146-1.aspx
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 19, 2010 at 9:22 am
I found out that named pipes was disabled on the server and have enabled that and "remote connections for both TCP/IP and named pipes". Do you think this could be it? I am waiting for an outage to restart the server.
February 19, 2010 at 10:51 am
That could be a problem.
If you try to connect from a client to the Server with TCP/IP enabled that should tell you something...
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 19, 2010 at 11:07 am
Are the Databases on Default or named instanced?
Are you using Static or Dynamic IP Addresses?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 19, 2010 at 2:48 pm
No issues connecting from a client to the server with TCP/IP. The databases are on default instance. We are using Static IP.
February 19, 2010 at 3:04 pm
How did you configure SSRS using the Configuration Manager Tool (rscong.exe)?
What did you do when you used the rskeymgtmt.exe encryption tool?
What options did you select when you ran the rs.exe command-line utility?
What security roles did you define, etc?
What document or instructional guidlines did you use to configure your SSRS Environment?
Did you do this alone or did you work with someone or did you inherit this?
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 19, 2010 at 3:15 pm
All this was done prior to me joining the company and as far as I know the person who configured it used SSRS Configuration Manager to set up SSRS.
February 19, 2010 at 4:39 pm
Did it ever work?
If so when did it stop working?
You may want to start from scratch.
Respectfully, do you have any documentation on the setup, configuration & troubleshooting of an SSRS Installation?
Regards... 🙂
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
February 22, 2010 at 8:27 am
Upon probbing it doesn't look like it ever worked. I am now looking into documentation and as you said worst case scenario I will start from scratch.
February 23, 2010 at 8:44 am
Fixed the issue by setting the max pool size to 200 in the connection string. We are going to rebuild the server with upgrade and so it will be setup correctly. Thanks for all your help
November 3, 2011 at 10:36 am
Fixed the issue by setting the max pool size to 200 in the connection string. We are going to rebuild the server with upgrade and so it will be setup correctly. Thanks for all your help
Hi Manoj,
The Max pool size setting should be set from SSRS server? please advice..thanks
Viewing 12 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply