Limits to passing parameters to reportserver via HTTP post?
Hi all, I'm passing params to my reportserver from a web page using HTTP POST. However, there is a multi value parameter that I want to send a lot of data to (usually over 100 items). When the data is passed to the report I get a 'page could not be displayed' message and it looks like the parameters are being placed into the querystring when they hit the server - does this mean my post request is being translated to a get request by SRS which is then passed to the reportsever url? It works fine with less parameters Anyone know if there is any way round this? Thanks, CharlesCharleh
April 27th, 2010 7:04pm

Hi all, I'm passing params to my reportserver from a web page using HTTP POST. However, there is a multi value parameter that I want to send a lot of data to (usually over 100 items). When the data is passed to the report I get a 'page could not be displayed' message and it looks like the parameters are being placed into the querystring when they hit the server - does this mean my post request is being translated to a get request by SRS which is then passed to the reportsever url? It works fine with less parameters Anyone know if there is any way round this? Thanks, Charles Charleh Hi, If you use SSRS web servuces + ReportViewer then should NOT be any problem. This report passes more then 2000 items without any problem. Alexei Cioina
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2010 8:08pm

Ok, I'll try the web service, I'm using legacy VB6 here though but I'm sure you can extend vb6 with web services functionality ThanksCharleh
April 28th, 2010 12:19pm

Hi Charleh, By default, in HTTPRuntime, the limit for the input stream buffering threshold is 4096 KB. If the threshold is exceeded, the post method will fail. We can increse the limit following these steps: 1.Open the web.config of Report Manager with TextEditor(such as Notepad) By default, the file is located at: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportManager 2.Add the maxRequestLength to the HttpRuntime E.g. <httpRuntime executionTimeout="9000" maxRequestLength="9000" /> 3.Open the web.config of Report Server with TextEditor(such as Notepad) By default, the file is located at C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer 4.Add the maxRequestLength to the HttpRuntime E.g. <httpRuntime executionTimeout="9000" maxRequestLength="9000" /> If you have any more questions, please feel free to ask. Thanks, Jin ChenJin Chen - MSFT
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2010 6:40am

Hi Jin Chen, I'm tracing the same issue in one of my applications. After listenning to the network's traffic, I was able to understand the Report Server is redirecting the client's request (using a HTTP 302 found reply with the long path including the report parameters). I applied your workaround, however the problem is still there. Is there any reason why the Report Server is requesting the redirection on the client side??? Thanks, - David.Net Developer
July 30th, 2010 12:11am

hi dvidben, i solve the same issue by changing the FORM ACTION from http://.../ReportServer?<report path> to http://.../ReportServer/Pages/ReportViewer.aspx?<report path> Charlie
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 3:27am

hi dvidben, i solve the same issue by adding one more parameter: <input type="hidden" name="rc:Toolbar" value="false"/> but my client needs the toolbar:(
April 7th, 2011 3:29am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics