Hi @Rui Pinto Ferreira,
Thanks for reaching out to us. We are very pleased to assist you.
Concerning the issue you mentioned, we have also done some internal research and found that the error you're encountering in SQL Server Reporting Services (SSRS) typically indicates a timeout or resource limitation issue.
Here are some steps you can take to resolve this:
1.Increase Execution Timeout:
Please modify the web.config for the SharePoint site with SSRS Integrated (Web.Config for the SharePoint site can be located from IIS Manager by exploring the site).
Adjust the httpRuntime
element to include a higher executionTimeout
value:
<httpRuntime executionTimeout="1800" maxRequestLength="51200"/>
This change allows the server more time to process large reports.
2.Adjust App Settings:
Add or modify the following settings in the web.config
file to handle larger requests:
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="100000" />
<add key="aspnet:IgnoreFormActionAttribute" value="true" />
</appSettings>
These settings help manage large collections of data and form actions.
To locate the web.config
file for SQL Server Reporting Services (SSRS), follow these steps:
- Open File Explorer: Navigate to the directory where SSRS is installed. The default installation path is usually:
C:\Program Files\Microsoft SQL Server\MSRS<version>.<instance>\Reporting Services\ReportServer
- Replace
<version>
and<instance>
with your specific SSRS version and instance name. - Locate the
web.config
File: Within theReportServer
directory, you should find theweb.config
file. This file contains configuration settings for SSRS. - Before making any changes, it's a good practice to create a backup of the
web.config
file.
If the problem persists, it is recommend configuring SSRS specific information for the SharePoint Unified Logging service. For more information, see Turn on Reporting Services events for the SharePoint trace log (ULS).
We need to check the logs for more detailed error information to further analyze the cause of the problem. If it is convenient, you can share the error log information with us (please be careful not to disclose your private information).
Should you have any concern or queries, please feel free to contact us.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. It will be beneficial to more community members reading here. Your contribution will be highly appreciated.