FIX: The FastCGI module does not process requests after you enable the CPU Limit feature for an application pool in Internet Information Service (IIS) 7.0

Consider the following scenario in Internet Information Services (IIS) 7.0:

• You use the FastCGI module to host non-ASP.NET applications, such as PHP applications, or Python applications.
• You enable the CPU Limit feature for the application pool in which you are hosting the non-ASP.NET applications.
  
  Note For more information about how to enable the CPU limit feature, see the MORE INFORMATION section.

In this scenario, when you visit these Web applications, they may not run as expected, and you may receive an error message that resembles the following:

The FastCGI module keeps child FastCGI processes in job objects. Therefore, when a worker process finishes, all child FastCGI processes also finish. If the CPU Limit feature is enabled for the application pool, a worker process that is started by Windows Process Activation Service (WAS) is also made part of a job object.

However, job objects cannot be nested in Windows. Therefore, the FastCGI module cannot process requests if the CPU Limit feature is enabled for the application pool.

Hotfix information

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 Web site: 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.

Prerequisites

You must have IIS 7.0 installed to apply this hotfix. You must apply this hotfix on a computer that is running Windows Vista Service Pack 1 or Windows Server 2008.

Restart requirement

You must restart the computer if the IIS is running when you apply this 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 Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008 and of Windows Vista

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about configuring CPU Settings for an Application Pool, visit the following Microsoft Web site: For more information about job objects, visit the following Microsoft Web site: