Forum Widgets
Latest Discussions
How to fix Error System.Web.HttpApplication does not implement IHttpModule in IIS
Hi, I need some help with error "Error System.Web.HttpApplication does not implement IHttpModule" with some steps for diagnose cause this error. Note: MY_SERVER has a single web site called "SitioNuevoVacio2" Context I have a web site called "SitioNuevoVacio2" this contains a single html file called "index.html" with following source code... <html> <body> -- empty web site -- </body> </html> when I browse "SitioNuevoVacio2", I get these error messages: " Server Error in '/' Application. ________________________________________ System.Web.HttpApplication does not implement IHttpModule. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Configuration.ConfigurationErrorsException: System.Web.HttpApplication does not implement IHttpModule. Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [ConfigurationErrorsException: System.Web.HttpApplication does not implement IHttpModule.] System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) +11874417 System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +221 System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1103 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +122 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +173 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +255 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +347 [HttpException (0x80004005): System.Web.HttpApplication does not implement IHttpModule.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +552 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +122 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +732 ________________________________________ Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.9195.0 " And Event viewer has this warning: " Event code: 3008 Event message: A configuration error has occurred. Event time: 9/10/2024 8:56:20 a. m. Event time (UTC): 9/10/2024 1:56:20 p. m. Event ID: 5bffbb78122e470a85ffaa557e38532d Event sequence: 1 Event occurrence: 1 Event detail code: 0 Application information: Application domain: /LM/W3SVC/3/ROOT-2-133729557801407411 Trust level: Full Application Virtual Path: / Application Path: C:\inetpub\wwwroot\SitioNuevoVacio2\ Machine name: MY_SERVER Process information: Process ID: 9424 Process name: w3wp.exe Account name: IIS APPPOOL\DefaultAppPool Exception information: Exception type: ConfigurationErrorsException Exception message: System.Web.HttpApplication does not implement IHttpModule. at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) Request information: Request URL: http://localhost:8085/ Request path: / User host address: ::1 User: Is authenticated: False Authentication Type: Thread account name: MY_SERVER\SomeUser Thread information: Thread ID: 12 Thread account name: MY_SERVER\SomeUser Is impersonating: False Stack trace: at System.Web.Configuration.Common.ModulesEntry..ctor(String name, String typeName, String propertyName, ConfigurationElement configElement) at System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) at System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) " I searched in the web and some post suggest check your source code in these files: - web.config - global.asax and find any reference to custom HttpModule, but "SitioNuevoVacio2" only has a single page. I don't know what to do, any suggestions? Technical Specs - SO: windows server 2022 standard 21H2 - IIS: Version 10.0.20438.1 - .NET Framework Version:4.0.30319 - ASP.NET Version:4.8.9195.0 TRY 1. List of 12 Handlers manually created... 1. PageHandlerFactory-ISAPI-4.0_32bit • Request path: *.aspx • Type: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Name: PageHandlerFactory-ISAPI-4.0_32bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 2. PageHandlerFactory-ISAPI-4.0_64bit • Request path: *.aspx • Type: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Name: PageHandlerFactory-ISAPI-4.0_64bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 3. PageHandlerFactory-Integrated-4.0 • Request path: *.aspx • Type: System.Web.UI.PageHandlerFactory • Name: PageHandlerFactory-Integrated-4.0 • Module: ManagedPipelineHandler • Entry Type: Local 4. SimpleHandlerFactory-ISAPI-4.0_32bit • Request path: *.ashx • Type: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Name: SimpleHandlerFactory-ISAPI-4.0_32bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 5. SimpleHandlerFactory-ISAPI-4.0_64bit • Request path: *.ashx • Type: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Name: SimpleHandlerFactory-ISAPI-4.0_64bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 6. SimpleHandlerFactory-Integrated-4.0 • Request path: *.ashx • Type: System.Web.UI.SimpleHandlerFactory • Name: SimpleHandlerFactory-Integrated-4.0 • Module: ManagedPipelineHandler • Entry Type: Local 7. WebServiceHandlerFactory-ISAPI-4.0_32bit • Request path: *.asmx • Type: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Name: WebServiceHandlerFactory-ISAPI-4.0_32bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 8. WebServiceHandlerFactory-ISAPI-4.0_64bit • Request path: *.asmx • Type: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Name: WebServiceHandlerFactory-ISAPI-4.0_64bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 9. WebServiceHandlerFactory-Integrated-4.0 • Request path: *.asmx • Type: System.Web.Services.Protocols.WebServiceHandlerFactory • Name: WebServiceHandlerFactory-Integrated-4.0 • Module: ManagedPipelineHandler • Entry Type: Local 10. ScriptHandlerFactory-ISAPI-4.0_32bit • Request path: *.axd • Type: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Name: ScriptHandlerFactory-ISAPI-4.0_32bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 11. ScriptHandlerFactory-ISAPI-4.0_64bit • Request path: *.axd • Type: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Name: ScriptHandlerFactory-ISAPI-4.0_64bit • Module: IsapiModule • Script Processor: C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319\\aspnet_isapi.dll • Entry Type: Local 12. ScriptHandlerFactory-Integrated-4.0 • Request path: *.axd • Type: System.Web.Handlers.ScriptHandlerFactory • Name: ScriptHandlerFactory-Integrated-4.0 • Module: ManagedPipelineHandler • Entry Type: Local 2. Check, download, install, update and reboot last windows updates. 3. Compare Handlers and Modules between IIS developer server with MY_SERVER note: IIS developer server works fine when I publish "SitioNuevoVacio2" EXPECT After made those verifications and changes IIS works fine and see index.html "SitioNuevoVacio2"SolvedxjavierbOct 09, 2024Copper Contributor427Views0likes8Comments
403 - Forbidden while posting the request to WCF hosted on IIS
I have an ASP.NET web application that uses a WCF service to interact with the database and handle business logic. Under normal load, everything functions as expected. However, when the load increases, the WCF service returns a 403 - Request Forbidden error. I attempted to capture a dump using DebugDiag, but it hasn't provided any useful information. While there are many guides available on capturing dumps, none seem applicable to this particular issue.SolvedDotnetAgentOct 05, 2024Brass Contributor244Views0likes2Commentsiis website problem after reinstall Windows 10, connection was reset
I posted this problem here back in July. Although I have made significant progress in some related issues this problem continues to be trouble. I have new, more detailed information so I am posting it again. Hope someone can help... 1. The problem: My website is readily accessible over mobile data locally from my smartphone, and also from anywhere in the world according to these online resources: site24x7.com and uptimia.com But I cannot connect to the website: [i] using a Browser, directly from my home computer which hosts the website, or [ii] using LocalHost or from any local device using my home wifi The result message is... This site can’t be reached mickwebsite.com took too long to respond. Try: Checking the connection ERR_CONNECTION_TIMED_OUT Details: Check your Internet connection When I run the Browser with http://localhost it redirects to https, but gives the explanation "Your connection to this site is not secure" and "the connection was reset". I did resolve the issue re: connecting directly from the host computer, by including the IP4 in the "hosts" file. However I think this does not fix the actual problem. I still cannot connect from a local device over wifi. 2. A bit of history: This website had been running problem free for at least a few years with essentially this same setup. Then recently I had a technical problem with my computer that I was unable to solve. I arbitrarily decided to reinstall Windows 10 over the internet from Microsoft. I have had this problem with my website ever since 😞 3. My setup: My website is https://mickwebsite.com I am running IIS on Windows 10 Pro 21H2 with minimum features implemented for a Static website, with support from No-IP, Certify The Web and Lets Encrypt. I have implemented SSL, and also implemented http -> https using URL Rewrite. Under Edit Site|Bindings|443 I have a current, valid certificate installed. I have worked through all of the options in my Technicolor XB7 router and I believe that it is set up correctly. I have port forwarded 80 and 443. Unlike my previous model this router does not support Dynamic DNS so I am using No-ip's DUC for this service. In Windows Defender Firewall I have set both IPV4 and IPV6 to default or medium security. I do not recall making any other Firewall changes. I have reviewed my setup with each of No-IP, Certify The Web and Lets Encrypt with the appropriate support people. 4. What I have done so far: First, I wanted to be certain that my IIS install and features choice were correct and have not been messed up somehow. I decided to renew my install of IIS using the minimum set of features for a static website. I followed these steps... 1. Remove all [both] websites, the default and my own, from inetmgr. 2. Delete the two web.config files and the inetpub folder. 3. Uninstall IIS using control panel "turn features off"; reboot computer. 4. Reinstall IIS adding in only the HTTP Redirection feature; rebooted computer. 5. The default web site did not reappear [probably because I had deleted inetpub] so I recreated it following instructions found on StackOverflow. 6. I installed the URL Rewrite feature as I had used it successfully for several years. The HTTP Redirection feature and HSTS are there if I may need them. I am not currently useing them. 7. Disabled static compression. Recommended by an MS Learn post; this is needed for URL Rewrite to function, a Known Issue. 8. Edited permissions for the website folder to ensure IUSR is there with Read permission only 9. Created binding for port 80. 10. SSL Settings feature: left Require SSL unchecked. Checked Accept for client certificates 11. URL Rewrite feature: set this up following a blog post 12. I tested the Default Website via Localhost: This site cannot be reached Your connection is not secure 13. Tested Default Website over mobile data: Success! 14. Checked http -> https over mobile data: Success! So the problem exists for the Default website. I can connect over mobile data but not over wifi/localhost I installed my website into inetmgr, setting up Features etc as above except created bindings for both ports 80 and 443. View shows the certificate is valid until 2023-01-11. The results are the same as for the default website. So the problem is not in my website code or setup 🙂 4. My question: So it appears to me that the problem is not caused by any of my router setup which I thoroughly reviewed, or by my IIS setup which I thoroughly reset, or by my website code which behaves same as the default website. So I am wondering... what option, setting, etc in Windows 10 might be causing this problem behavior? What did reinstalling Windows 10 from Microsoft over the internet change? Or is it something else entirely? Any help is appreciated, MickSolvedFeMickNov 13, 2022Copper Contributor1.3KViews0likes2Comments
X-Forwarded-For header is being removed somwhere between my IIS reverse-proxy and backend IIS setup
Hi, I've the following web hosting setup: 1. Users facing Windows Server 2016 Server (v1607 - OS Build 1493.2791) with IIS v10.0.14393.0 and Application request routing 3.0 acting as an IIS reverse-proxy for backoffice server. 2. Backoffice Windows Server 2019 Server (v1809 - OS Build 17763.1817) with IIS v10.0.17763.1 hosting mix of Angular and .Net applications. When ARR on the IIS reverse-proxy is configured to preserve client IP in X-Forwarded-For header, it is not added to the incoming requests on the backoffice server. But when I change the header name to something different (like X-Forwarded-For2 for an instance) it suddenly is added to the incoming requests and the backoffice server can see it. When I change the name back to the default value it disappears again from the incoming requests on the backoffice server. It seems like there is something that removes the header if its named X-Forwarded-For. Unfortunately I can't use a different header name because of the third party software on the backoffice server is expecting the standard header name - X-Forwarded-For. I have used Postman to simulate the request and manually added X-Forwarded-For and X-Forwarded-For2 headers with mocked IP addresses. I've sent the requests from Postman directly to the backoffice IIS server and X-Forwarded-For2 header value only is present in backoffice IIS server logs.The log column for X-Forwarded-For header value is dashed out. Is there a configuration option controlling this unexpected behavior I can change to my advantage? (Edit) I've checked IIS reverse-proxy log also configured to log X-Forwarded-For values and it is filled with my IP address before reaching backoffice IIS server. So this is a solid proof that "something" is clearing X-Forwarded-For on the backoffice IIS server 😕SolvedRobertN_42Jul 28, 2022Copper Contributor2.4KViews0likes2Comments
Use "Windows Process Activation Service" without IIS?
I have a vendor that is requesting the NET.Tcp listener adapter to be installed on SQL servers to allow their product to monitor them. After installing that service, and all required dependencies, using Server Manager (in the .NET 4.7 section), it will not start because it has a dependency on the "Windows Process Activation Service" (WPAS) which itself will not start - it generates an invalid index error when I try to start WPAS. I don't know anything about WPAS, this is the first I have encounter any mention of this service and I am not an IIS expert. However, from what I can tell, WPAS seems to be related or used in conjunction with IIS, but it did not tell me that I needed IIS installed when I installed NET.Tcp listener. So I don't know if my assumption is correct. Could someone with IIS experience let me know if WPAS does indeed require IIS to start? At least if I know that, then I can continue my troubleshooting the problem without having to be concerned with IIS missing from the equation. Thanks NKSolvedNJKWorkMar 01, 2022Copper Contributor1.1KViews0likes1Comment
Resources
Tags
- IIS21 Topics
- http4 Topics
- https3 Topics
- IIS Windows Server 20222 Topics
- roadmap2 Topics
- url rewrite2 Topics
- exchange2 Topics
- url authorization rules2 Topics
- Release1 Topic
- DLL1 Topic
