718 Washington Ave. N. Suite #101
Minneapolis, MN 55401
View map and all Locations

Send us a message

This blog post is more for you Dynamics CRM developer types. (If you’re looking for something more basic, try our CRM How-to Portal.) If you’ve been getting an SSRS error that says “The number of requests for XYZUSER has exceeded the maximum number allowed for a single user”, then we have a solution for you today! Here’s what the error looks like:


SSRS error: exceeded maximum number of requests allowed for a user

This generally happens when you have a plugin or some background process sending the request to report server for report generation and the report server reaches the maximum number of allowed requests from a single user. Believe me! There is a cap on the report server on how many requests it can accept from a single user at a time. By default it is 20.

Sometimes it is not obvious where to go to change the configuration settings for SQL Server Reporting Services (SSRS). If you want to reconfigure the max number, you’ll need to find the configuration file. The file you want is called RSReportServer.config. Search for this file in the report server. It should be located inside the report server folder.

A typical location would be: C:Program FilesMicrosoft SQL ServerMSSQL.9Reporting ServicesReportServer

This depends upon the version of the reporting services that you have installed in that machine. If you have two report servers installed, then you might find this in two places. Best way to find is search for the file RSReportServer.config using command prompt.
Open this file in any text editor. Here are some of the values that you can change:

[sourcecode language=”SQL”]
<Add Key="SecureConnectionLevel" Value="0"/>
<Add Key="ProcessRecycleOptions" Value="0"/>
<Add Key="CleanupCycleMinutes" Value="10"/>
<Add Key="SQLCommandTimeoutSeconds" Value="120"/>
<Add Key="MaxActiveReqForOneUser" Value="20"/>
<Add Key="DatabaseQueryTimeout" Value="120"/>
<Add Key="RunningRequestsScavengerCycle" Value="60"/>
<Add Key="RunningRequestsDbCycle" Value="60"/>
<Add Key="RunningRequestsAge" Value="30"/>
<Add Key="MaxScheduleWait" Value="5"/>
<Add Key="DisplayErrorLink" Value="true"/>
<Add Key="WebServiceUseFileShareStorage" Value="false"/>

To resolve the issue discussed earlier, simply find MaxActiveReqForOneUser and set the value to some bigger number like:

[sourcecode language=”SQL”]
<Add Key="MaxActiveReqForOneUser" Value="100"/>

Save and close. You might want to run the iisreset command in the command prompt for these configurations to take effect.

Microsoft also provides more info about options in this configuration file and what they mean, so check that out for more information.

Happy CRMing!

Avatar for JoeCRM


Joe CRM is a CRM superhero who runs on pure Microsoft Dynamics CRM adrenaline. As the face of PowerObjects, Joe CRM’s mission is to reveal innovative ways to use Dynamics CRM and bring the application to more businesses and organizations around the world.