I'm having issues with one of my reports timing out when certain parameters are passed to it. This seems to happen when the execution of the stored procedure (that builds the dataset for the report) runs over 2 mins.
I have ran the query within SSMS and the query runs and finishes in 2 mins 5 seconds.
I have read up on numerous ways on trying to increase this time out value:
Updating the report on the web portal to run indefinitely.
Updating the remote query timeout for the db instance (set to 600s)
Updating DatabaseQueryTimeout in rsreportserver.config (set to 360s)
Updated Httpruntime, executionTimeout property in web.config (set to 9000s)
Moving back through the chain I have found that the issue persists when running the report directly from the SSRS web portal.
When you inspect the console on the site, I get the following:
Funnily enough if i hit view report again after hitting this error the report is correctly generated. guessing this is because the query data was cached?
Was wondering if anyone has experienced this and would be able to give me guidance on a setting / configuration which would stop the timeout.
The version of SSRS is 2016
Related
I am having a strange issue with SSRS 2016. We setup a new server and uploaded some reports, the reports ran fine for few days. The issue is, randomly the report doesnt run, When I load the report page, the parameters appear blank and I am unable to select any parameters. If I try to run and click the view reports button, nothing happens. After few mins/hours, it automatically resolves.
We have contacted MS support and could not get anything to get this resolved
Has Anybody faced a similar issue ?
This does not constitute an answer but it won't fit in a comment!
Does this affect more than one report?
If more than one, do they all fail at the same time or will one work and another not when you try to run the at the same time?
If the situation is "all fail" or "all work" at any single point in time then try adding a new report with no parameters.
If this attempts to run when other reports fail then it sounds like the datasource cannot be resolved or a timeout connecting to the database.
If your parameters are populated by querying the database the report will 'hang' until it can complete the queries to populate the parameters so by running a parameter-less report you should see an error instead.
Try running a trace on the database server to see if you can see the queries being run at all.
A bit vague I know but it might help you understand where the problem lies a little better.
I am having a problem with some CRM Reports as they are not being rendered with the error
Microsoft.Crm.Reporting.DataExtensionShim.Common.ReportExecutionException: The fetch data set query timed out after 307.9435095 seconds. Increase the query timeout, and try again.
I dont know where to change that limit , but I changed the following limits in both CRM Application servers.
OLEDBTimeout , ExtendedTimeout , NormalTimeout
Do not time out ( through ReportManager for the whole report manager and for the report itself)
executed SessionTimeout.rss script against the report manager
executiontime and maxrequestlength in web.config for CRM website
But I am still getting the error as I cant optimize the query , the report is huge and takes 5 minutes of processing but it keeps showing an error after exactly 319 seconds.
This problem applies to CRM out of the box reports and also for reports developed in BIDS
Reports works fine if the data is not huge.
Joe CRM at Power Objects has a little guide that might help.
Hope that helps.
I have some users intermittently receiving this error 'Unable to read data from the transport connection—The connection was closed' when viewing an ssrs report through the ReportViewer control.
The user can access the SSRS via web browser and not replicate the error
On multiple pages reports the first page loads and where it states 'Page 1 of totalPages' this totalPages counts up as the rest of the pages are loaded. Half the time it doesn't display an error but not all pages are loaded.
We are running SSRS express within a windows application.
SQL Express installation is a named instance
When it happens the screen hangs for around 2 minutes
It occurs on a couple of reports but not others different reports. It's not data amount related, sometimes 50 page reports come through OK and sometimes 2 page reports fail.
If it fails the user can run the report again and it usually works the next time. Sometimes it takes 3-4 goes.
Nothing has changed recently, I'm told this was always the case but they never reported it.
I tried giving the single shared ssrs datasource sa user credentials - no change
Some reports appear to load OK everytime while others error out or only load a couple of pages.
What I have tried so far:
I cannot replicate this error from our remote client, I just ran 20 successful reports no dramas from within another client installed on the same network. But I can replicate it from the users computer with both my account and their account.
I cannot see anything relevant in 'C:\Program Files\Microsoft SQL Server\MSRS10_50.MyInstance\Reporting Services\LogFiles'.
Thanks in advance for tips on where to look for clues and ways to resolve this issue..
I have resolved this by removing the ReportViewer UI control and we are now creating a pdf of the report using ReportViewer.ServerReport.Render() and opening with Process.Start(). The client only wants a pdf or a print out so we don't need the report viewer as such.
I'm not sure why the connection was closed at times, maybe it's network related as I couldn't replicate on a machine located physically next to the server. Either way this is resolved, onto the next project!
I created an annonymous SSRS web wrapper that had been working without error for several months. Recently we've had our year end release and the production version has had problems with, to my knowledge, one report. The Dev and Test environment produce the report without error it's just production where it has been failing. We've began to trouble shoot the problem with the following results:
The execution time for the stored procedure can at times be in seconds and other times in excess of 20 minutes.
The above is also true for rendering the report using report manager.
Once you get to the SSRS wrapper it completely fails. Even so considering there is a fluctuation in the amount of time the stored procedure executes it seems to me that even if I set the wrapper to not have a timeout the stored procedure may still be the culprit.
As for the report server, I'm not the DBA so I'm not familiar with the rs.config files. Also, I read something about the settings being set a certain way using IIS 6. According to the DBA it does not run off of IIS 6. Again, this is something I'm not familiar with.
Another thing I have a question about is parameter sniffing. There are three parameters being sent in, one for the City set as Text in RB 3.0 and Varchar in SQL, the month and year both set as int in RB 3.0 as well as integer in sql.
I know for a fact that the first time this error came about the server was reset and the report was produced without error. Since then they have been able to stabilize the server but now the report does not render. Anyone with trouble shooting advice please come to the rescue.
I have a negative one. Sorry about the bad question. Anyway, the problem was the stored procedure. The DBA told me he had to reset the statistics.
Our company has a huge nasty report that takes about 50-60 minutes to run (it's for a university and lists all sorts of payment information for all students registered in courses). While it has been running each morning at 5am as a subscription, it recently stopped working and displays "An error has occurred during report processing." in the properties window for the subscription.
If I manually run the report from inside Visual Studio it will work every time, but the subscription will now always fail. I had our DBA turn on trace logging and it gave us no helpful information whatsoever. I've also set the subscription to run at different times throughout the day, with no success. The report is supposed to put an Excel file on a file share and it works for the other 5 subscriptions to this report (I have 6 subscriptions, only 1 of the 6 has a parameter set that returns values from a larger dataset). So this means that it has permission to write to the file share. Any ideas?
Could it be trying to write more than 65536 rows to the Excel file? If so it will just fail.
Also you might check the configuration for IIS to see if the report is causing a timeout.