The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable ) Get Online Help Timeout expired. The timeout period elapsed prior to o

Hi,

The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable) Get Online Help 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.

How to resolve this?

Thanks,

Manasa

May 26th, 2015 3:03am

We need more information to help you trouble-shoot this so which environment are you referring to ? Is it SQL Server 2008/ 2008 R2/ 2012.

On a side note: One of the reason for this is when you use data driven subscription and all of them are running almost in parallel therefore we need to know whether it for scheduled subscriptions or you are getting this error while running interactively as well

Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 3:16am

Hi Kappor,

we are using Sql server 2008 R2. When we try to access the report we are getting this error.

we are using oracle as shared data source.

Thanks,

Manasa.

May 26th, 2015 3:57am

Can you give more information as in volume of records you are pulling from this data source
Free Windows Admin Tool Kit Click here and download it now
May 26th, 2015 4:13am

Can you try disabling the Pooling by right clicking the shared data source --> Advanced --> Set Pooling to False. You will have to re-deploy the data source and reports to see the effect. As far as I am aware, you need to also set true for overwrite data source in the solution properties to deploy the DS again

Refer this screen-capture for disabling the Pooling:

May 26th, 2015 4:21am

Hi Manasa,

Base on my research that the error can be caused by the when open connections without closing them and when the pool reaches maximum connections, it will throw the specified error. Make sure you are not opening connection inside loop, if you open connection make sure you are closing it immedietly after you execute the query.

As you mentioned that you are using the Oracle as the datasource, please check below details information:

  1. That you are using Oracle ODP.NET provider (version 102 or higher) and not Microsoft provider for oracle. This bug solved just in ODP.NET.
  2. Ensure that you close all your open connections by closing or disposing OracleConnection.
  3. Pay attention to those two connection string options:"Decr pool size" and "Incr pool size". "Decr pool size" set the Number of connections that are closed when an excessive amount of established connections are unused. "Decr pool size" default value is 1. "Incr pool size" set the Number of connections established when all connections in pool are used. "Incr pool size" default value is 5. As you could see those default values can cause the pool to reach it maximum connection pool size default value (Ddfault -100). You can also try to increased max pool size from 100 to bigger value to have a check.
  4. As Manu mentioned that please also try to set Pooling to False.


Similar threads for your reference:
Timeout expired.The timeout period elapsed prior to obtaining a connection from the pool
Connection Pooling and the "Timeout expired" exception FAQ
Connection pooling and Oracle.

If you still have any problem, please feel free to ask.

Regards,
Vic

Free Windows Admin Tool Kit Click here and download it now
May 27th, 2015 2:12am

The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable).

This error occurs when the report server cannot connect to the SQL Server relational database that provides internal storage to the server. The connection to the report server database is managed through the Reporting Services Configuration tool. You can run the tool, go to the Database Setup page, and correct the connection information. Using the tool to update connection information is a best practice; the tool ensures that dependent settings are updated and that services are restarted. For more information, see Configuring a Report Server Database Connection and Configuring the Report Server Service Account.

This error can also occur if the Database Engine instance that hosts the report server database is not configured for remote connections. Remote connection is enabled by default in some editions of SQL Server. To verify whether it is enabled on the SQL Server Database Engine instance you are using, run the SQL Server Configuration Manager tool. You must enable both TCP/IP and named pipes. A report server uses both protocols. For instructions on how to enable remote connections, see the section "How to Configure Remote Connections to the Report Server Database" in How to: Configure a Report Server for Remote Administration.

If the error includes the following additional text, the password expired on the account used to run the Database Engine instance: "An error has occurred while establishing a connection to the server. When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not permit remote connections. (provider: SQL Server Network Interfaces, error: 26 - Error Locating Server/Instance Specified)." To resolve this error, reset the password.

May 27th, 2015 3:24am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics