This question is locked. New answers and comments are not allowed.
My problem: After a fresh install of TeamPulse, new database (SQL 2008 R2), fresh IIS7, I get the following error in the Application Log:
Exception information:
Exception type: HttpException
Exception message: No http handler was found for request type 'GET'
at System.Web.HttpApplication.MapIntegratedHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig, Boolean convertNativeStaticFileModule)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
I also see multiple instances of this error in the web-log.txt file, in
2012-10-30 16:51:14,598 [5] ERROR TeamPulse.Shared.Logger - - Unhandled Exception. System.Web.HttpException (0x80004005): Error executing child request for ~/WebLogin/Login.aspx. ---> System.Web.HttpException (0x80004005): No http handler was found for request type 'GET'
at System.Web.HttpApplication.MapIntegratedHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig, Boolean convertNativeStaticFileModule)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at System.Web.HttpServerUtility.Transfer(String path)
at TeamPulse.Client.Host.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I have tried this in multiple environments, with different versions of TeamPulse (2012 R2 and 2012 R5 SP1). The only commonality has been Windows 2008 R2, A/D domain logins and a SQL 2008 R2 database. I get the same problem each time. I have other ASP.NET MVC and .NET 4.0 sites running on the same boxes. I have re-run the aspnet_regiis.exe -i command. The domain user is a domain admin, and has batch logon rights. There must be something obvious I am missing.
Any thoughts?
Exception information:
Exception type: HttpException
Exception message: No http handler was found for request type 'GET'
at System.Web.HttpApplication.MapIntegratedHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig, Boolean convertNativeStaticFileModule)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
2012-10-30 16:51:14,598 [5] ERROR TeamPulse.Shared.Logger - - Unhandled Exception. System.Web.HttpException (0x80004005): Error executing child request for ~/WebLogin/Login.aspx. ---> System.Web.HttpException (0x80004005): No http handler was found for request type 'GET'
at System.Web.HttpApplication.MapIntegratedHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig, Boolean convertNativeStaticFileModule)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
at System.Web.HttpServerUtility.Execute(String path, TextWriter writer, Boolean preserveForm)
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at System.Web.HttpServerUtility.Transfer(String path)
at TeamPulse.Client.Host.Global.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I have tried this in multiple environments, with different versions of TeamPulse (2012 R2 and 2012 R5 SP1). The only commonality has been Windows 2008 R2, A/D domain logins and a SQL 2008 R2 database. I get the same problem each time. I have other ASP.NET MVC and .NET 4.0 sites running on the same boxes. I have re-run the aspnet_regiis.exe -i command. The domain user is a domain admin, and has batch logon rights. There must be something obvious I am missing.
Any thoughts?