August 15, 2017 at 9:39 am
Hello experts,
We recently upgraded one of our database servers from SQL 2012 Enterprise Edition to SQL 2016 Enterprise Edition.
We also have a SQL 2012 Standard Edition SSRS report server that has started to throw the following error intermittently when the clients try to run reports.
processing!ReportServer_0-52!4d0!08/15/2017-10:42:22:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: , Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'ReportData'. ---> System.InvalidOperationException: ExecuteReader requires an open and available Connection. The connection's current state is closed.
I tried searching for a resolution online, but most of the discussions are about coding connections (such as if (_conn.State == ConnectionState.Closed)
_conn.Open();").
I don't think that coding advice is relevant for errors appearing sporadically in an SSRS report rendering situation. But I also don't know if that is relevant.
Have other people seen this issue? Can you recommend anything to troubleshoot and fix?
If any other info is needed, just let me know.
Thanks for any help.
- webrunner
-------------------
A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html
August 15, 2017 at 10:48 am
I think it's most likely related to this part of the error quoted above.
I would start by checking the data source for ReportData dataset - check the permissions, check the result set, run the query manually in SSMS, etc.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply