I am trying to run a report in SSRS 2016. After running the report, it throws "Maximum request lenght exceeded".
So, I've found a possoble solution as to put "maxRequestLenght" into web.config file in Report Server directory.
I've changed this line to the following:
<httpRuntime executionTimeout="9000" requestValidationMode="2.0" maxRequestLenght="10000" />
and restarted the Reporting Services service (in Reporting Services Configuration Manager).
After restart I am trying to run the report again and I am getting "HTTP 500 The website cannot display the page"
Restarting SQL, rerstarting SSRS, restarting Windows didnt help
Related
I'm running SQL Server 2016 and have local reporting services running.
I can run my SSRS reports up fine and display them to screen.
I can also export them to PDF or to CSV but if I try to export to Word, PP or EXCEL I get:
Reporting Services Error
An error occurred during rendering of the report. (rrRenderingError)
An error occurred during rendering of the report.
The type initializer for 'MS.Utility.EventTrace' threw an exception.
Requested registry access is not allowed.
the same report works fine on other peoples machines in the office so I know it's not to do with the report itself.
I've tried
Has anyone else had this issue or know how I can shift it?
I just spent hours troubleshooting this in a fresh install of SSRS 2019 using an updated database from a prior version.
I'm using an execution account with low permissions and did not want to make it a full Local Admin permanently but I tried adding it, unsuccessfully.
I removed the account from unattended execution in Report Services Configuration Manager and suddenly was able to export to XLSX. I was not sure what the fallout would be for existing reports, so I was not satisfied with this solution either.
Elsewhere I saw a recommendation to use Process Monitor (procmon) to watch for registry key access denials, you can download it here procmon.
It was difficult to search all of the output but you can filter by registry key access, then look for the RS executables or the result ACCESS DENIED.
In my case, it was HKU\%service account sid%\Software\Microsoft\Avalon.Graphics, and granting the execution account (not the account that runs the service) Read access to this key resolved the issue.
I got the same issue. Check in the URL (once you click on excel) whether the format is EXCELOPENXML. If yes change it to EXCEL.
Then it will download and work correctly.
You can enable it to 'EXCEL' by default by changing the 'rsserverconfig' file under reporting services. It will download in 'xls' format not 'xlsx'
NOTE: This solution is a common workaround when rendering extensions fail to work due to your deployment configuration or environment.
RSServerConfig
C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\rsreportserver.config
Look for the Render section, enable or disable the export formats that you want your users to have access to. see Rendering Extensions Overview on SQLDocs for more information on individual extensions.
<Render>
<Extension Name="WORDOPENXML" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordOpenXmlRenderer.WordOpenXmlDocumentRenderer,Microsoft.ReportingServices.WordRendering"/>
<Extension Name="WORD" Type="Microsoft.ReportingServices.Rendering.WordRenderer.WordDocumentRenderer,Microsoft.ReportingServices.WordRendering" Visible="false"/>
<Extension Name="EXCELOPENXML" Type="Microsoft.ReportingServices.Rendering.ExcelOpenXmlRenderer.ExcelOpenXmlRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="false"/>
<Extension Name="EXCEL" Type="Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer,Microsoft.ReportingServices.ExcelRendering" Visible="true"/>
…
<Render>
I had the same issue in SSRS2016 on a clean install of Windows Server 2016 & SQL 2016 with SSRS with all SP's & CU's and windows updated applied.
To confirm my fix, the execution account was not a member of the local administrators group on the SSRS server, once added and stop/start of SSRS, I am now able to export to Excel & Word, not the most secure way of getting it working but better than enabling the depreciated Excel 2003.
I had the same issue in SSRS 2019, and the fix was quite easy.
In Report Server Configuration Manager > Service Account, I had it set to "Use built-in account" = "Virtual Service Account".
I changed to "User another account", and selected a local users who is part of the Administrators group.
NOTE: This is NOT the Execution Account. This is for the Service Account.
You could be getting this error in Excel because the maximum number of rows that can be put in an excel sheet is 65536. If your data has more rows than that it will throw that error.
I got this issue on one of my machines when I installed MSSQL Server 2016 with SSIS, SSAS and SSRS.
SSIS and SSAS is working fine but SSRS does not.
After the installation, I opened the Reporting Services Configuration Manager and leave everything to default. This usually the end of it, but for some reason when opening the Portal, I got this:
When I check the log, the error is
ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: Invalid PBI Configuration, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
What is Invalid PBI Configuration? And how do I identify the problem?
Thank you in advance.
Took a while to sort this out, but it's a simple fix.
Open SQL Server Reporting Services Configuration Manager
Click on Web Service URL menu and make sure that the URL's match the ones located in Web Portal URL menu.
If they're different, open the rsreportserver.config file (C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer) and remove any entries not listed in Web Service URL.
Open your web portal ie. http://localhost/Reports and see if it's resolved. If so, all done.
If not, click the Encryption Keys menu, in the "Delete Encrypted Content" section, click "Delete".
Open your web portal again and see if it's resolved.
Locate and update your datasource credentials.
I have installed SSRS 2014 and Configured. When I open the web link from Report Server Configuration Manager I get below message,
I can't see any home page. I am not sure what is missing.
The correct format for the report manager is
http://<Server Name>/Reports/Pages/Folder.aspx?ViewMode=List
Have you solve it yet?
It might happen because the reporting service is not running-make sure the service is running ( can check at sql server config manager) screenshots added.
You can also refresh the service from command prompt by typing:
net stop reporting service
and
net start reporting service
Sql Server Configuration Manager
am getting the following error when attempting to run an MVC website in VS2013 and SQl Server 2014 using the ReportViewer control and accessing a report from the report server:
RSExecutionConnection MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report server is a compatible version.
I am using the correct report server url foun in the Reporting Services configuration manager. When I attempt to run the report in the SSRS project, the system prompts me for a user name and password. I enter the computer admin user/password. The report then runs. By the way, the reportviewer control uses the same user/password.
I am also able to access both the report server and reports urls in a browser with the same prompt for user//password.
I tried fiddling around with the report server role settings and under folder settings, this user has all privileges checked (browser, content manager, my reports, publisher, report builder).
Also as a side issue, I cannot see site settings even if I invoke the browser as an administrator.
I also looked in the SSRS Configuration manager. The service account is "Local System". The same admin user is listed in "Execution Account".
When running the website, I see no error entries in the SSRS log.
Please help, I have been looking into this for 2 days.
I think these solutions can help
Change from Local System to Network Service in Service Account of Reporting Services Configuration Manager
Update the web.config of ReportServer for these settings as below
<authentication mode="Windows" />
<identity impersonate="true" />
I'm fairly new to reporting services. I have set up a timed subscription to run a report and write it to a file though the report manager. I can see that the report ran but I see the following error.
"Failure writing file FIRM_LIST : The report server has encountered a configuration error."
Any ideas to get more specifics on the error?
Check in the application log on the reports server.
If there is nothing in there check in the reporting services LogFiles directory (something like C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles), these tend to give you quite a bit of info.
In my experience the main problem with scheduling reports to write to a folder are permissions issues. Make sure the user you are using to run the report has write/delete access into the folder you are trying to save to