Maybe it's just Vista that has the problem?!?

So I installed a second instance of Report Server since the default instance couldn't find any default directories and I got this error message with started my saga Friday. I actually chose to follow MS's advise and do solution 1). That is when Report Server first lost track of it's directories and caused me to reinstall everything.

Does anyone know what this means?

Server Error in Application "Default Web Site/ReportServer$Two"

---

HTTP Error 500.0 - Internal Server Error

Description: This application is running in an application pool that uses the Integrated .NET mode. This is the preferred mode for running ASP.NET applications on the current and future version of IIS.

In this mode, the application should not specify ASP.NET handler mappings in the <system.web>/<httpHandlers> configuration section. Instead, it should use the <system.webServer>/<handlers> configuration section to configure ASP.NET handler mappings. You have the following options:

1) Migrate the application to work with the Integrated .NET mode (PREFERRED).

You can migrate the application configuration, including the contents of the <httpHandlers> configuration section, by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE migrate config "Default Web Site/ReportServer$Two"

After you migrate your application, it will run in both Classic and Integrated .NET modes, as well as on downlevel platforms.

2) Move this application to an application pool using the Classic .NET mode.

You can move the application to an application pool that uses the Classic .NET mode by using the following from a command line window (the window must be running as Administrator):

%systemroot%\system32\inetsrv\APPCMD.EXE set app "Default Web Site/ReportServer$Two" /applicationPool:"Classic .NET AppPool"

Alternatively, you can use any other application pool on your system that is running in the Classic .NET mode. You can also use the IIS Administration tool to move this application to another application pool.

It is preferred that you migrate this application by using option 1 to take advantage of the benefits provided by the Integrated .NET mode.

Error Code: 0x80070032

Notification: BeginRequest

Module: ConfigurationValidationModule

Requested URL: http://jc:80/ReportServer$Two

Physical Path: C:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\ReportServer

Logon User: Not yet determined

Logon Method: Not yet determined

Handler: AboMapperCustom-43870

Most likely causes: IIS received the request; however, an internal error occurred during the processing of the request. The root cause of this error depends on which module handles the request and what was happening in the worker process when this error occurred. IIS was not able to access the web.config file for the Web site or application. This can occur if the NTFS permissions are set incorrectly. IIS was not able to process configuration for the Web site or application. The authenticated user does not have permission to use this DLL. The request is mapped to a managed handler but the .NET Extensibility Feature is not installed.

What you can try: Ensure that the NTFS permissions for the web.config file are correct and allow access to the Web server's machine account. Check the event logs to see if any additional information was logged. Verify the permissions for the DLL. Install the .NET Extensibility feature if the request is mapped to a managed handler. Create a tracing rule to track failed requests for this HTTP status code. For more information about creating a tracing rule for failed requests, click here.

More Information... This error means that there was a problem while processing the request. The request was received by the Web server, but during processing a fatal error occurred, causing the 500 error.

Microsoft Knowledge Base Articles: 294807

---

Server Version Information: Internet Information Services 7.0.Could be. I heard that SQL has some problems with Vista. Check on the Microsoft site and make sure you have the new update for Vista and VS 2005 SP1. You'll have to download SP1 though. Or maybe check for some SQL updates for Vista.

maximum width

When loading a report that another developer created, I got an error
message saying that the deserialization failed because the width value
needs to be between 0 and 85.3333 in. I was able to get around this by
opening the RDL file in notepad and changing the width values manually.
But my questions is, how was the developer able to set the width >
85.3333 if it was not allowed?Probably, the report was manually edited.
As for the 85.3 in limit - in RS 2000 SP2 it will increase to 160 in.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bucky" <uw_badgers@.mail.com> wrote in message
news:1103826459.105803.261470@.f14g2000cwb.googlegroups.com...
> When loading a report that another developer created, I got an error
> message saying that the deserialization failed because the width value
> needs to be between 0 and 85.3333 in. I was able to get around this by
> opening the RDL file in notepad and changing the width values manually.
>
> But my questions is, how was the developer able to set the width >
> 85.3333 if it was not allowed?
>

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.

Maximum Length of Report Reached in Report Designer- Bug?

