I am trying to create a subscription for an SSRS report in Report Manager on the report server.
When I click OK or try to change the time, I immediately get an error message:
Maximum request length exceeded.
When I Google for the error, the answers all relate to the size of the RDL report file being over 4 meg. My report is only 384k and the resulting Excel file is only 119k.
Is there anything else I can change to make this work?
I have also noticed that when I do get the error, my current Internet Explorer history is wiped out. I cannot go BACK after getting the error. I get the same error with Chrome except that the history doesn't get wiped out.
I had a working subscription but I deleted to try with a newly deployed version of the report.
History wiped out?
Related
I have multiple report running by creating subscription.
All reports are generating PDF files to the given drive. However, one report having error:
Failure writing file Filename#timestamp : Report processing has been canceled by the user.
This report is working fine from development PC and taking around a minute to get/render the data. However, it’s taking long time in the report server to be rendered.That is, sometimes its rending (taking more than 30 mins) and sometimes not.
Also, there is error while executing under subscription:
Failure writing file Filename#timestamp : Report processing has been canceled by the user.
Please note that, no one is cancelling the report, then why am I getting this kind of error message.
Do not time out report "site setting" as well as "individual report".
EDIT:
Got one new error, while just executing report (no subscription):
Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occurred while processing the request on the server. The status code returned from the server was: 12002
What is wrong with this? How to debug this? How to fix this issue?
Note: this report query has NOLOCK and deployed in released mode from SSDT.
Thanks.
I've created a shared dataset in both BIDS and Report Builder. The data source is set up to use a windows service account. I've also tried it with a sql user that is verified to work.
In both BIDS and Report Builder, data is returned. When I go to the report portal and try to preview the data, or try to add it is a dataset to a mobile report, it throws an error:
I've given permissions at the root folder level to NT Authority\Authenticated Users and to my department's AD group, with all rights granted.
I'm not really sure what else to do, or where to even check to see what the error actually is. Any help is appreciated.
So I figured it out - it actually had nothing to do with permissions. A fiddler trace showed a 422 and 500 errors.
422: the Dataset could not be processed. The 500 said
500: There was a problem getting data from the Report Server Web Service: System.Web.Services.Protocols.SoapException: The JSON SharedDataSet Table renderer cannot parse the supplied report...
This lead me to check the actual query coming back, which had a Geography data type coming back for one of the fields. When I removed this from the query, everything worked fine.
I have a 2012 SSRS scale out with 2 servers. When users run a report the report comes back in a timely manner but if the user tries to export the report to Excel the "remote server returned an error: (401)" error message comes up. I have run the report on my local report builder with the same results. This error doesn't occur all the time. There are instances when the report executes as intended but the majority of the time it ends with failure. One interesting side not is if we put the report as a subscription it will be successful every time. Thanks in advance.
You mention the error doesn't occur all the time. Who does it occur for? 401 errors are usually cause by "Unauthorized access". This seems like a permissions or Credentials error on the server you are encountering the problem.
See similar below:
http://bidn.com/Blogs/the-remote-server-returned-an-error-401-unauthorized
I am having this problem where the data being shown in report is different when I deploy it on server. So let's say if I am viewing report by pressing F5 (to debug) or by clicking on "Preview" button on the report in BI Studio the data shown is correct. But when I deploy the same report and when I run it from server such as http://myserver/reports then data shown is incorrect/missing.
For e.g. in some cases it is not showing data for a particular field and there are some number fields which are showing wrong data. I have cleaned the solution, deleted data cache files, rebuilt and deployed like 100 times but no luck.
When I deploy it shows some warning (which I guess I can ignore) but no errors.
I have checked the database by running queries and stored procedures directly and they all return correct data.
How do I fix this issue?
I went to report server and looked at the XML of one of the data set which was creating problem and found out that the new FIELD I have added is not there. Then I tried to deploy that data set and it said Overwrite Dataset property is set to False and that's why it was not deploying and I missed it in messages when it deploys a solution. So I simply set the property to True, deployed it and viola problem is solved.
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.