DHCP Interface Crash – windows 2008 R2


 
 
I have raised a bug with microsoft regarding MMC crash, and here are the details about the same.
 
I have observed this behavior on windows 2008 R2 RC build and would encourage users to try with the latest build.
 
ISSUE : On windows 2008 R2 Rc 64 bit edition server uncheck IPV4 address and use IPV6 and try to configure the DHCP role , and we get MMC error “MMC snap-in failed to load”
 
 
Resolution From Product DHCP Product Group :
 
There are a couple of work arounds which could be used in this situation:
1. Have a static IPv6 address on the interface. This is in any case would be required for DHCP server to bind to. We have found that in case of a static IPv6 address, the role installation of DHCP server works fine.
 

2. Use the command line mode for installation (ocsetup or powershell). (In powershell, you can run import-module servermanager, followed by add-windowsfeature dhcp)

3. Enable IPv4, install the server role and then disable IPv4. After installation of the server role, the DHCP MMC works fine regardless of whether IPv4 is enabled or not.

Hope the article will help and please do post your comments after testing the behavior.

 
 
Sainath
Microsoft MVP
Advertisements

8 thoughts on “DHCP Interface Crash – windows 2008 R2

  1. This looks like a problem with the number of leases. We are only using IPv4. Do I have to uninstall the DHCP server and reinstall and then restore from backup? Does Microsoft have a fix yet?

  2. Experience similar MMC Crash issue with dhcpmgmt.mmc. We only use IPv4. IPv6 is disabled. I restored DHCP from Win2K3, as I’ve done on many other DHCP servers, then I Authorize the new sever, expand DHCP, expand servername, then when I expand IPv4 it quickly shows the Filters container and crashes.

    • Hi Jason,
      Could you provide me the windows server version , dhcpcsvc.dll , dhcpmon.dll, dhcpsapi.dll versions ?
      Is there an error message you see ?

  3. Thanks Sainath … This is migration to Win2K8 R2.

    Problem signature:

    Problem Event Name: APPCRASH

    Application Name: mmc.exe

    Application Version: 6.1.7600.16385

    Application Timestamp: 4a5bc808

    Fault Module Name: dhcpsnap.dll

    Fault Module Version: 6.1.7600.16385

    Fault Module Timestamp: 4a5bdecc

    Exception Code: c0000005

    Exception Offset: 0000000000066131

    OS Version: 6.1.7600.2.0.0.272.7

    Locale ID:

  4. I’m also set now … issue was caused by ghosted/undefined 135/136 options after custom 128-133 options were created. Deleting 135/136 resolved the issue.

    • i dont have Options 135/136 to mark. i dont even use Options 128-133 but get the same Error.

      i have server 2008 r2 x64. after migrating my dhcp from a 2003 r2 by using
      netsh dhcp server export/ import, the mmc console started to crash when i expand the ipv4 container. I tried to reinstall the dhcp role but even with a clean install it crashes the same way.

  5. After testing around some time, I realised, that when i opened the mmc console on another 2003 server, added the dhcp snap in to the mmc console, added the 2008 r2 server to the dhcp snap in, i can browse all the settings without crashing the mmc. The DHCP Service is up an running. the only thing that crashes ist the mmc console.

    maybe its a problem with service pack 1 i installed.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s