SSRS: The deployment has exceeded the maximum request length allowed by the target server

Earlier today, I was deploying SQL Server Reporting Services (SSRS) reports for a client who just upgraded from version 9 to version 2010 R2 on Microsoft SQL Server 2008 R2. Upon beginning the deployment, the following error came up:

maxRequestLength error deploying BI reports

The error and it’s resolution are pretty clear and called for setting the maxRequestLength attribute to “20690” in SSRS’s web.config file.

Web.config

The SSRS web.config file can typically be found under the %programfiles%\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\Report Server, for a Microsoft SQL Server 2008 R2 SSRS installtion done in Native mode. If you have other types of deployments, for example, SharePoint integrated, it will be necessary to consult with your system administrator.

You can then proceed to use Visual Studio or, simply, Notepad to edit the web.config file, locating the httpRuntime element of the XML document.

web.config – httpRuntime section

The final edit of this section should look like this, with the maxRequestLength attribute added.

web.config – Edited httpRuntime section with maxRequestLength parameter

Once the web.config file was saved, I reinitiated the deployment and all was well. The maxRequestLength attribute specifies the maximum upload size for a file into the SSRS reports library in kilobytes. For this specific instance, 20,690 seems to be the magical number.

Until next post!

MG.-
Mariano Gomez, MVP
IntellPartners, LLC
http://www.intellpartners.com/

Advertisements

3 Responses to SSRS: The deployment has exceeded the maximum request length allowed by the target server

  1. Kumar says:

    Mariano, Great post with screenshots. The same issue has been summarized in Daoud's article in his blog http://mohdaoud.blogspot.com/2011/04/dynamics-gp-2010-r2-business.html.

  2. Raja says:

    this is very valuable information. Thank you for posting this.

  3. Thanks Mariano,Nice to find a solution at 4am, all spelled out, with screenshots and exactly what I needed to fix the error I was seeing. You're the best!-Victoria

Leave a Reply

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

WordPress.com Logo

You are commenting using your WordPress.com 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: