Symptoms
Consider the following scenario:
-
You install Windows Server AppFabric on a server that is running Internet Information Services (IIS) 7.5.
-
You create a website. Then, you add multiple applications to the website.
-
You configure these applications to run under different application pools.
-
You enable the auto-start feature for different services in these applications.
-
You start the application pool that is used by the website.
In this scenario, all the services in these applications are preloaded unexpectedly. You expect only the services that the application runs in the same application pool of the website to be loaded.For example, you create a website named MySite on a IIS 7.5 server. MySite includes two applications named App1 and App2. MySite and App1 run in an application pool named AppPool1. App2 runs in an application pool named AppPool2. In App1, you enable the auto-start feature for a service named service_App1. In App2, you enable the auto-start feature for a service named service_App2. When AppPool1 is started, service_App1 and service_App2 are loaded in the application pool AppPool1. However, only service_App1 should be loaded.
Cause
This issue occurs because of an error that occurs when IIS checks the applications that are part of the application pool where the website is runs. In the example that is described in the Symptoms section, when AppPool1 is started, IIS incorrectly assumes that both App1 and App2 are running in the same application pool. Therefore, both service_App1 and service_App2 are preloaded. However, App2 runs in another application pool and service_App2 should not be preloaded.
Resolution
Update information
The following files are available for download from the Microsoft Download Center:
119591 How to obtain Microsoft support files from online servicesMicrosoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Prerequisites
You must have IIS 7.5 installed to apply this hotfix. This hotfix can be installed on a computer that is running Windows 7 or Windows Server 2008 R2.
Restart requirement
If IIS is running when you apply this hotfix, you must restart the computer after you apply the hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
For all supported x86-based versions of Windows 7
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Iisw3adm.dll |
7.5.7600.20708 |
396,288 |
06-May-2010 |
12:47 |
x86 |
|
W3tp.dll |
7.5.7600.20708 |
15,872 |
06-May-2010 |
12:48 |
x86 |
|
W3wphost.dll |
7.5.7600.20708 |
55,296 |
06-May-2010 |
12:48 |
x86 |
|
Wbhstipm.dll |
7.5.7600.20708 |
24,064 |
06-May-2010 |
12:48 |
x86 |
|
Wbhst_pm.dll |
7.5.7600.20708 |
23,552 |
06-May-2010 |
12:48 |
x86 |
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Iisw3adm.dll |
7.5.7600.20708 |
451,584 |
06-May-2010 |
11:46 |
x64 |
|
W3tp.dll |
7.5.7600.20708 |
19,968 |
06-May-2010 |
11:48 |
x64 |
|
W3wphost.dll |
7.5.7600.20708 |
60,928 |
06-May-2010 |
11:48 |
x64 |
|
Wbhstipm.dll |
7.5.7600.20708 |
28,672 |
06-May-2010 |
11:48 |
x64 |
|
Wbhst_pm.dll |
7.5.7600.20708 |
25,600 |
06-May-2010 |
11:48 |
x64 |
For all supported IA-64-based versions Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Iisw3adm.dll |
7.5.7600.20708 |
941,056 |
06-May-2010 |
08:54 |
IA-64 |
|
W3tp.dll |
7.5.7600.20708 |
40,960 |
06-May-2010 |
08:59 |
IA-64 |
|
W3wphost.dll |
7.5.7600.20708 |
144,384 |
06-May-2010 |
08:59 |
IA-64 |
|
Wbhstipm.dll |
7.5.7600.20708 |
65,536 |
06-May-2010 |
08:59 |
IA-64 |
|
Wbhst_pm.dll |
7.5.7600.20708 |
67,072 |
06-May-2010 |
08:59 |
IA-64 |
Workaround
To workaround thIS issue, put applications under different Web sites.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about Windows Server AppFabric, visit the following Microsoft Developer Network (MSDN) Web site:
Windows Server AppFabricFor more information about Auto-Start feature and how to configure it, visit the following MSDN Web site:
