I was recently working on a reporting web application that uses the Report Viewer ( ReportViewer ) control that ships with SQL Server Reporting Services (SSRS). The Report Viewer control was rendering perfectly when I was developing using Visual Studio 2008. The trouble started when I published the web application to an IIS 7.0 server. The Toolbar was completely broken and showed up something like this.
<rsweb:ReportViewer AsyncRendering="false" ID="reportViewer" Width="100%" Height="100%" runat="server" SizeToReportContent="True" > </rsweb:ReportViewer>
GET /Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=9.0.30729.1&Name=Microsoft.Reporting.WebForms.Icons.NextPage.gif HTTP/1.1
GET /Reserved.ReportViewerWebControl.axd?OpType=Resource&Version=9.0.30729.1&Name=Microsoft.Reporting.WebForms.Icons.LastPage.gif HTTP/1.1
When you use the Report Viewer Control Visual Studio edits your web.config to map a Http Handler to respond to these requests.
<add path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=22.214.171.124, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" validate="false"/>
The above entry tells ASP.NET that whenever a call is made to ReportViewerWebControl.axd use the Microsoft.Reporting.WebForms.HttpHandler assembly to execute it.
This mapping is very important because if you remove it the web server will return a 404 “File Not Found” error code because the ReportViewerWebControl.axd does not exist physically on the server.
Strangely when I checked the IIS 7.0 logs for the broken scenario I found that all requests for ReportViewerWebControl.axd had failed with a 404.
With IIS 7.0 there was an architectural change. There were changes to the web.config structure as well. The <httpHandlers> section that was under the <system.web> has now moved to <handlers> under <system.webServer>
Visual Studio had edited the web.config based on the IIS 6.0 model and had made an entry for the Http Handler under the <httpHandler> section. With IIS 7.0 this section is no longer read. So we need to make the proper entries for the Http Handler that handles the calls to ReportViewerWebControl.axd
<add name="ReportViewerWebControl" path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/>
IIS 7.0 will now understand that whenever a call is made to ReportViewerWebControl.axd it needs to route it to the Http Handler Microsoft.Reporting.WebForms.HttpHandler
I miss the days when MS would bend over backwards for backwards compatibility - much less not making stupid breaking naming changes like this.
Create empty file in notepad
and save it under the name
into folder containing Web.config.
Your blog cuts off a large portion of the code can you please post an entry with the full code for the handlers?
Mike I have added scroll bars around the code block. Hope it helps.
Thanks. I tried to drop that into my code but no fix. I know it applied to IIS 7.0 & I am running IIS 5.1 on XPSP2 with VS 2K8 and I am still getting the same thing. Thanks for the scroll bars guess I will be back to the drawing board till I find a fix... If you have any ideas as to why I am getting the same error but on a different platform please feel free to shoot me a message trigeek512 at gmail dot com! Thanks & keep up the good work.
I was recently working on a reporting web application that uses the Report Viewer ( ReportViewer ) control
Thank very much. reslove my problem.
Thank you. This solved my problem.
Thank you. Solved my problem :)
I could reach through my monitor and kiss you! Thank you! Thank you! I've been scratching my head all day on this one. The picture of the broken tool bar at the top was golden. I knew when I saw it that this page would be the exact fix I needed.
Thank you thank you thank you!!!!!!! I have been practically banging my head against the desk over this problem. Your solution was EXACTLY what it took to fix it for me also!
Hi.. I was experiencing the same problem of the missing icons and report not rendering with ReportViewer 8.0 connecting to SSRS 2008 and IIS7. The above fix didn't solve the problem for me unfortunately. Does anyone think that the versions are incompatible...?
Thanks in advance!
Fixed!! It was the missing 'name' attribute and offending 'validate' attributes in my entry that was causing the issue.
So in conclusion, ReportViewer 8.0 does work with SSRS 2008 effortlessly!
Great post .. many thanks!
What a beauty. It just worked adding the comments.
Thanks so much! You saved me hours of troubleshooting!