Skip to content
June 27, 2013 / sarachalaca

Error in SSRS – System.Web.HttpException: Maximum request length exceeded

After finishing developing a new report on a new solution on reporting services (this case on SSRS 2008 R2) I receive the following error while trying to deploy the project:

System.Web.Services.Protocols.SoapException: There was an exception running the extensions specified in the config file. —> System.Web.HttpException: Maximum request length exceeded.    at System.Web.HttpRequest.GetEntireRawContent()    at System.Web.HttpRequest.get_InputStream()    at System.Web.Services.Protocols.SoapServerProtocol.Initialize()    — End of inner exception stack trace —    at System.Web.Services.Protocols.SoapServerProtocol.Initialize()    at System.Web.Services.Protocols.ServerProtocol.SetContext(Type type, HttpContext context, HttpRequest request, HttpResponse response)    at System.Web.Services.Protocols.ServerProtocolFactory.Create(Type type, HttpContext context, HttpRequest request, HttpResponse response, Boolean& abortProcessing)

This error occurs because exists a property MaxRequestLength under the httpRuntime element in the file web.config (<your SSRS folder>\Reporting Services\ReportServer) where its default value is 4096 KB (4 MB) and when the report size is higher than this value, Reporting Services can’t upload a report successfully.

This error can be solved by doing the following steps:
1. Go to
(Example-> C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer)

2. Open the File

3. On the file web.config change the line
<httpRuntime executionTimeout=”9000″/>
To (for example):
<httpRuntime executionTimeout=”9000″ maxRequestLength = “16384” />
By default, the property maxRequestLength doesn’t exist in the config file and the default value is 4096 KB so you have to increase that value. In example above I am increasing the value to 16384 KB.



Leave a Comment
  1. Mostafa / Dec 4 2013 5:37 am

    Nice and helpful advide

    • Mostafa / Dec 4 2013 5:38 am

      I mean to say nice and helpful advice !

  2. Charles Mulwa / Apr 23 2014 2:34 pm

    This worked, I must add that I had to restart SSRS services to for the changed configuration to be picked up. You could also get around the size of the rdl by putting most of your SQL logic into Stored Procedures such that all you have in the rdl are stored procedure calls especially in cases where you have thousands of lines of code.

  3. isabel marant shoes sale / Jul 8 2014 8:36 am

    thank you for share!

  4. A happy Reader / Apr 22 2015 5:32 pm

    Thank you for the solution. It worked perfectly on SQL Server 2012 R2 with SP2. SSRS restart was not needed in our case.

  5. park / Jun 2 2015 8:07 am

    omg i love you.

  6. Benny Blanco / Jan 10 2016 10:13 am

    Nice job…Excellent information that saves me lots of digging and time !!

  7. billy / Jun 2 2016 6:45 pm

    You are my new hero

  8. Al / Jun 24 2016 5:11 pm

    This change not working for me on SQL Server 2008 R2

  9. Keith Simson / Aug 4 2017 5:00 pm

    Worked well for me too. Thanks!

    I’d like to add that you do not need to restart the services, but you may need to close and reopen BIDS. That’s what I had to do anyway.


  1. SQL Server Data Tools for Visual Studio 2013 – Report Sizes | Rob Sanders: Sanders Technology
  2. SQL Server Reporting Services (SSRS) Export - System.Web.HttpException: Zeit für Anforderung überschritten - SharePoint-Wiese

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 )

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s

%d bloggers like this: