IIS MMC hangs after upgrading Windows 2000 to Windows 2003



IIS Manager hangs up on the loading procedure after the OS upgraded from Windows 2000 to Windows 2003. Customer could open IIS Manager but found it hang when right click any item on the left pane. Meanwhile, customer could still browse web pages from the clients.




Customer tried to reinstall IIS but the problem still existed. Checked files under %windir%\system32\inetsrv, there were several files with different versions and they should not be included in a clean installation. Checked iis6.log file and found several flags were set to 1 which means the installation is not completed correctly. So we suggested customer uninstalling IIS and deleting all files under inetsrv and then re-install IIS again using the latest Windows 2003 service pack.

After re-installed IIS, the problem still occurred. We recommended capturing both IIS and MMC hang dump for analysis.


Based on the hang dump of mmc.exe, we can see:


0:000> kbn

 # ChildEBP RetAddr  Args to Child             

00 0007ebcc 7c957d0b 7c821d1e 000004fc 00000000 ntdll!KiFastSystemCallRet


04 0007eed4 63783b41 00000001 031f1ea8 00000000 webengine!RegisterAspNetMMC+0x145 05 0007ef20 63783bac 00000000 0007ef40 00000001 MmcAspExt!CAspNetMMCPropertySheet::GetRemoteObject+0xdc

06 0007ef48 63785c73 00000000 0007efac 00000001 MmcAspExt!CAspNetMMCPropertySheet::ReadData+0x4c

07 0007efa4 4aae27b5 00000000 01e52b20 00000000 MmcAspExt!CAspNetMMCPropertySheet::CreatePropertyPages+0xa9



0:000> du 0x7ecc4

0007ecc4  “C:\WINNT\Microsoft.NET\Framework”

0007ed04  “\v2.0.50727\Regasm.exe C:\WINNT\”

0007ed44  “Microsoft.NET\Framework\v2.0.507”

0007ed84  “27\AspNetMmcExt.dll /tlb:AspNetM”

0007edc4  “mcExt.tlb”


0:000> lmv mMmcAspExt

    Loaded symbol image file: MmcAspExt.dll

    Image path: C:\WINNT\Microsoft.NET\Framework\v2.0.50727\MmcAspExt.dll

    Image name: MmcAspExt.dll

    Timestamp:        Wed Oct 24 11:43:20 2007 (471EBF58)


    FileVersion:      2.0.50727.1433 (REDBITS.050727-1400)


Based the call stack of MMC.exe, the problem is due to MMC.exe failed to load .Net 2.0 related module after system upgrade.




We suggested customer uninstalling .NET 2.0 framework first and then apply .NET 2.0 SP1. The problem was then resolved.




Hanson Wang


Skip to main content