- You install the Windows Server AppFabric feature on an Internet Information Services (IIS) server that is running Windows 8.1, Windows Server 2012 R2, Windows 7 service Pack 1 (SP1), or Windows Server 2008 R2 SP1.
- You create a website, and then you add multiple applications to the website.
- These applications are running under different application pools.
- You enable the auto-start feature for different services in these applications.
- You deploy a new service to run under the same website. Or, you restart an existing service.
For example, you create a website that is named MySite on an IIS server. MySite includes two applications, which are named App1 and App2. MySite and App1 run in an application pool that is named AppPool1. App2 runs in an application pool that is named AppPool2. In App1, you enable the auto-start feature for a service that is named service_App1. In App2, you enable the auto-start feature for a service that is named service_App2. When you deploy a new service_App3 in application App3, and then run the service in application pool AppPool3, service_App1 and service_App2 are also loaded in the application pool AppPool3. However, only service_App3 should be loaded.
Hotfix informationImportant Do not install a language pack after you install this hotfix. If you do, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.
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 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, visit 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.
PrerequisitesTo apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2. Or, install Service Pack 1 for Windows 7 or Windows Server 2008 R2.
Registry informationTo apply the hotfix in this package, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply the hotfix if IIS is running when you apply the hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
Article ID: 2672277 - Last Review: Jul 2, 2015 - Revision: 1