We have reached the maximum length that Report Designer allows - 180 inches.
The problem is that we need to make the report longer. Also - it appears that
the maximum size for a rectangle is 60 inches - this also is too small. Does
anyone know how to report these items to Microsoft Reporting Services
Development as an enhancement request / defect?According to the MS webinar, the page problem has been fixed. The
webinar info has been posted to the WIKI:
http://www.reportingservicesfaq.com/ow.asp?SP2ForRS%3F
jstocker101 wrote:
> We have reached the maximum length that Report Designer allows - 180 inches.
> The problem is that we need to make the report longer. Also - it appears that
> the maximum size for a rectangle is 60 inches - this also is too small. Does
> anyone know how to report these items to Microsoft Reporting Services
> Development as an enhancement request / defect?|||You might be refering to 883501 but that is a different bug. The
details of that bug are related to an error message you get when you
export to Excel. Here is that article:
http://support.microsoft.com/kb/883501
But the problem we are having would not be fixed by Reporting Services
Service Pack 2. Again, the Report Designer tool does not allow you to
create a report larger than 180 inches, and rectangles are limited to
inches. After reviewing the bugs fixed in Reporting Services SP2, none
of the fixes address this issue.
This is a major problem because you cannot create a large report in
Reporting Services!!
Jerry wrote:
> According to the MS webinar, the page problem has been fixed. The
> webinar info has been posted to the WIKI:
> http://www.reportingservicesfaq.com/ow.asp?SP2ForRS%3F
>
>
> jstocker101 wrote:
> > We have reached the maximum length that Report Designer allows -
180 inches.
> > The problem is that we need to make the report longer. Also - it
appears that
> > the maximum size for a rectangle is 60 inches - this also is too
small. Does
> > anyone know how to report these items to Microsoft Reporting
Services
> > Development as an enhancement request / defect?|||In SP2, the maximum height or width for any object is 160 inches. I'm
interested in the scenario that requires such a long report. Can you design
your report as subreports and combine the subreports together in one large
report?
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
<jstocker@.gmail.com> wrote in message
news:1109014748.413769.319290@.f14g2000cwb.googlegroups.com...
> You might be refering to 883501 but that is a different bug. The
> details of that bug are related to an error message you get when you
> export to Excel. Here is that article:
> http://support.microsoft.com/kb/883501
> But the problem we are having would not be fixed by Reporting Services
> Service Pack 2. Again, the Report Designer tool does not allow you to
> create a report larger than 180 inches, and rectangles are limited to
> inches. After reviewing the bugs fixed in Reporting Services SP2, none
> of the fixes address this issue.
> This is a major problem because you cannot create a large report in
> Reporting Services!!
>
> Jerry wrote:
> > According to the MS webinar, the page problem has been fixed. The
> > webinar info has been posted to the WIKI:
> >
> > http://www.reportingservicesfaq.com/ow.asp?SP2ForRS%3F
> >
> >
> >
> >
> > jstocker101 wrote:
> > > We have reached the maximum length that Report Designer allows -
> 180 inches.
> > > The problem is that we need to make the report longer. Also - it
> appears that
> > > the maximum size for a rectangle is 60 inches - this also is too
> small. Does
> > > anyone know how to report these items to Microsoft Reporting
> Services
> > > Development as an enhancement request / defect?
>|||We require one long report because when we export to PDF, we need the
report to display each section as a bookmark to PDF and subreports do
not exhibit this appearance after conversion to PDF. In other words,
create a rectangle in report designer, then export to pdf and you will
notice that the rectangle will appear as a navigation tab on the left
within Acrobat reader. We have reached the limit of 160 inches and we
need to add more tabs to the report.
Regardless of whether the workaround you suggest is valid, the point is
that there should be no limit to the length of a report. That should be
up to the developer.
Albert Yen [MSFT] wrote:
> In SP2, the maximum height or width for any object is 160 inches.
I'm
> interested in the scenario that requires such a long report. Can you
design
> your report as subreports and combine the subreports together in one
large
> report?
> --
> Albert Yen
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> <jstocker@.gmail.com> wrote in message
> news:1109014748.413769.319290@.f14g2000cwb.googlegroups.com...
> > You might be refering to 883501 but that is a different bug. The
> > details of that bug are related to an error message you get when
you
> > export to Excel. Here is that article:
> > http://support.microsoft.com/kb/883501
> >
> > But the problem we are having would not be fixed by Reporting
Services
> > Service Pack 2. Again, the Report Designer tool does not allow you
to
> > create a report larger than 180 inches, and rectangles are limited
to
> > inches. After reviewing the bugs fixed in Reporting Services SP2,
none
> > of the fixes address this issue.
> >
> > This is a major problem because you cannot create a large report in
> > Reporting Services!!
> >
> >
> >
> > Jerry wrote:
> > > According to the MS webinar, the page problem has been fixed. The
> > > webinar info has been posted to the WIKI:
> > >
> > > http://www.reportingservicesfaq.com/ow.asp?SP2ForRS%3F
> > >
> > >
> > >
> > >
> > > jstocker101 wrote:
> > > > We have reached the maximum length that Report Designer allows
-
> > 180 inches.
> > > > The problem is that we need to make the report longer. Also -
it
> > appears that
> > > > the maximum size for a rectangle is 60 inches - this also is
too
> > small. Does
> > > > anyone know how to report these items to Microsoft Reporting
> > Services
> > > > Development as an enhancement request / defect?
> >|||I have the exact same problem. Did you solve this problem - and how did you solve it
From http://66.102.9.104/search?q=cache:RcuHA1_q0zkJ:www.developmentnow.com/g/115_2005_1_0_0_455194/Maximum-Length-of-Report-Reached-in-Report-Designer-Bug.htm+"reporting+services"+"maximum+height"&hl=da&ct=clnk&cd=7&gl=d
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Maximum date calculation for all records

For Crystal Reports version 8.5, I need a report for last year's amounts and this year's amounts. My raw data looks like: fund-type, fund-id, customer-id, check amount, check date, last year's beginning date, last year's ending date, this year's beginning date, and this year's ending date. The beginning and ending dates are subject to change. Also, out of the 2,000 records in the raw data, about 5 of the records have the beginning and ending dates attached. I have used the summary calculation of Maximum to find the beginning and ending dates. My problem is that I cannot use the Maximum function in the formula fields to determine if a check is for last year or this year. I also need totals for a customer's checks (last year and this year), fund-id amounts (this year and last year), and fund-type (last year and this year). When I try to create running-totals, I receive the error message that the summary/running totals cannot be created. Is there a way to create this report?
Thank you for any and all help and advice,
TracySHCCreate a formula having the code

If year(datecol)<year(currentdate) then
1
else
2
Place it in details section
Now group the report by this formula and use summary accordingly