ReportViewer on IIS 7 Windows 2008 not rendering, usual fix not working
I moved from Katmai and Windows 2003, to SQL 2008 RTM and Server 2008 with IIS 7. My ReportViewer based .Net application runs but reportviewer control icons do not display and the report does not render. Same reports render in ReportManager and Visual Studio. I tried this common fix which did not work: Open Internet Information Services (IIS) Manager and select your Web application. Under IIS area, double-click on Handler Mappings icon. At the Action pane on your right, click on Add Managed Handler. At the Add Managed Handler dialog, enter the following:Request path: Reserved.ReportViewerWebControl.axdType: Microsoft.Reporting.WebForms.HttpHandlerName: Reserved-ReportViewerWebControl-axd Click OK. http://forums.msdn.microsoft.com/en/vsreportcontrols/thread/4f75cfdb-805c-47bc-bd2c-07f716ed0e15/My Web.Config is below. Any insights appreciated.<?xml version="1.0"?><configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> <connectionStrings/> <system.web><!--<compilation debug="false" strict="false" explicit="true">--> <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> <customErrors mode="Off"/> <authentication mode="Forms"><forms name="AuthCookie" timeout="60"><credentials passwordFormat="Clear"><user name="foo" password="bar" /></credentials></forms></authentication> <compilation> <buildProviders> <add extension=".rdlc" type="Microsoft.Reporting.RdlBuildProvider, Microsoft.ReportViewer.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </buildProviders> </compilation> <authorization> <deny users="?" /></authorization><sessionState mode="InProc"/><pages> <namespaces> <clear/> <add namespace="System"/> <add namespace="System.Collections"/> <add namespace="System.Collections.Specialized"/> <add namespace="System.Configuration"/> <add namespace="System.Text"/> <add namespace="System.Text.RegularExpressions"/> <add namespace="System.Web"/> <add namespace="System.Web.Caching"/> <add namespace="System.Web.SessionState"/> <add namespace="System.Web.Security"/> <add namespace="System.Web.Profile"/> <add namespace="System.Web.UI"/> <add namespace="System.Web.UI.WebControls"/> <add namespace="System.Web.UI.WebControls.WebParts"/> <add namespace="System.Web.UI.HtmlControls"/> </namespaces></pages> </system.web><system.webServer><validation validateIntegratedModeConfiguration="false" /> <handlers> <add name="Reserved-ReportViewerWebControl-axd" path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler" resourceType="Unspecified" /> </handlers></system.webServer> </configuration>
August 28th, 2008 9:55am

Are you getting an error message or is nothing showing up?? You might read this: http://coderrob.com/blog/post/2007/12/Deploying-client-side-report-definition-files--or-RDLC-reports.aspx be sure you get the 2008 redist though if you download it.
Free Windows Admin Tool Kit Click here and download it now
August 28th, 2008 7:02pm

This looks promising, I will give it a shot and report back later today. Thanks for taking the time.
August 28th, 2008 9:46pm

This did not fix the problem. I am suspicious of IIS 7 configuration, vis-a-vis the application pool. However I do not see anything obviously wrong. I will keep trying, as I have no experience with IIS7.
Free Windows Admin Tool Kit Click here and download it now
August 29th, 2008 6:37am

To answer my own question with what I discovered: There were a number of problems with the Transition to IIS 7. Considerable debugging was required. FIRST ISSUE RESOLVED: Directory permissions for the IIS 7 application pool identity (the default was Network Service) needed to be added so that the IIS application pool could have access to the physical path of the Website directory. SECOND ISSUSE RESOLVED:A line needed to be added to the ASP.Net application web.config file.Child of <configuration>After <system.web> Added:<system.webServer><validation validateIntegratedModeConfiguration="false" /></system.webServer> THIRD ISSUE RESOLVEDThe Default App pool upon install has .Net Framework 2.0 as default. This was fine.The Default App pool setting for Managed Pipeline Mode needed to be changed from 'Integrated' (default) to 'Classic', this was the quick fix to keep my app running as it had on IIS 6.
August 30th, 2008 12:46am

I too had this issue with IIS7 on 2008 Windows Web Server Edition. It cost me dearly,deploying anASP application upgradebased onSQL Reporting Services. I had to give up. Until, months later I accidently discovered that an application migrated from another server was able to use reporting services after I implemented httpHandlers forthereport viewer componet in IIS 7.0. What I accidently discovered was that if the session of the asp application was cookieless. This somehow let the report viewer control work. <system.webServer> <handlers> <add name="Reserved-ReportViewerWebControl-axd" path="Reserved.ReportViewerWebControl.axd" verb="*" type="Microsoft.Reporting.WebForms.HttpHandler" resourceType="Unspecified" /> </handlers></system.webServer> This was less than ideal because it rewrites the URL, it intefars with site analitics tracking and looks ugly. Later I accidently discover that a site was working with cookies for session state on one of my sites. After a couple more hours of my life spent on this issue, I determined it was because the application was seetup within a webserver and not the root of the web server itself. Sloution 1. Setup new httpHandlers section under web config 2. Turn cookieless to true under sessionstate 3. Or, setup you application under an existing web server Notice I never had to validateIntegratedModeConfiguration=False. I dont know much about this. It just never came up as an issue for me. Honestly, I hate dealing with these server issues. Anyway, I dont claim to be an expert on this and really would love to hear from someone who can explain why.I don't really want to have to run the application in another web server. I am not sure of the root issue here or wht it behaves this way.Symptoms: report servies works on 6.0 not IIS 7. HTTTP access error on users browser reportviewer component . Componet also prompts for autentication, user and password. I never had to add any permissions or anything to solve this.
Free Windows Admin Tool Kit Click here and download it now
November 22nd, 2009 11:30pm

The Default App pool setting for Managed Pipeline Mode needed to be changed from 'Integrated' (default) to 'Classic'. Nothing else is needed.
January 5th, 2010 7:15pm

Mubashar,You are a star, thanks for this advice. Works great.Jim Davis
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2010 5:37am

i have tried every single suggestion on this entire thread and STILL get the error: The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. Add <add verb="*" path="Reserved.ReportViewerWebControl.axd" type = "Microsoft.Reporting.WebForms.HttpHandler, Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> to the system.web/httpHandlers section of the web.config file. How unbelievably frustrating. It's really hard to make a good case to your supervisors to go with Microsoft reporting over Crystal when you spend days trying to get it to work and still have nothing to show. Any new info would be appreciated since none of these have worked for me.
May 28th, 2010 9:51pm

The Default App pool setting for Managed Pipeline Mode needed to be changed from 'Integrated' (default) to 'Classic'. Nothing else is needed. Thank you very much - that worked perfectly for me. Gary.
Free Windows Admin Tool Kit Click here and download it now
October 12th, 2010 11:33am

It appears that ReportViewer 8.0 (2005) and 9.0 (2008) must run under Classic mode in IIS7. ReportViewer 10.0 (2010) does work under Integrated mode. http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/b2ef1892-943d-4f83-981b-6e9d7f2bac4e http://msdn.microsoft.com/en-us/library/ms251661.aspx (last section on httpHandlers) http://www.microsoft.com/downloads/en/details.aspx?FamilyID=a941c6b2-64dd-4d03-9ca7-4017a0d164fd&displaylang=en
January 26th, 2011 8:24am

This worked perfectly for me too. I spent a whole day trying various different settings and lots of debugging with no joy. Stumbled across this thread, change the Managed Pipeline Mode and report viewer control was back with us! Thank you. Chris.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2011 3:45am

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

Other recent topics Other recent topics