Maximum Request Length Exceeded Help!

I have a report that has 14 user supplied parameters. When I added a 15th parameter and deployed the report, I get an error of Maximum Request Length Exceeded when I try to set up a subscription to the report. All of the subscriptions on the report are failing now and users are getting rather upset.

Please help! How do I get rid of the Maximum Request Length Exceeded error?

Thanks!

i'm not entirely sure, but shortening your parameter names may help.

ie: CustomerLocation to 'Loc'

|||

Redmanmc wrote:

I have a report that has 14 user supplied parameters. When I added a 15th parameter and deployed the report, I get an error of Maximum Request Length Exceeded when I try to set up a subscription to the report. All of the subscriptions on the report are failing now and users are getting rather upset.

Please help! How do I get rid of the Maximum Request Length Exceeded error?

Thanks!

did you ever find a fix for this problem? i seemed to have stumbled upon it myself. thanks

|||

Unfortunently I have not found a solution to the problem yet. I tried reducing the length of the variable names but it did not fix the problem.

If anyone out there has a fix please yell out!

|||

good news.. found a fix for this.

it's actually the same fix for file uploads that exceed the default 4mb set by IIS. however, the change needs to made to the report manager web.config file and not the report server web.config file. that's why it didn't work for me the first time.

here is an article that talks about it http://support.softartisans.com/kbview_825.aspx

if you have kept the default installation directory, the file you edit is:

C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\Web.config

Just add the maxRequestLength property here and set a size appropriate to you. Not to large to discourage DoS attacks.

The example below is 10mb

<httpRuntime executionTimeout="9000" maxRequestLength="10240"/>

hope it helps.

Maximum Number of Parameters

Is there a limit to the maximum number of parameters that can be used
in Reporting Services when you render a report.
I hava report that uses about 35 parameters. the preview works fine but
when I deploy the report to the server and render no data comes back.
If I have 30 parameters it works fine.How much data is in those parameters? You may be bumping up against the
maximum length for a URL (browser GET).
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
<isam5030@.hotmail.com> wrote in message
news:1102471837.315758.229690@.f14g2000cwb.googlegroups.com...
> Is there a limit to the maximum number of parameters that can be used
> in Reporting Services when you render a report.
> I hava report that uses about 35 parameters. the preview works fine but
> when I deploy the report to the server and render no data comes back.
> If I have 30 parameters it works fine.
>

Maximum Number of Input Parameters

We created a report with 42 parameters in it. While in VS, it
previewed fine. Then in our preferred browser Firefox, it rendered
fine as well. Only after we had to test different platforms did we
realize that it did not work in IE 6 or 7, using our interface, or
even the MS Report web interface. This seemed really odd as we are
able to run this report through Firefox.
We then created a test report with nothing in it and just started
adding parameters to it, uploading it, and used the MS Report web
interface to view it. At 36 parameters, it stopped working...
We removed shortened up the length of the names of the parameters to
see if it was a GET/POST issue, but the same limit happened.
Anyone else with this issue? Any suggestions?On Mar 1, 12:12 pm, "dmcnamer" <dmcna...@.gmail.com> wrote:
> We created a report with 42 parameters in it. While in VS, it
> previewed fine. Then in our preferred browser Firefox, it rendered
> fine as well. Only after we had to test different platforms did we
> realize that it did not work in IE 6 or 7, using our interface, or
> even the MS Report web interface. This seemed really odd as we are
> able to run this report through Firefox.
> We then created a test report with nothing in it and just started
> adding parameters to it, uploading it, and used the MS Report web
> interface to view it. At 36 parameters, it stopped working...
> We removed shortened up the length of the names of the parameters to
> see if it was a GET/POST issue, but the same limit happened.
> Anyone else with this issue? Any suggestions?
I've never used this many parameters; however, it sounds like it is
related to a limitation in IE 6/7 page rendering. Is there not a way
that this report can be split up into more than one report?
Enrique Martinez
Sr. SQL Server Developer|||On Mar 1, 10:05 pm, "EMartinez" <emartinez...@.gmail.com> wrote:
> On Mar 1, 12:12 pm, "dmcnamer" <dmcna...@.gmail.com> wrote:
> > We created a report with 42 parameters in it. While in VS, it
> > previewed fine. Then in our preferred browser Firefox, it rendered
> > fine as well. Only after we had to test different platforms did we
> > realize that it did not work in IE 6 or 7, using our interface, or
> > even the MS Report web interface. This seemed really odd as we are
> > able to run this report through Firefox.
> > We then created a test report with nothing in it and just started
> > adding parameters to it, uploading it, and used the MS Report web
> > interface to view it. At 36 parameters, it stopped working...
> > We removed shortened up the length of the names of the parameters to
> > see if it was a GET/POST issue, but the same limit happened.
> > Anyone else with this issue? Any suggestions?
> I've never used this many parameters; however, it sounds like it is
> related to a limitation in IE 6/7 page rendering. Is there not a way
> that this report can be split up into more than one report?
> Enrique Martinez
> Sr. SQL Server Developer
we are not able to split up the report, as it is a summary report
which requires all of the input parameters. we contacted MS tech
support and, for some reason, they were able to get this to work.
however, we gave them access to our machines and it did not work for
them. they spent a while trying to figure it out with IE and SQL RS
people on the line and were not able to figure out which setting
combination made this not work. our guy got tired from staying on the
line. instead, we created a bit string to represent all of the binary
options get around this limitation and then parse the bit string in
the report.