Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

An upgrade of the IP Address Management feature is unsuccessful in Windows Server 2012 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows Server 2012.
  • You have the IP Address Management (IPAM) feature installed on this computer.
  • You upgrade this computer to Windows Server 2012 R2.
  • You try to upgrade IPAM.

In this scenario, the upgrade of IPAM is unsuccessful. Additionally, you receive the following error message:

An error occurred while performing IPAM server upgrade.

Failed to convert Schema. Please see the details.
The given key was not present in the dictionary.
Please restart the Wizard to update the IPAM server.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. 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, go to the following Microsoft website: 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 2012 R2 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

File information
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows Blue RTM" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Blue RTM" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.3.960 0.16 xxxWindows Server 2012 R2RTMGDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Ipamserver.dll6.3.9600.164734,336,64021-Nov-201311:39x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2
File nameAmd64_796d12281dba2c3f21f9dbdf0e15e8b8_31bf3856ad364e35_6.3.9600.16473_none_92320e05c720c785.manifest
File versionNot Applicable
File size683
Date (UTC)21-Nov-2013
Time (UTC)20:13
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameMsil_ipamserver_31bf3856ad364e35_6.3.9600.16473_none_b4b5b5af95d8cfdb.manifest
File versionNot Applicable
File size5,060
Date (UTC)21-Nov-2013
Time (UTC)12:48
SHA-1 hashNot Applicable
MD5 hashNot Applicable

↑ Back to the top


References

See the terminology Microsoft uses to describe software updates for more information.

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2912551
Revision : 1
Created on : 1/7/2017
Published on : 1/15/2014
Exists online : False
Views : 246