IIS HTTP Stopped Taking Request and Connections_refused
Comments (2) Recently, one of the web server suddenly stopped from taking any request, restarted IIS WWW service won’t help, and there is no W3WP.exe in the process at all! Everything else seems normal, of course restarting the whole server helps, but it will happen again in a few months, so this is not the permanent solution.
Then I found out there are tons of “Connections_refused” entries are logged in the Httperr.log, it turns out the server has run out of non-pool memories.
Work around for this issue is to add the EnableAggressiveMemoryUsage registry entry to the following registry subkey:
Then, set the EnableAggressiveMemoryUsage registry entry to 1.
To do this, follow these steps:
- Click Start, click Run, type regedit in the Open box, and then click OK.
- Click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
- On the Edit menu, point to New, and then click DWORD Value.
- Type EnableAggressiveMemoryUsage, and then press ENTER.
- On the Edit menu, click Modify.
- In the Value data box, type 1, and then click OK.
- On the File menu, click Exit to exit Registry Editor.
- Restart the HTTP service. To do this, follow these steps:
- Click Start, click Run, type cmd in the Open box, and then click OK.
- At the command prompt, type net stop http /y, and then press ENTER.
- At the command prompt, type iisreset /restart, and then press ENTER.
By default, the HTTP service in IIS 6.0 stops accepting connections when nonpaged pool memory reaches 20 MB. When you enable the EnableAggressiveMemoryUsage registry entry, the HTTP service stops accepting connections when nonpaged pool memory reaches 8 MB.
