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!
Related
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
I am using Dynamics CRM 2013 on premise.
I have built all the reports based on stored procedures in SSRS.
one report however, that has no issue with execution definitions, permissions or what ever,
once executed causes to browser to crash (any browser, i tried FF, Chrome, IE9 and up, )
it seems the problem is not a report execution problem but a report rendering problem for this specific report.
I cannot cache the report or make a snapshot of it, as the values of the reports also depends on the user running the report (among other parameters user-defined) and each user should get a different result. - i have more than 400 users.
I have tried searching for any one who had face this kind of issue and reported on it but failed. hence decided to post this question my self.
if anyone has any idea, please share.
thanks
Have you enabled tracing/logging in SSRS? http://msdn.microsoft.com/en-us/library/ms156500.aspx
You might turn on verbose logging while trying to run the report to see if you can get more helpful information.
If you write code, you can write a .NET application that calls the SSRS web services to render the report. Doing that will help you know for certain whether it's a browser rendering issue since you can get back the report as a byte array and save it to disk as Word, PDF, etc.
I'm just helping out while our regular SSRS guy is away and having an issue.
There is currently a very large report that's being generated. The subscription settings for this report is to ftp the report. The Subscription status for the report currently says "Processing delivery...". I assume this to mean that it finished generating and is now trying to send the file to the ftp location. I can see that the file is there in the ftp folder but the size is still 0kb. It has been saying "Processing delivery..." for a long time now.
My question is: Is there a location (folder or sql table) I can check to see if ssrs is actually doing something? I assume it would create temporary file somewhere locally first before sending it on its way.
Check the ExecutionLog views in the ReportServer DB of your SQL Instance. There are three views which show everything from the requested format to start time, complete times, and parameters used. Take a look at the time difference between start and complete for previous runs and compare it to the running time of the current report whose complete time will be null if it is still processing.
For bonus points: setup a SSRS report based on the view and set a subscription for daily email delivery. This saves a TON of time when troubleshooting reports where users can't tell you the parameters they use or the morning reports are empty, etc.
Also, funny as it sounds, you might want to check the free space on the server that the report is output to. With no free space the report will show processing delivery for a long time. If it's FTP and you don't have control of the FTP server, still might be worth the quick phone call.
I'm at wits end trying to find a solution for my issues with Internet Explorer and SSRS. I have created an C# Windows Forms program that uses the WebBrowser element to display SSRS reports to the end user.
Currently there are two report options for them to choose from. One report opens and displays fine. The data set for this report takes about 2-3 seconds to retrieve. The second report is either timing out or not rendering as I get a blank screen.
I think it is timing out as opposed to not rendering because I can't even choose the export to file option. The data set for the second report only takes about 15 seconds to retrieve. I have tried altering timeouts on web.config and rsreportserver.config on the SQL Server and I have tried putting a <system.web> section into the app.config file of the ASP project, but none of that seems to have fixed the issue.
I also tried changing the sessionState value in the web.config but that doesn't seem to have done anything either. Has anyone encountered this error that can tell me what steps to take to fix the problem? My local machine is using IE9 and the server is running SQL Server 2008 R2 on Windows 7.
The answer to this is above in the comments to my question. Don't use the WebBrowser control as it is prone to the failure of IE. I placed the ReportViewer control on there and it works correctly. Check http://technet.microsoft.com/en-us/library/aa337089(v=sql.100).aspx for usage of this control.
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.