Hi,
I'm running SQL Server 2008 R2 with reporting service. I have multiples reports that run on it sharing the same connection via a "Shared datasource". Connection pooling is also active.
If for some reason I need to put MyUserDB (used by the report) in maintenance (setting it to Restricted User temporary), when the DB come back availlable, the first time I try to access the report results in this error:
"Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'PrintJob'. ---> System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed."
The reused connection that was in the pool is no longer availlable due to the service interruption (obviously killed). The second time I try to run the report everything works fine.
Work around: Turning off connection pooling (pooling = false in the connection string) resolve this issue but slow down the report.
Question : Why connection pooling is not more robust? I expect that if a connection is invalidate, drop it from the pool and try the next one. If all connections are invalidate, try creating a new one in a last resort, if still not able to return a valid connection, raising an error will then be the solution.
Is there a way to force a number of retry in the connection attempt?
thanks for your answer