When trying to export an SSRS report to excel, I am getting a runtime error. I have looked at the logs and see the following:
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.;
The report displays fine in Report Manager, and has run successfully in the past.
The report is only not very complex, and is approx 40 columns wide. When I run the query in SSMS I get 27,628 records, and it takes 3 seconds to run (again, im SSMS). The report runs fairly quickly in Report Manager also, and exporting the results to .scv format works as expected.
If any additional information is needed to help with resolving this, please let me know and I will provide it. Thanks for you help in advance!
Additionally, report has been set to not timeout. Report runs in VS2010 and exports to Excel as expected.
Your connection might be timing out. Try changing the timeout length by:
1.Open the rsreportserver.config with Text Editior(e.g. Visual Studio, NotePad). By default, it is hosted in C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
2.Change the value for 'DatabaseQueryTimeout'. Valid values range from 0 to 2147483647. A value of 0 specifies an unlimited wait time and therefore is not recommended.
3.Save the file, and then restart the Reporting Services to apply the changing.
http://msdn.microsoft.com/en-us/library/ms157273.aspx
This tip is for anyone struggling with SSRS Excel export runtime error:
I got this error when I had a typo in my .rdl-file, namely in Language-element I had culture written wrong. Replacing it with value: =User.Language, fixed my case.
Try adding the config below on your web.config (main app). This change resolved my issue.
<location path="Reserved.ReportViewerWebControl.axd">
<system.web>
<!-- adjust the timeout value accordingly -->
<httpRuntime executionTimeout="3600"/>
</system.web>
</location>
Related
I'm having problems when using the option "Get values from a query" in my Parameter settings.
On the server everything works like a charm.
But when I deploy and then launch the report on my hosting, I get an error message:
If I use the option: "None", then everything works fine.
I've placed a test Tablix, to see the result of the dataset on the host, and also this causes no problem.
So the issue is only with the "Get values from a query" section AND only on the hosting.
Anybody got an idea?
EDIT: I turned EnableRemoteErrors on, as requested by the errormessage, but no additional info is given.
The detail of the error is in the SSRS log file located at -->
<SSSRS_INSTALL_DIR>\Report Server\Log Files.
That is where I would go. Based how you describe the dataset driving the parameters works but not when given a value then I would expect this to be a parameter mismatch or missing parameter. Make sure that you are feeding the dataset the parameters you think you are. Also, if you don't allow nulls then make sure you are supplying a default value.
You said, you placed a tablix on the report showing the results of the YearsDOW dataset and this fails. If this also fails when you set your available values to 'None' then we can assume, as the error states, that the issue was with executing the query itself, not your report design.
As this seems to work when you run it from your local machine in development but fails when run from the server I would suspect it's an authentication/permissions issue.
Check the credentials on the datasource in your development environment and compare these to the SSRS server's version of the datasource. Remember, by default datasources do not get overwritten so it maybe that you deployed the datasource initially with one set of credentials then then changed them in your development environment.
If this is the case and the datasource is not used for other reports on the server, then you can either change the project properties to overwrite datasources but personally I prefer to delete the datasource from the server and then redeploy, that way future changes won't affect the servers version unintentionally.
If the datasource is used in other reports without problems then you could just rename the datasource to something unique so it will get redeployed under the new name and your report will point to that new version.
Can someone happen to let me know what the maximum value that can be set for maxRequestLength in the SSRS web.config file. I currently have it set to 2097151 but if I increase it any further the SSRS Reports homepage stops working and just displays "Error" I have restarted SSRS through the service as well as the config manager but nothing seems to work, can anyone assist? The location of the file that I am editing is "C:\Program Files\Microsoft SQL Server\MSRS12.MSSQLSERVER\Reporting Services\ReportServer"
Thanks
I have found what was the issue, though I had set the maxRequestLength within the relevant config files in SSRS, I had to also amend the Limit Size set in IIS for the SMTP, once I had increased the size here everything worked fine.
I think there was some initial confusion on the error message due to getting a similar one before based on the config file.
I have a report with a list of customers passed in as a parameter. This list has become quite large and found it hit the limit imposed by MaxHttpCollectionKeys. I've found this documented in several posts, but I now have a more specific issue.
I have set this a lot higher in the SSRS web.config file which has solved the problem when I access the report via the report manager (ServerName/Reports). However this doesn't solve the problem when I render via the report server (ServerName/ReportServer).
I do need to access these reports via the report server as we pass some hidden parameters through from our App, as well as having some user selectable parameters. Searching for the solution only gives me posts related to the original solution which I've found.
Does anyone else have any ideas on solutions for this.
Many thanks.
Ok found solution.
I didn't realise there are two web.config files. One for the manager, one for the server. These both needed to have the mod made. Needed to add the following code to the web.config file in
C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
Between the < system.web > and < runtime > tags.
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="20000" />
</appSettings>
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 created a report an SSRS report in VS 2008, and running it on a Windows Server 2012. When I run the report from Report Manager, it runs with no issues. However, when I set up a scheduled subscription, I get the following error message: Failure sending mail: An error occurred during rendering of the report. Mail will not be resent.
I have tried a number of Render Format options, including Excel, Word and CSV. It has failed on each of these formats. I did try the 'XML file with report data' option and the mail was sent. I also used the 'Include Link' option without including the report and that worked.
I have also set the Report Timeout option to 'Do not timeout report' in the Processing Options but still got the problem.
I am also running another report that is identical, except for the time interval and it runs fine. The report that is failing captures weekly data, while the report that runs OK captures monthly data.
Any ideas of what is going on with this report? I have provided all the information I can think of, but if anyone needs anything additional, please let me know! Thank you for your assistance!
Although I am not 100% certain of this, after I changed the name and removed some special characters (primarily parenthesis) and this seemed to clear it up.
Edit: After a significant span of time has passed I am certain that this was not a fix. I have a couple of reports that seemed to run fine for a while but then failed. When running the report from Report Manager it runs fine, and can be exported without any problem.
I subsequently ran the report from Report Manager and exported it into a .csv file. After opening this file in a text editor, I noticed that there were double quotation (") marks randomly distributed throughout the report. This did not show when exporting to excel. I rewrote the script to replace the quotations with blank spaces. I ran it again from Report Manager and exported it again to .csv and there were double quotes in the result. When I do this from SSMS I don't get the double quotes. It appears then that this occurs as a result of the export. The report will display in Report Manager, but won't go out in subscriptions.
Any ideas or suggestions would certainly be appreciated. I have worked on this for a while now (months) and need to come to some resolution. Thanks!
The solution ultimately was found and solved by updating the sql server with a service pack that was missing.