Jaa


Upgrade Windows Server AppFabric

The Windows Server AppFabric setup program enables you to upgrade the version of AppFabric. If you run the setup program on a computer that has a previous version of AppFabric installed on it, the setup wizard gives you the option of upgrading or uninstalling AppFabric. You cannot add or remove individual features.

The AppFabric upgrade program enables you to upgrade from the Beta 2 Refresh version of AppFabric to the RTW version. To be upgradable, AppFabric Beta 2 Refresh must be installed with the .NET Framework 4 RTM or higher.

The AppFabric upgrade program does not enable you to upgrade from a Beta 1 or Beta 2 version of AppFabric. Using the program, you can only upgrade from AppFabric Beta 2 Refresh to RTW. You must upgrade from AppFabric Beta 1 or Beta 2 by first uninstalling AppFabric, and then installing a later version. For more information, see Remove Features and Uninstall and Install Windows Server AppFabric.

The AppFabric Installation Wizard can be initiated in several different ways, for example, from an executable downloaded from the Microsoft Download Center or from the Install AppFabric command on the Start menu. Any of these commands can start the upgrade process. Only the AppFabric Setup Wizard enables you to upgrade AppFabric; you cannot use the AppFabric Configuration Wizard to upgrade AppFabric configuration. Existing configuration and registry settings will not be changed. This includes .NET Framework 4 RTM configuration files and root and application Web.config files.

The upgrade program performs a prerequisite check, and waits until all prerequisites have been installed to proceed with the upgrade. If any AppFabric Windows service is running, upgrade stops at the Platform Validation page and notifies you that the Event Collection Service, Workflow Management Service, and/or Caching Service are running. The services must be stopped before you can continue. After you have stopped them, the prerequisite check will succeed and you can resume the upgrade process. Upgrade checks only if a default instance of the Event Collection Service, Workflow Management Service, or Caching Service is running. Upgrade does not check for additional instances of the Event Collection Service, Workflow Management Service, or Caching Service that were created after the installation of AppFabric. If there are additional service instances that are not known to the setup program, then upgrade will continue and you may be prompted for a reboot at the end of the upgrade, because the files may be in use if the additional service instances were not stopped prior to the upgrade. In the case of automated installation, the installation script must stop the services prior to the upgrade. The upgrade will proceed even if the services are running. The computer must be rebooted after the upgrade.

After upgrading AppFabric, you may need to run a database upgrade script if the AppFabric upgrade requires database schema to be updated as a part of the upgrade process. If database upgrade is required, until this step is done the system will be in an inconsistent state due to database version mismatch. The upgrade of databases used in AppFabric is always a manual process.

In This Section