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 Contributor427Views0likes8CommentsIIS hardening with CIS standards - tools and options
Hello IIS experts. Please suggest on best strategy for hardening on-prem IIS farm to CIS standards. I'm also interested in recurring audit of the results. There is a number of commercial products allowing to scan IIS for CIS Benchmarks. The latest "CIS Benchmark for Microsoft IIS 10" available to download in PDF format free of charge at https://www.cisecurity.org/cis-benchmarks/. However in this instance CIS does not offer "Build kit". Depends on product to be hardened, CIS "build kit" can be set of scripts, GPO policy or similar to allow rapid hardening deployment. Since there is no Official build kit I'm looking for alternatives. Can you please share your experience on this subject? I found few blogs but those are quite old.SerggSep 03, 2021Iron Contributor11KViews0likes6CommentsHow to Host a Rails App on IIS: Seeking a Simple Approach
Hello, I’m having trouble hosting my Rails app on IIS (Windows Server 2019). Unfortunately, I don’t have the option to choose a different server since the app will be hosted on an on-premise server, which also runs other applications on IIS (Windows Server 2019). I’ve read numerous discussions on this topic, and the most common feedback is that “it’s painful.” However, I haven’t been able to find a clear, step-by-step guide or solution. So far, I’ve come across the following options: Hosting with a reverse proxy Hosting with WSL Hosting with Docker However, I’m looking for a more traditional approach to hosting the app, similar to how one would typically host an application in other languages. As a developer with limited experience in server management, I’m not sure where to start. If anyone has any tips, tutorials, or guidance, I would greatly appreciate your help!Lobby1625Sep 25, 2024Copper Contributor493Views0likes5CommentsTemporary error 403 on images
I've been having the following problem for some time now. Some images are repeatedly not displayed on the website (error 403). These are also linked as an image. If I click on the link, they appear without any problems. When I refresh the page with cache turned off, different images are affected. Does anyone have an idea? for instance www.salzlandkreis.de/bildungkultur/ringheiligtum-poemmelte/impressionen http and https same behaviorKlaus_KunathSep 11, 2024Copper Contributor333Views0likes5CommentsIIS issue - apsnetcore.dll not found
Hi, I am working on upgrading a server from 2012 to 2022 (on AWS). I have installed a fresh 2022 instance and have sued webdeploy to copy the entire IIS configuration from the 2012 server to the 2022 server. To try to further bring the server up to date, the 2012 server is running .Net 2.x and on 2022 I have installed .Net 8.x When I launch the 2022 server IIS runs but my websites won't come up - I keep getting a 503 error. When I look in the Event Viewer the error message I see is "apsnetcore.dll not found". I have spent some time trying to identify how to rectify this but so far have not been successful. Could anyone please give me any suggestions to try to find a fix ? TIArpreston845Sep 24, 2024Copper Contributor323Views0likes4CommentsChunked data through IIS
I am trying to chunk data through iis but it is not happning I tried <rewrite> <outboundRules> <!-- <rule name="Remove Content-Length" stopProcessing="false"> <match serverVariable="RESPONSE_Content-Length" pattern=".*" /> <action type="Rewrite" value="0" /> </rule> --> <!-- <rule name="Add Chunked Encoding" patternSyntax="ECMAScript"> <match serverVariable="RESPONSE_Transfer-Encoding" pattern=".*" /> <action type="Rewrite" value="chunked" /> </rule> --> and <rule name="Transfer-Encoding chunked"> <serverVariables> <set name="RESPONSE_Content-Length" value="" /> <set name="RESPONSE_Transfer-Encoding" value="chunked" /> </serverVariables> <action type="CustomResponse" statusCode="200" /> </rule> and <httpProtocol allowKeepAlive="false"> <customHeaders> <!-- <remove name="Content-Length" /> <add name="Transfer-Encoding" value="chunked" /> --> <add name="X-Content-Type-Options" value="nosniff" /> </customHeaders> </httpProtocol> in these cases in response header transfer-encoding is coming as chunked but response body is not comingAbhishek_RajSSep 24, 2024Copper Contributor387Views0likes4CommentsIIS Logs have Incorrect Date Modified
I have a server that is creating daily IIS logs (stored local) with a timestamp in the Date Modified that have the incorrect date for the "current" log. Example: Today is 9-10-2024, the current log is named correctly(u_ex240910.log), has correct information inside, but the Date Modified Timestamp is 9-9-2024 7:00PM. There is also a log file for u_ex240909.log) which has correct information in it as well. I have dozens of IIS servers, and this is not an issue on the rest of them. The Logging feature in IIS Manager is setup identical on this issue server and working servers so I am stumped. Screenshot of "problem" server. Screenshot of "working" server: Screenshot of Logging setup in IIS Manager(which is identical on both trouble and working servers):ChrisHankinsSep 10, 2024Copper Contributor268Views0likes3CommentsWill all Classic ASP apps stop working now that VBScript is about to be removed from Windows OS?
VBScript will be removed from Windows OS in the near future. What does that mean for Classic ASP web applications? Will Classic ASP also be removed from future Windows OS?Pieter_CooremanApr 11, 2024Brass Contributor709Views0likes3CommentsCalls from classic asp web pages to custom com+ soap web adaptor sequential/concurrent issue
Hi, I have a classic asp web site which uses a custom com+ app installed on the server to communicate with a custom soap web service. When I use the website installed on a Windows 10 Ent workstation running IIS 10 it behaves as needed, with separate web page hits making concurrent connections to the web service through the adaptor. However, when I use the site installed on a windows 2012R2 server running IIS 8.5 the actions from different web page hits are queueing and being processed sequentially. This is most noticeable when a series of actions are performed. eg If page hit (a) makes 5 sequential calls to the web service which might take a total of 60 seconds to complete, and then page hit (b) happens a few seconds after page hit (a), none of the actions from (b) are started until all 5 actions from (a) have completed. On the W10/IIs10 machine they are run concurrently. When I test using VBScript running under cscript.exe they run sequentially on both machines, so I am down to thinking that this is an IIS issue. Both instances of IIS and the com+ app are configured the same. The only difference I can see is that IIS Worker Processes info looks very different, with the "good machine" showing 8,412 Private Bytes and a very large 2,151,803,376.00 KB Virtual Bytes, and the "bad machine" showing 66,380.00KB Private and only 95,224 Virtual. The "bad" one has 64GB RAM and the good one only 16GB. This is very confusing because normally I would expect the server to perform better under load/multi-user conditions than the workstation, but this is the other way around. Any idea what may be causing the calls to be queued? Or perhaps it's not the com+ apps calls that are queued, it's just that subsequent pages not start processing until the previous page has finished waiting for a response?pmtelstraOct 27, 2022Copper Contributor634Views0likes3Comments
Resources
Tags
- IIS21 Topics
- http4 Topics
- https3 Topics
- IIS Windows Server 20222 Topics
- roadmap2 Topics
- url rewrite2 Topics
- exchange2 Topics
- url authorization rules2 Topics
- angular1 Topic
- SharePOint 2019 Server1 Topic