IIS 7 and Above
Known Issues and Workarounds
IIS Admin Service Crashing
Last post Jul 14, 2012 03:39 PM by owjeff
May 16, 2012 09:21 PM|computerwhizguy|LINK
We encountered a problem this week with the IIS Admin Service and the SMTP service crashing unexpectedly in IIS 7.5 under Windows 2008 R2 64 bit, 4 processors, 8GB of RAM. I wanted to share the problem and cause. However I am not sure why the typo affects
IIS in such a bad way.
After comparing a backup of IIS from a few months ago with one made today, we found that the IIS configuration (specifically the applicationhost.config file) contained an invalid netmask in an "allow IP restriction" on a virtual directory. What was entered
in the IIS manager was
Allow 192.168.2.0, netmask of 255.255.254 (no .0 at the end).
Allow 192.168.2.0, netmask of 255.255.254.0
This caused the IIS Admin Service to crash whenever the SMTP service was started, or running Metabase Explorer, or trying to open the root of the website through VBscript and a GetObject method call.
What was reported in the windows event logs was:
Log Name: Application
Source: Application Error
Date: 5/16/2012 12:21:38 PM
Event ID: 1000
Task Category: (100)
Faulting application name: inetinfo.exe, version: 7.5.7600.16385, time stamp: 0x4a5bd0e3
Faulting module name: abocomp.dll, version: 7.5.7600.16385, time stamp: 0x4a5bde62
Exception code: 0xc0000005
Fault offset: 0x00000000000299e7
Faulting process id: 0xe08
Faulting application start time: 0x01cd338859e84291
Faulting application path: C:\Windows\system32\inetsrv\inetinfo.exe
Faulting module path: C:\Windows\system32\inetsrv\abocomp.dll
And when attempting to start the SMTP service, would receive the error:
Windows could not start the Simple Mail Transfer Protocol (SMTP) service on Local Computer Error 1067: The process terminated unexpectedly.
In addition, when running the Metabase Explorer would receive the error message:
An error occurred: Failed to enumerate subkeys. Reason: The remote procedure call failed. Do you want to continue?
Can anyone else confirm this behavior / surprised it's this fragile. Maybe some input validation when entering IP addresses and netmasks would be appropriate.
This just goes to show you how important it is to enter the addresses carefully and check them twice.
May 17, 2012 02:45 AM|lextm|LINK
Jul 14, 2012 03:39 PM|owjeff|LINK