ReportViewer Causing Major Problems

microsoft.public.dotnet.framework.aspnet.webcontrols

5 Dec 2006 10:41 PM

Saubz

Hello, I have a web app that I need to add the ReportViewer control to. The
problem is when I add the control to my Default.aspx page and try to publish
my application to IIS, I get the following error:

The file '/LoanPricing/login.aspx' has not been pre-compiled, and cannot be
requested.

This login.aspx page only contains a standard Login control. The problem is
not on this page. I can resolve the problem by removing the ReportViewer
control from my Default.aspx and also removing all references to the
ReportViewer control, namely these following references:

From Default.aspx
<%@ Register Assembly="Microsoft.ReportViewer.WebForms, Version=8.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"
    Namespace="Microsoft.Reporting.WebForms" TagPrefix="rsweb" %>

From web.config
<buildProviders>
        <add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider,
Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" />
</buildProviders>

And

<httpHandlers>
      <add path="Reserved.ReportViewerWebControl.axd" verb="*"
type="Microsoft.Reporting.WebForms.HttpHandler,
Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
</httpHandlers>

The application works just fine while I'm debugging on my local machine, but
gives me the errors when I publish to my remote IIS.

Why does this ReportViewer cause errors? How can I fix this?

Thanks,
Matt

6 Dec 2006 8:51 AM

Walter Wang [MSFT]

Hi Matt,

I've done some test on my side and didn't reproduce the issue on my side.
I'm afraid it's an environment specific issue.

If you remove the Login control from login.aspx, does the issue go away? If
you publish it to another IIS server, does it still report the error? If it
can be easily reproduced on your side, would you please send me the web
site so that I can test it on my side?

Sincerely,
Walter Wang (waw***@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

6 Dec 2006 2:46 PM

Saubz

Well after some research, I found the solution to the problem.

On my remote IIS Server I had to install this program that ships with Visual
Studio:

C:\Program Files\Microsoft Visual Studio
8\SDK\v2.0\BootStrapper\Packages\ReportViewer\ReportViewer.exe

After I installed that program, I had to give full access to 'NETWORK
SERVICE' to my c:\windows\temp directory. After that, it all worked great.

I don't know why this is the case, but there it is. I know lots of other
people are having this same problem, so I hope this helps.

Show quoteHide quote

"Walter Wang [MSFT]" wrote:

> Hi Matt,
>
> I've done some test on my side and didn't reproduce the issue on my side.
> I'm afraid it's an environment specific issue.
>
> If you remove the Login control from login.aspx, does the issue go away? If
> you publish it to another IIS server, does it still report the error? If it
> can be easily reproduced on your side, would you please send me the web
> site so that I can test it on my side?
>
>
> Sincerely,
> Walter Wang (waw***@online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
>
> ==================================================
> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications. If you are using Outlook Express, please make sure you clear the
> check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
> promptly.
>
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>

7 Dec 2006 9:52 AM

Walter Wang [MSFT]

Hi Matt,

Thank you for your update and sharing your findings with the community.

You're right that for a product environment, you need to execute
reportviewer.exe after installed .NET 2.0 framework:

#Deploying Reports and ReportViewer Controls
http://msdn2.microsoft.com/en-us/library/ms251723(VS.80).aspx

I'm sorry that I didn't mention that in my previous reply, I was using a
server with Visual Studio 2005 installed, which means the controls are
already installed.

As for the temporary directory setting, I think you might be using a custom
setting of ReportViewerTemporaryStorage:

#Web.config Settings for ReportViewer
http://msdn2.microsoft.com/en-us/library/ms251661(VS.80).aspx
You can set the ReportViewerTemporaryStorage attribute for objects that
implement ITemporaryStorage interface. You can add it if you want to store
the temporary streams that are sent by the report server rather than hold
them in memory.

Regards,
Walter Wang (waw***@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

11 Dec 2006 2:16 PM

Saubz

Walter,

Thank you for your help with this issue. Everytying works great now.

I don't think I'm using any custom settings for my ReportViewer, though. I
only have this httpHandler in my web.config

<add path="Reserved.ReportViewerWebControl.axd" verb="*"
type="Microsoft.Reporting.WebForms.HttpHandler,
Microsoft.ReportViewer.WebForms, Version=8.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>

It might be some other issue that was giving me the temp problems because
before, when I published my site, I could not check "Allow this precompiled
site to become updatable". Now that I opened up the temp folder, I can use
that feature as well.

Show quoteHide quote

"Walter Wang [MSFT]" wrote:

> Hi Matt,
>
> Thank you for your update and sharing your findings with the community.
>
> You're right that for a product environment, you need to execute
> reportviewer.exe after installed .NET 2.0 framework:
>
> #Deploying Reports and ReportViewer Controls
> http://msdn2.microsoft.com/en-us/library/ms251723(VS.80).aspx
>
> I'm sorry that I didn't mention that in my previous reply, I was using a
> server with Visual Studio 2005 installed, which means the controls are
> already installed.
>
> As for the temporary directory setting, I think you might be using a custom
> setting of ReportViewerTemporaryStorage:
>
> #Web.config Settings for ReportViewer
> http://msdn2.microsoft.com/en-us/library/ms251661(VS.80).aspx
> You can set the ReportViewerTemporaryStorage attribute for objects that
> implement ITemporaryStorage interface. You can add it if you want to store
> the temporary streams that are sent by the report server rather than hold
> them in memory.
>
>
>
>
> Regards,
> Walter Wang (waw***@online.microsoft.com, remove 'online.')
> Microsoft Online Community Support
>
> ==================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>