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.
Related
When accessing deployed SSRS reports via URL link using AD authenticated username/password, reports do not complete their rendering. The parameter bar displays with appropriate values and the Loading wheel displays until an error is thrown.
About 75% of the time the error shown is:
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error
has occurred while processing the request on the server. The status
code returned from the server was: 500
The rest of the time the status code returned is: 0
As an added curveball, when connected to internal Wifi the reports render accurately and quickly in Safari on Apple devices.
Reports render correctly in IE, Firefox and Chrome. Using Chrome on any Apple device has been shown to work in all tests so far. Unfortunately using any other browser than Safari is not possible in production.
Additional information
Server does receive a successful login in Event Viewer but nothing gets to the Reporting Services ExecutionLog stored procedures.
The rendering times out at around 120 seconds. A timeout issue could be involved but I can not currently find the appropriate setting to change and even if this is the fault, waiting over 2 minutes to reports this small is inappropriate.
Environment
SQL Server Reporting Services 2014
Accessing data from SQL Server 2000
Issue occurs in Safari browser on Mac, iPhone, iPad for iOS 9.1 and 9.2 (other OSs not tested)
When working reports show a variety of data from multiple databases on a single SQL server. They access several stored procedures to display parameter dropdowns and general report data organised in tables and graphs with images
Resolves trialled (and failed :)
Creating non database linked report with picture and one line of text (still did not render)
Changing ReportingServices and ReportManager web config file to increase httpRuntime executionTimeout and maxRequestLength values (still did not render)
Changing to Basic authentication (stopped any connection to any aspect of report manager etc)
Changes to javascript file (still did not render)
I have scanned the internet and of course here on Stack Overflow to little avail. I may have missed something or interpreted it incorrectly so any assistance, suggestions and help would be most appreciated.
Safari and Chrome render differently than Internet Explorer.
SSRS reports use the DIV tag with overflow: auto that renders the report invisible in Safari and Chrome.
See this for more info on how to deal with the issue:
SSRS 2008 R2 - SSRS 2012 - ReportViewer: Reports in Safari/Chrome but works fine in Firefox/Internet Explorer 8... why?
I had some SSRS report timeout issues earlier too (tried a few things in your suggestions too and didn't work). I discovered the rendering process would fail when report result set is too big. I ended up adding some page break to the report so report can be browsed by page to fix the issue. Hope this help.
I have a report in Microsoft Access 97 (yes, I know) that works properly on my client's copy of Server 2003. However, when I try to run it on my own copy of Server 2003, the report crashes Access immediately. It does the same in Server 2008 R2 and Server 2012 R2. Now, the interesting thing is that the query underneath that report runs perfectly, which I would think rules out things like MDAC. There's nothing unusual about the report -- no strange fonts or graphics -- at least nothing obvious. If I can get it working in an environment identical to the client's, then I can move it forward to other operating systems. Where should I start looking for the cause?
Usually this kind of crash is related to missing references..You need to go to the VBA Editor (ALT + F11) -> Tools -> References and check if you have any MISSING
Import everything from your current project into a new blank project, seems like that is the only resolution I have been able to find online.
The information that I found can be viewed here: http://www.pcreview.co.uk/threads/access-97-crashes-opening-a-report.3901588/
What worked for me, don't ask me why:
I found the printing worked and so did Layout View
Open the report in Layout View
Save the report
It works!
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 am trying to print a report that contains a bar graph using the report viewer, but running into an error. My reporting server is running SQL Server 2005 Reporting Services SP3 on Windows Server 2003 SP2.
Here are some steps that will reproduce the problem (at least for me)...
On a clean machine, I open up the
report, and it displays fine.
I then click the print button, and I
am prompted to install the
RSClientPrint ActiveX control. The
control downloads and installs fine.
I then click the print button again,
and the print dialog appears.
I select a printer, and click "OK".
A message box appears that has the
following text (including the
spelling error)...
An error occured during printing.
(0x80004005)
Any other report I try to print works fine. The only difference between this report and the other ones is that it contains a bar graph. If I remove the graph from the report, redeploy it, and then re-run it, it prints without getting that error.
As far as I know, it is not isolated to a specific machine. It happens to every customer I have talked to, and a variety of machines here in the office.
Has anyone seen anything like this? I have seen similar posts on the web suggesting to uninstall video drivers on the reporting server (thinking the GDI dlls have become corrupt ), install service packs, etc. I have tried every suggestion, but haven't found a good solution yet.
Thanks.
I ended up having to use a paid Microsoft incident on this, but it is resolved now. The issue was that I had a matrix in my report that had dynamic columns. Depending on exactly which date range you picked, the report could have n number of columns. In my case, when a date range was chosen that produced three or more of these dynamic columns, it would cause the matrix to become too large and run outside of the margins of the report.
The report would run and display fine with the matrix being too large, but the incredibly non-descriptive error would display whenever the report was printed or exported.
I resolved the issue by reducing the size of other columns and the overall font size in the report. This prevents the matrix from running off the page in the case of date ranges that produce three dynamic columns. It doesn't solve it in the general case (four or more columns will make it fail), but is good enough for my current purposes.
Microsoft didn't have a fix for the general case (such as a way to make the matrix fixed width).
I figured I should answer this in case anyone else runs across it.
-David
I've been following this tutorial (lesson 6) in order to build and deploy a sample report with an embedded subreport which reads its parameters' values from the parent report. This subreport is embedded in one of the group rows of the report's table, and both share the same datasource. Additionally, detail rows appear collapsed until the user presses the (+) button for each group of data in the table.
The report works great when I preview it at the Business Intelligence Development Studio (by the way, SQL 2005 Express edition) but when I deploy it and try to see in the Report Manager, the subreport is not shown. And, if I press the (+) button, the following message appears:
Some parameters or credentials have not been specified
Does anybody has the slightest idea of what I am doing wrong? Why does it works perfectly in the Report Viewer embedded in Visual Studio but not in the Report Manager web app?
Thanks in advance.
Does the subreport use the same Data Source as the parent report? If not, be sure to check the data source of the subreport to make sure it is correct. Check in Report Manager, not your local copy.
I'm beginning to think this could be an issue with the browser. I'm currently using Internet Explorer 8 Beta and I'm also experiencing weird behavior from the Report Manager. I've tried with Google Chrome and Firefox 3 and, although the navigation is not as smooth as I like, the problem seems fixed.
it happens when you use IE8 as a report browser. I faced same issue and when I tested on chrome it worked fine .
This may or may not be related, but I had a similar problem some time ago (except that in my case the reports were accessed through a custom web page) and it turned out we had an older version of the report viewer control (the version that came with Sql 2005 RTM). After upgrading to the latest version the issue went away.