Share via

Fix Windows Server AppFabric After Upgrading Windows

  • Article

If Windows Server AppFabric is installed on Windows Vista or Windows Server 2008, and the operating system is upgraded to Windows 7 or Windows Server 2008 R2, not all AppFabric features will work correctly on the upgraded operating system. Some features will work correctly; others will not. You will need to run AppFabric setup for the upgraded operating system to resolve the issues. When you run setup, the upgraded version of the setup program will be executed. For more information, see Upgrade Windows Server AppFabric.

To fix AppFabric on an upgraded operating system

  1. Download the setup.exe file for the upgraded operating system from the Windows Download Center (https://go.microsoft.com/fwlink/?LinkID=183123).

  2. Before running AppFabric setup.exe, write down the AppFabric features that you have installed. You will need this information if a reboot is required after running setup.exe.

    Note

    You can determine the AppFabric features that are installed by running regedit and looking at the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppFabric\v1.0\Features.

    Note

    A reboot is not always required after fixing the AppFabric installation. You will be prompted for a reboot if one of the AppFabric files was in use when setup.exe was run.

  3. Ensure that all AppFabric system services (AppFabric Event Collection Service, AppFabric Workflow Management Service, and AppFabric Caching Service) are stopped. Open the Services dialog box by executing services.msc from the Run line, and then verify that the status for each of these services is not Started.

  4. Run AppFabric setup.exe that you downloaded in step 1, selecting the features that you noted in step 2.

    Note

    This setup process will be treated as an AppFabric upgrade. For more information, see Upgrade Windows Server AppFabric.

    Note

    If you are running automated setup, execute setup.exe /u.

  5. If prompted for a restart, restart the computer.

    Note

    Usually after the AppFabric setup program succeeds, you will not be prompted for a restart. However, in this case you may be. If you are, proceed with step 6. If a reboot was not necessary, you do not have to run the Windows Package Manager because the AppFabric installation will be fixed after step 5.

  6. If a restart is necessary, run the Windows Package Manager (pkgmgr.exe) after the computer has restarted. Do so by opening a command prompt, moving to <drive>:\Windows\System32, entering Pkgmgr.exe (with the appropriate parameters, as shown below), and then pressing ENTER.

    Pkgmgr.exe /quiet /norestart /iu:Application-Server-Extensions;Application-Server-Extensions-Admin;Microsoft-Windows-ApplicationServerExtensionsDCServer;Microsoft-Windows-ApplicationServerExtensionsDCClient;Microsoft-Windows-ApplicationServerExtensionsDCAdmin;Application-Server-Extensions-Win7 /p:Microsoft-Windows-ApplicationServerExtensions-Package~31bf3856ad364e35~<processorarch>~~<packageversion>

    Note

    Application-Server-Extensions-Win7 must always be entered.

    Note

    processorach can have the following values: x86 or amd64.

    Note

    For packageVersion, enter the value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppFabric\v1.0\PackageVersion.

    Note

    /iu is followed by a semicolon, and then a delimited list of features. See the following table.

    Feature Registry Key

    Parameter to /iu

    Worker

    Application-Server-Extensions

    WorkerAdmin

    Application-Server-Extensions-Admin

    DCA

    Microsoft-Windows-ApplicationServerExtensionsDCAdmin

    DCS

    Microsoft-Windows-ApplicationServerExtensionsDCServer

    DCC

    Microsoft-Windows-ApplicationServerExtensionsDCClient