I have a report which works without problems. I created a new version of that report with two levels of grouping, which works perfectly in Visual Studio. I deployed it to the server (in SharePoint integration mode). The report runs for a while (displaying the spinner) and then I get the error:
An error occurred during client rendering
So it appears to collate the data but chokes when trying to render it.
I can render the report from the server directly to PDF and Excel and that renders correctly. It is just when it tries to render in the browser that it doesn't render.
The Reporting Services log simply shows that it processed the report and doesn't have any errors.
Has anyone got any clues to what might cause this?
When rendering to HTML in Visual Studio (using the save button after rendering in VS) it gave me the following error message:
An error occurred during local report processing.
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
I found this post which suggested that it was to do with items in the header or footer being to big for the header or footer, and particularly mentions images. I have an image in the header. My image looked fine but was 0.00475cm in from the left margin when it should be flush left (and was flush left in the report that this report was copied from). I changed it to be positioned at 0,0 and the report now renders in HTML.
Its the little things...
When I get the error:
An error occurred during client rendering.
An error has occurred during report processing.
The data source 'XYZDataSource' cannot be found.
It always happens after I Deploy reports to the server from BIDS.
To resolve it, I close the Browser (page) and start a new Browser window, put in the URL and it works again.
I received this same error when I had a line at the bottom of a header which was somehow covered by the body.
I was getting this error when I had tables inside tables, and the inner tables had column visibility expressions. When every column's visibility expression resulted in a false value (causing them all to be hidden), then I would get this error. I added an extra super thin column in the row, and then it was fine.
Related
I developed a DB with MS Access 2013.
I want to printout one report which include 3 subreports (subrA, subrB, subrC) Sometimes #error appears in the PDF (on subrA). It is always on the same textbox.
What is weird is that I always display the report (as preview) and no error appears.
Then I launch PDF printing and sometimes (not always???) I get the error (after error happening in PDF, I sometimes have error in report preview).
My tests :
I tried to printout with PDFcreator and DoCmd.OutputTo, same issue happens
I tried to replace the subrA (expecting a corrupt report) but I still get the error.
I expand the textbox to be sure that it large enough according to the content,
If I print all the reports in one time, I never get this issue
It seems to be lack of refresh issue, as if Access do not have time (sometimes) to format the data in the subreport before printing.
Do you have any idea to support me or any idea of what happens ?
Thanks a lot.
Additional information (added the 2018/01/22)
All the data in SUBR_A come from a query. The data code in error is :
SomDom("QtyCalculeIngredient_UProd";"qryProduction_OFDetailsIngredients";"IdProduction=" & [IdProduction] & " AND Ordre<=" & [Ordre])
This call is perhaps to long to perform and this must explain why #error happens sometimes. Do you have any ideas to reduce the request time ?
A domain function (here DSum()) in the Details section can be problematic.
In your case it seems that you could easily replace that by using the RunningSum property, see:
https://support.office.com/en-us/article/summing-in-reports-ad4e310d-64e9-4699-8d33-b8ae9639fbf4#bmrunningsum
Thanks for the support. By the way, I was searching for a workaround on myself and I change the DSUM() by a RunningSum before our post your answer,
Of course, it works very well. Thanks for the tips !!!
I have recently tried to use Report Viewer Web Part in a SharePoint page. The reports have been used outside SharePoint for years. We are currently on SSRS 2008 R2 native mode and SharePoint 2007. After a while, when you go to the page with the web parts, you just get the error:
The report execution yoty4kmgk3hjr5uup1ng0a45 has expired or cannot be found. (rsExecutionNotFound)
And, in the SSRS log you get:
library!ReportServer_0-33!13bc!10/28/2013-11:09:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerStorageException: , An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.;
session!ReportServer_0-33!13bc!10/28/2013-11:09:45:: e ERROR: Error in getting session data: Invalid or Expired Session: yoty4kmgk3hjr5uup1ng0a45
session!ReportServer_0-33!13bc!10/28/2013-11:09:45:: i INFO: LoadSnapshot: Item with session: yoty4kmgk3hjr5uup1ng0a45, reportPath: , userName: DOMAIN\USER not found in the database
library!ReportServer_0-33!13bc!10/28/2013-11:09:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: , Microsoft.ReportingServices.Diagnostics.Utilities.ExecutionNotFoundException: The report execution yoty4kmgk3hjr5uup1ng0a45 has expired or cannot be found.;
library!ReportServer_0-33!f84!10/28/2013-11:09:45:: i INFO: RenderForNewSession('/PATH/REPORT')
Now I know exactly what this is. We get this all the time. When you run a report, SSRS takes a temporary snapshot and associates it with your session, and then renders from the snapshot to the browser. If you allow the report to sit open in the browser long enough the session times out and the temporary snapshot is destroyed. If you come back and try to interact with the report you will get this error because the session is gone. When this happens in a browser you can simply go back to the report manager and re-run the report to get a new session and snapshot.
Right now my creative team is working on the SharePoint layout and design. They have been working with at least three different example pages, which each hosts the same two SSRS reports in an instance of a Report Viewer Web Part. The reports do render normally when you initially place them on the page. However, after SSRS expires the session, the web part will show the session not found error. Each page establishes a different session for the same report so there will be multiple sessions open and the report will continue to render on one page after it starts showing the error on another.
The message is absolutely correct, the session does not exist. Sessions are transient, with a timeout of 600 seconds. This is expected behavior. So why is the instance of the web part in the page still holding on to the dead session? If you navigate away from the page and then come back, or you refresh the page, why does the SharePoint Report Viewer Web Part not go execute the report and get a new execution id? Is the web part not intelligent enough to know what's going on? Is there some expectation of the instance lifetime that's not being met?
So the question is: How could we get the SSRS SharePoint Web Part to be well behaved? In the SharePoint context a user should be able to open a page and interact with the content on it, unaware of where the content comes from or how it gets there, the experience should be seamless and transparent. In this case the Web Part is caching the session on the SharePoint server [I guess] so once SSRS kills the session the view in SharePoint just renders an error and we have found no way to refresh it.
Is there a way to solve this?
Try to increase the ssrs timeout. I am facing the same problem as I am using ssrs url in my asp.net web application to generate report. If I leave my page open for some time and come back to it, I get the same error that 'Report execution has expired'. I tried different options including adding &rc:UniqueGuid= newguid to the ssrs url, but of no help.
I have a report created in VS2008 on SQL Server 2008 (SP3).
The report comprises of several sub reports nested 3 or 4 levels down in some instances. Document Maps are used extensively so that Word Tables of Contents can be generated further down the line.
Now here's the problem.
If I render to screen either in the development environment or rendered the deployed report from the reporting services server, then everything is OK. If I export the report in any format (tested with Word, PDF & Excel) then the output is as expected.
However, if I create a URL including all the parameters something like
http://MYSERVERNAME/ReportServer/Pages/ReportViewer.aspx?%2fMYPATH%2fMYREPORTNAME&PARAM1=999&PARAM2=999&PARAM3=999&rs:Command=Render&rs:Format=HTML4.0
then paste this into an IE window, the output is incorrect.
Well let me clarify that.
If I render as above using the HTML4.0 rendering extension then the report renders on screen as expected, all the content is shown.
If I render to Word by changing the rs:Format parameter to Word then the report renders but the first page is missing (see note about this content below)
If I render to PDF, the same part of the report is missing.
If I render to Excel, the document map generated on the first workbook sheet shows an entry for the missing section of report but clicking the click gives and 'invalid reference' error and indeed that part of the report is again not rendered.
Note that the 'master' report for want of a better term is made up of 3 subreports, each of these contain other sub reports.
Its the content of the first subreport, that also happens to only every show on the first page (as it is just less than a page long) that is missing.
In Word there is something rendered but it looks like an empty table with a width that is the full width of the page but a heigh of just a few millimetres.
I'm really at a loss as to why the section does not render when it works perfectly if rendered to screen and then exported. I had assumed they would use the same rendering process but I'm not sure.
I'll continue to experiment, maybe add some blank content before the problem section or something and see where I get but I'm puzzled as to why this happens, other reports do not suffer the problem (however I have only tested 3 or 4 or the hundreds that I have written).
I've not used the URL method much in the past but I got to this point as I was writing a c# application to run the same report with varying parameters to produce over 1200 word documents, each of which takes about 2 mins to run. the output was incorrect there so I worked my way back to creating a manual URL and the problem was still apparent, the rest is history!
I finally found the answer.
The subreport that was causing the problems takes parameters that are subsequently passed on to other child subreports. While I was testing these, I had datasets that provided the available values for the parameters (list of countries and their associated ID's for example).
My normal method of working is to remove all datasets that are only used to populate parameters in all subreports as this improves performance (the report does not have to query the database to get a list of countries for example).
However, on this occasion I had removed all the datasets (which in itself was fine) but I had left the datasource in place (visible in the report data pane).
Once I removed this redundant entry, the report rendered as expected.
Now I'm still not sure why it rendered OK to HTML4.0 but it would appear that when rendering to other formats there is some process going on that looks at the datasource perhaps and as there is no data (as there are no datasets) then the report is not rendered. That's a bit of a guess but it's the only thing that makes sense to me at the moment.
My problem is with the reporting services for sql2008:
-I add a parameter to an already established report, where I get the names of certain people. RespStep, and it shows on the preview. But when I upload it to the server, it wontshow:
It pretends it´s loading for less than a second and then the report stays in blank.
NOTES:
This behavior happends only when I set the parameter to allow multiple value.
I thought it was a null problem, but the column from where the parameter values come has no nulls and still presents these problems.
I am desperate to know where the problem might be, on the server the data source and everything is well directed. Actually it shows no erros, just wont load anything and keep the page in blank.
just delete the report on server and re-depoly it.after that you can see the parameter in report
I'm trying to display an external image within a SSRS 2005 report, however I can't accomplish that. I've tried a lot of things but they just don't work.
I have a table in my report that displays a dynamic image based on code, I thought the error was in the code however it wasn't because I can see the image in BIDS, however when I try to display it on the report server or within an ASP.NET webpage it doesn't show up.
My Code is as follows:
Function ShowImage(value as Object) As String
Dim strImg as String
If value < 0
strImg= "http://icons.iconarchive.com/icons/fatcow/farm-fresh/24/traffic-lights-green-icon.png"
ElseIf value > 0
strImg= "http://icons.iconarchive.com/icons/fatcow/farm-fresh/24/traffic-lights-red-icon.png"
Else
strImg= "http://icons.iconarchive.com/icons/fatcow/farm-fresh/24/traffic-lights-yellow-icon.png"
End If
Return strImg End Function
The value in my image control is as follows:
=Code.ShowImage(Fields!Diferencia_Entre_Importes.Value)
When I see the preview in BIDS it shows up the way it's supposed to be, but it doesn't happen in the report server.
As you see the images don't need any kind of authentication, besides that, I tried configuring the Execution Account with the same result (I just get a horrible X instead of the image)
I also tried setting the image's value as
http://icons.iconarchive.com/icons/fatcow/farm-fresh/24/traffic-lights-green-icon.png
But had no success, also I tried using an image in the server in this way:
file:ImagePath
And had the same problem, using all of these solutions I can see the image in BIDS, but not in the Report Server.
Thank you very much
I suspect this is caused by an internet access issue on the account on the server running the SSRS report. Whether it is or not, I recommend saving those .png files locally on the server, and modifying the code accordingly - it should improve report performance as well as getting rid of this issue.