Microsoft KB Archive Search

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.

  1. Home
  2. The upgrade from Windows Server 2008 to Windows Server 2008 R2 fails if you have applied some TCP-A and NetDMA settings before the upgrade

The upgrade from Windows Server 2008 to Windows Server 2008 R2 fails if you have applied some TCP-A and NetDMA settings before the upgrade

View products that this article applies to.

Symptoms

You try to upgrade Windows Server 2008 to Windows Server 2008 R2. However, the upgrade process fails, and the following information is logged in the Setup log file:
2009-06-05 22:57:33, Info                  MIG    IPostApply::ApplySuccess for Plugin={ServerPath="%windir%\system32\Migration\netiomig.dll", CLSID={ea51459a-a30d-4a33-b294-0e0163551c75}, ThreadingModel=Apartment} - Working directory: C:\$UPGRADE.~OS\OnlineUpgradeApplyWork\srcworking\agentmgr\CCSIAgent\005A6BFD
2009-06-05 22:57:33, Info                         TCPIP: Starting application of all settings from registry.
2009-06-05 22:57:33, Warning                      TCPIP: Instance number 0 does not match the current NSI object description.
2009-06-05 22:57:33, Warning                      TCPIP: Failed to collect instances of object number 2 from the registry: 0xd.
2009-06-05 22:57:33, Warning                      TCPIP: Failed to assemble complete list of object instances that should be applied to NSI (0xd).  Aborting all TCPIP upgrade.
...
2009-06-05 22:57:33, Error      [0x08038d] MIG    Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="%windir%\system32\Migration\netiomig.dll", CLSID={ea51459a-a30d-4a33-b294-0e0163551c75}, ThreadingModel=Apartment}. Error: 0x8007000D
Additionally, some network settings in the registry are reverted to their default values unexpectedly.

This problem occurs if you have applied some TCP-acceleration (TCP-A) and network direct memory access (NetDMA) settings before the upgrade.

↑ Back to the top

Cause

A fix that is included in Windows Server 2008 R2 has a defect. This defect prevents certain additional settings from being updated during upgrade. Therefore, after the upgrade fails, the system restores some settings to their default values.

↑ Back to the top

Workaround

To work around this problem, remove the following settings if you have applied them, and then upgrade to Windows Server 2008 R2:
  • Subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
    Entry:
    EnableTcpa
  • Subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
    Entry:
    EnableDca
After you upgrade to Windows Server 2008 R2, reapply these settings.

↑ Back to the top

More information

When this problem occurs, the following settings are restored to the default values:

TCP window scaling configurations

Examples:
netsh interface tcp set global autotuninglevel = <parameter>
netsh interface tcp set heuristics wsh= <parameter>
UDP dynamic port range

Example:
netsh interface <ipv4/ipv6> set dynamicport udp <parameters>
Network layer settings
  • Global settings
  • Compartment settings
  • Interface settings
  • Address settings
  • Static neighbor settings
  • Path settings
  • Proxy neighbor settings
  • Route settings
  • Subinterface settings
  • Multicast Forward Entries Settings
Example:
netsh interface <ipv4/ipv6> set global <parameter>
Network Driver Interface Specification settings
  • NdisNsiObjectInterfaceInformation
  • NdisNsiObjectNetwork
  • NdisNsiObjectCompartment
  • NdisNsiObjectInterfacePersist
  • NdisNsiObjectInterfaceInformationRaw
Example:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi
Forwarding layer interface settings

Example:
netsh interface <ipv4|ipv6> set interface [interface id] forwarding=enabled
Teredo port number

Example:
Netsh interface teredo set state clientport = <port>
Teredo remote v4 address

Example:
Netsh interface teredo set state server <ipv4>

↑ 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

Keywords: kbprb, kbtshoot, kbexpertiseinter, kbsurveynew, KB973422

↑ Back to the top

Article Info
Article ID : 973422
Revision : 2
Created on : 7/22/2009
Published on : 7/22/2009
Exists online : False
Views : 364