Skip to content
April 29, 2013 / Francisco Castro

Reporting Services: Your Report doesn’t show up (only a blank page)?


A very typical problem when designing complex reports on Microsoft Reporting Service is the limitation on the number of elements that can be loaded on filters.

If you define a report with default values to all parameters, when you open it, the report should be automatically generated. But if this problem occurs, the page appears blank. If you dig into log files you’ll find the following error: ThrowIfMaxHttpCollectionKeysExceeded()

This error occurs simply because your report uses more than the allowed number of elements in the filters/parameters. The default limit is 1000, but you can change it.


Locate the web.config files for the ReportManager & ReportServer. These files should be located somewhere like this:

C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager\Web.config
C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\Web.config

Once you locate both Web.config files, you need to edit them adding the following bit of code:

<add key="aspnet:IgnoreFormActionAttribute" value="true" /> 
<add key="aspnet:MaxHttpCollectionKeys" value="100000" />  

These app settings should be added between /system.web and runtime nodes, so the files should look something like the following:

<add key="aspnet:IgnoreFormActionAttribute" value="true" /> 
<add key="aspnet:MaxHttpCollectionKeys" value="100000" /> 

NOTE: The ReportManager may already have an app settings node so you will only need to paste the two add key lines.The ReportServer will more than likely require all 4 lines (including the open and close appsettings nodes).


Here is the original post that I used to solve this issue:Original Link



Leave a Comment
  1. Derrick Claar / Jan 29 2014 10:31 pm

    Why should the appSettings element be added between the system.web and runtime nodes? I’ve tried identifying other nuances like this in SSRS, but have found the msdn docs on this very sparse. Thanks!

    • Rodrigo Chiolas / Apr 23 2014 2:52 pm

      Hi Derrick, sorry for the delay, I have no idea why but if i had to guess, i’d say it is about how SSRS read and process the web.config tags. It probably needs to read appSettings first before process runtime nodes.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: