You may receive a "Snap-in Failed to Initialize" error message when you try to view DHCP scope reservations on a Windows Server 2003-based DHCP server

Symptoms

Consider the following scenario. You have a Microsoft Windows Server 2003-based Dynamic Host Configuration Protocol (DHCP) server. On the DHCP server, you have a DHCP scope that has 87 reservations. When you try to view the reservations on this scope, you may receive the following error message:
Snap-in Failed to Initialize

Also, when you use the DHCP management console to connect to the DHCP server, either locally or from another computer, the following error message is displayed in the right pane of the console:
The DHCP server you specified cannot be located. The DHCP server might be down, there might be network problems, or the DHCP service might not be installed. The error was: The parameter is incorrect.

Resolution

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, x86-based versions

Date Time Version Size File name
--------------------------------------------------------------
21-Jul-2005 03:11 5.2.3790.2492 270,848 Dhcpssvc.dll
21-Jul-2005 00:42 5.2.3790.2492 32,256 Arpidfix.exe
Windows Server 2003, Itanium-based versions

Date Time Version Size File name Platform
-----------------------------------------------------------------------
21-Jul-2005 01:14 5.2.3790.2492 732,672 Dhcpssvc.dll IA-64
21-Jul-2005 01:14 5.2.3790.2492 270,848 Wdhcpssvc.dll x86
21-Jul-2005 01:14 5.2.3790.2492 74,752 Arpidfix.exe IA-64


Windows Server 2003, x64-based versions

Date Time Version Size File name
--------------------------------------------------------------
21-Jul-2005 01:14 5.2.3790.2492 432,128 Dhcpssvc.dll
21-Jul-2005 01:14 5.2.3790.2492 270,848 Wdhcpssvc.dll
21-Jul-2005 01:14 5.2.3790.2492 43,008 Arpidfix.exe

Workaround

To work around this problem use one of the following methods.

Method 1: If you have 87 reservations, add a reservation to the scope by using the Netsh command-line utility

netsh dhcp server ServerIP scope ScopeIP add reservedip ReservedIP MACAddress ClientName

Method 2: If you have 87 scopes, add a scope to the DHCP server by using the Netsh command-line utility

netsh dhcp server ServerIP add scope ScopeIPSubnetMask ScopeName ScopeComment

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

More Information

For more information about the standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Propriedades

ID do Artigo: 902954 - Última Revisão: 09/10/2011 - Revisão: 1

Comentários