My question is about the following scenario:
In SSRS 2015 one report keeps refusing to render(hangs on a blank report) under specific circumstances.
Here is the scenario.
Open the report, which automatically renders (Functions perfectly)
Alter one parameter (it doesn't matter which one), render the report (Functions perfectly)
Alter a another parameter (It could be the same one or a different one), render the report. It hangs. There is no actual error shown, but the report just hangs with nothing displayed.
Specifically; The parameters are all greyed out and no report is rendered. The "View report" button is still visible and appears active, but nothing happens when you click on it.
The only way to make the report function again is to back completely out of it and re-enter the report from the beginning.
It is important to note that none of the sub-reports are effected. You can drill through to them as much as you like and nothing will hang.
Also, this functions perfectly on our 2012 server and that no other reports on either server have encountered this error.
I can't even replicate it in Visual Studio.
Has anyone ever seen anything like this?
Any insight would be appreciated.
Related
I have a report that consists of two graphs, with two separate datasets. They are overlapped and displayed or hidden based on a parameter on the report.
When tested in Visual Studio the report displays and runs fine (although a warning about overlapping report items is thrown), but when deployed to to our production setting, the report fails and throws an error that the Query failed for the Dataset that is hidden.
For example, datasets are WOs and WOsByAsset. When WOs is selected for display the error is Query Execution Failed for dataset WOsByAsset. When WOsByAsset is selected for display the error is Query Execution Failed for dataset WOs.
I have confirmed that both datasets work in SSMS, no actual errors are presented.
Could the fact that the graphs are overlapping cause this issue? The pattern of the errors appears to indicate that but I'd like any confirmation, or better yet, explanation that anyone may be able to give.
Thanks all for the suggestions.
Problem was of my own making. I had not taken into account that the report runs for each dataset even when the datasets related table was hidden. The report used a multivalue parameter, and by default passed all possible choices within the parameter into the report.
This was causing that dataset to fail, but when I tested the query in ssms I was only passing a single value for which the query ran just fine.
All good here.
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 have used a Guage as a clock. It is set to auto-refresh for every 3 sec.
It is running properly, but whole report is refreshing, reloading. So cant get a feel of a clock.
So I tried to use this (Clock) report as a sub-report in another report (say main report) which is not set to auto-refresh.
I am not getting why my sub-report is not auto-refreshed in main report.
Ideas & Hints are welcome!
I've never used the auto-refresh property of a report but I would guess that since it is a report-level property what you're expecting to happen won't work. In order for only the subreport part of the report to refresh it would effectively need to be a frame or iframe (using HTML as a reference). SSRS does not render this way and so your subreport isn't going to autorefresh. It renders the subreport and shows it in the subreport control and moves on.
I'm not really sure how you could have a dynamically updating element in a report using the standard controls. It would need javascript or some kind of other client-side scripting language that gets processed in order to keep functioning and even then it would only work when rendered to HTML.
Basically I don't think this is possible without a third party add-on, and I don't know of one that allows dynamic refreshing of individual report elements without refreshing the whole report.
If you can program in .NET you could write your own custom control for SSRS. This is effectively a third party addon you would create yourself. You could create a clock control and even give it properties to make it customizable. If you're going to use it in reports that you deploy to a report server you'll need enough access to that server to deploy the control assembly to the necessary location. See these MSDN pages for more info:
Creating a Custom Report Item
Jazz Up Your Data Using Custom Report Items In SQL Server Reporting Services
I have an issue with a report causing an "Object reference not set to an instance of an object" exception when run through my web application. This is, so far, only happening on one QA machine.
I can:
Run the report locally on my development machine (latest code, same database)
Run the report through the Reporting Services Web Interface on the QA machine
Run the report on the QA machine through my web app if I select a format other than PDF/TIFF (e.g. Excel, CSV, HTML, XML all report successfully)
The Reporting Services log on the QA machine looks like this when I get the exception.
I did not find the log helpful so I started whittling the report down to a minimum to find the issue.
What I found confuses me.
Given the following RDL; I can change the height of Tablix list1 from 3.09444in to 1in, deploy the report to the QA server and the report will run successfully.
How in the world could shortening the height of Tablix list1 prevent the exception?
UPDATE
It's not moving height of the tablix to 1in. It's getting rid of the long decimal on the height. I changed (3.09444in to 3.1in) and the report ran successfully. FTR, I did not choose the height 3.09444in...rs chose that for me while I designed the report.
Fixed by changing the long decimal on the height of a Tablix from 3.09444in to 3.1in.
I did not choose the height 3.09444in.
The Reporting Services designer chose that for me while I designed the report.
I've experienced this problem a few times. It typically happens to me when I have a hidden textbox executing some Code.xxx routine and that textbox is located under a table, and the table has some kind of group page break.
It seems that with each page break, the fields hidden under the table are refreshed and sometimes they get a object reference error.
Here's the weird thing - I can typically fix the problem simply by moving all the hidden fields to a location such that their upper left corner is above the table's upper left corner, or to the left of it. It's like the position of the field somehow has some influence on what is refreshed and what is not.
I do not claim to know why it works, it just does.
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