The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

    The Report Viewer Web Control HTTP Handler has not been registered in the application's   web.config file.  Add  to the system.web/httpHandlers section of the web.config file  

This error is coming . I have already mentioned this line in http handler but still getting this error

my html page markup is as follow

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

Web config assemblies section is as follows :

Answer by Mayank Pathak for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

Could you check your web.config for handlers registered or not for ReportViewer. its should be like this

Handler

Also check assembly section in your web.config for ReportViewer, it should be like below.

Answer by NothingsImpossible for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

I was having the very same problem. What happened was I put the Report loading routine on Page_Load, and didn't wrap it in if (!IsPostBack). The ReportViewer makes a POST to the page, and that was triggering Page_Load and reloading the report, somehow messing it up. After putting everything inside if (!IsPostBack), it worked like a charm.

Answer by dellyjm for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

This issue arose for me after I changed the parameter of the stored procedure my query was calling without refreshing the dataset in the SSRS designer, so you could try this.

Answer by Sean for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

The issue also went away for me when I changed the app pool from Integrated to Classic.

Answer by Martin Meeser for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

The last two days I have had the same issue. This is not really an answer to the original question - just some additional information for those having the same problem.

The application I had the problem with has been developed in 2005 and is under development still.

So it has been ported from VS 2005 to VS 2008 to VS 2010 and lately to VS 2013. It seems this is when the error happened. Somewhere in between the .NET framework has switched from .NET 3.5 to .NET 4.

I think (I did not verify) that with .NET 4 the report viewer *.dlls come as system libraries. Anyway this showed my GAC to me:

Only the first one, version 8, has been manually installed by myself (with the Reporting Viewer 2005 redistributable binary).

So in VS 2013, Resharper is thinking of version 11 and automatically changes those lines in web.config

So long story short: It seems - at least in my case - this error points to a version conflict with the libraries used with visual studio and those used an runtime. The error given from Microsoft is a little bit misleading.

Answer by Gabriel Simas for The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file

I have not changed anything in the app pool just added this line:

Fatal error: Call to a member function getElementsByTagName() on a non-object in D:\XAMPP INSTALLASTION\xampp\htdocs\endunpratama9i\www-stackoverflow-info-proses.php on line 72