Application pool stopped on webrequest

I have a website that has been working fine for several months. This morning I started getting 503 Service Unavailable errors. After checking IIS, I noticed that the application pool is stopped. Since I had problems with this before, I suspected that the WebRequest problem was a problem. So I commented on part of the WebRequest site and guessed that the application pool is no longer shutting down. I suspect there was another security update, and I cannot figure out what else needs to be done to get WebRequest to work again.

Things I've already tried:
1) aspnet_regiis -u then -i
2) reinstalling .net framework

Additional info: I am using NetworkService account for asp.net v4.0 application pool with Windows Authentication

Error from event log: "HipIISEngineStub.dll failed to load. Data is an error.

var request = (HttpWebRequest)WebRequest.Create(path1); request.Credentials = CredentialCache.DefaultCredentials; request.PreAuthenticate = true; var getResponse = new Func<WebRequest, WebResponse>(req => req.GetResponse()); try { return getResponse(request).GetResponseStream(); } 
+7
source share
1 answer

This seems to be related to McAfee Host intrusion prevention. Maybe your McAfee license has expired? Or do you have an old version that needs to be updated? View your McAfee installation. Perhaps reinstall it.

If you recently uninstalled McAfee or somehow changed the installation, there is probably a link to it in the ISAPI settings. Try removing the link to MfeEngine in your Host.config application:

https://kc.mcafee.com/corporate/index?page=content&id=KB72677&actp=LIST

Quote from the page (my emphasis):

  • Go to: % windir% \ system32 \ inetsrv \ config
  • Open applicationHost.config as an administrator for editing in Notepad.
  • Edit the globalModules section and delete the following line:
 <add name="MfeEngine" image="%windir%\System32\inetsrv\HipIISEngineStub.dll" /> 
  • Edit the modules section and delete the following line:
 <add name="MfeEngine" /> 
  • After editing the applicationHost.config file, save the file, then restart the IIS server using iisreset or restart the system.
+18
source

All Articles