Skip to main content

Ssrs reports error when large number of parameters are passed


Now where you can find this web.config file?

If using SharePoint integration Mode: It’s located on the web server and has the path C:\inetpub\wwwroot\wss\VirtualDirectories\80\web.config

But you have to keep on mind if there is more than one SharePoint instance and what instance are you using to deploy the reports, of example the path can be C:\inetpub\wwwroot\wss\VirtualDirectories\EPMA\web.config

If using SSRS native Mode: The web.config file will be located at your SQL server and it will have the path: C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer.



The solution for this issue is to add a section in your web.config file inside the <appsettings/> section



<appSettings>

    ...

    <add key="aspnet:MaxHttpCollectionKeys" value="9999" />

    ...

</appSettings>



That 9999 value should represent the number of parameters that you believe it will be used.

Comments

Post a Comment

Hi User,
Thanks for visiting My Blog and please provide your valuable feedback and subscribe for more updates. Please don't post any spam content or comments.
Thank You

Popular posts from this blog

SSRS INTERVIEW QUESTIONS

Q: What is SSRS? Ă˜   SSRS or SQL Server Reporting Service is a server-based report generation software systems from Microsoft and is part of Microsoft BI. Ă˜   It is used for preparing and delivering interactive and variety of reports. Ă˜   It is administered through an web based interface. Ă˜   Reporting services utilizes a web service interface for supporting and developing of customized reporting applications. Ă˜   SSRS lets you create very rich reports (Tabular/Graphical/Interactive) from various datasources with rich data visualization (Charts, Maps, sparklines) Ă˜   SSRS allows are reports to be exported in various formats (Excel, PDF, word etc) Q: Explain SSRS Architecture? Reporting services architecture comprises of integrated components. It is a multi-tiered, included with application, server and data layers. This architecture is scalable and modular. A single installation can be used across multiple computers. It includes the fo...

Exception deserializing the package "The process cannot access the file because it is being used by another process."

TITLE: Microsoft Visual Studio ------------------------------ Failed to start project ------------------------------ ADDITIONAL INFORMATION: Exception deserializing the package "The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process.". (Microsoft.DataTransformationServices.VsIntegration) ------------------------------ The process cannot access the file 'E:\SSASCube\HistoricalDataLoad\HistoricalDataLoad\bin\Development\HistoricalDataLoad.ispac' because it is being used by another process. (mscorlib) ------------------------------ BUTTONS: OK ------------------------------ While running SSIS package i got the error “The process cannot access the file ‘*.ispac’ because it is being used by another process”. I tried to close SSDT and run it again but, I still got the same error while compiling. Then, after searching over internet, I got...

Failed to execute the package or element. Build errors were encountered

Error: TITLE: Microsoft Visual Studio ------------------------------ Failed to execute the package or element.   Build errors were encountered. For more information, see the Output window. ------------------------------ BUTTONS: OK ------------------------------   Solution: We tried to close SSDT and run it again but, we still got the same error while running SSIS package. Then, we need to follow bellow solution: Step 1: Go to Task Manager–> Details Tab. Step 2: Locate the process “ DtsDebugHost.exe “. Kill this process. There might be multiple instances of this process. Kill all of them. Step 3: Rerun SSIS package