When deploying large reports to SharePoint or Reporting Services from BIDS (Visual Studio) something like the following message might appear:
Error 1 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) 0 0
This happens when the report is bigger than the maxRequestLength specified in the Reporting Services web.config file. The default is 4 MB so if the Report is bigger than that it will fail to deploy. it will frequently happen if the report contains map reports using embedded esri shape file data…
The solution, apart from making the report smaller, is to increase the maxRequestLength attribute of the httpRuntime Element in the web.config file of the Reporting Services instance. This file might be found in a directory like this for SQL Server 2008 r2: C:Program FilesMicrosoft SQL ServerMSRS10_50.MSSQLSERVERReporting ServicesReportServer
Change the element to the following:
<httpRuntime executionTimeout="9000" maxRequestLength = "16384" />
where the 16384 equals 16 MB max sixe for the reports. Change the value to suit your report size needs…
more information about the element in this article: http://msdn.microsoft.com/en-us/library/e1f13641.aspx
Updated 2012-12-08: The above link is outdated. Here are some alternative resources:
Report and Snapshot Size Limits (SQL Server 2008)
Modify Reporting Services configuration files [AX 2012]