How to: Verify or Correct the IIS Configuration for an Application Pool
You might have problems when you try to access a Web site or Web service if one of the following conditions occurs with an application pool for Team Foundation:
The pool is stopped. The application pool should always be running. If several worker processes fail within a certain period of time, the application pool might stop as a result of the Enable rapid-fail protection setting. For more information about worker processes, see "Configuring Rapid-Fail Protection in IIS 6.0 (IIS 6.0)" in the Windows Server 2003 TechCenter on the Microsoft Web site.
The AutoStart setting is disabled. If an application pool stops running, this setting might get disabled. If you restart the application pool, the AutoStart setting is automatically enabled.
The ASP.NET 2.0 setting is incorrect. For computers that are running Windows Server 2008, the ASP.NET version is assigned to the application pool under which the application runs.
Note
For computers that are running Windows Server 2003, the ASP.NET version is assigned to the Web site under which the application runs. For more information, see How to: Verify or Correct the IIS Configuration for a Web Site or Virtual Directory.
The Identity setting is incorrect. This setting should be set to the service account for Team Foundation Server, which you specified when you installed it. This account is referred to as TFSService.
To verify or correct the Internet Information Services (IIS) configuration for an application pool, verify that each application pool is running and that its identity is correctly set.
Team Foundation Server uses the following application pools with their corresponding identities:
Application Pool |
Identity |
|---|---|
DefaultAppPool |
Network Service |
Microsoft Team Foundation Server Application Pool |
TFSService |
Microsoft Team Foundation Server Proxy Application Pool (only when Team Foundation Server Proxy is installed) |
TFSService |
ReportServer .gif "Note") Note:
You manage ReportServer in IIS for SQL Server 2005 but not for SQL Server 2008.
|
Network Service |
SharePoint Central Administration v3 |
TFSService |
Note
In a single-server deployment, you log on to the application-tier server to stop and start all application pools. In a dual-server deployment, you must log on to the appropriate server where the application pool is defined. For more information about the location of application pools in a dual-server deployment, see How to: Stop and Start Services, Application Pools, and Web Sites.
Required Permissions
To perform these procedures, you must be a member of the Administrators security group on the server where the application pool is defined.
To restart an application pool or change its identity in Internet Information Services 6.0
Log on to the server where the application pool is defined.
Open the Start menu, point to Administrative Tools, and click Internet Information Services (IIS) Manager.
Internet Information Services (IIS) Manager opens.
In the tree pane, expand the local computer, and click the Application Pools node.
The state of each application pool appears in the results pane.
If an application pool is stopped, right-click it, and click Start.
To verify or change the identity of an application pool, right-click the application pool, and click Properties.
On the Identity tab:
For DefaultAppPool and ReportServer, verify that Network Service is selected for the Predefined option. If it is not selected, select it.
For all other application pools for Team Foundation, verify that Configurable is clicked and the User name and Password for the TFSService account are set. If they are not, click Configurable, and specify these values.
If you changed the Identity, stop and restart the application pool.
Close Internet Information Services (IIS) Manager.
To restart an application pool, change its ASP.NET version, or change its identity in Internet Information Services 7.0
Log on to the server where the application pool is defined.
Open the Start menu, point to Administrative Tools, right-click Internet Information Services (IIS) Manager, and then click Run as administrator.
Internet Information Services (IIS) Manager opens.
In the Connections pane, expand the local computer, and click Application Pools.
The state of each application pool appears in the Application Pools page.
If an application pool is stopped, right-click it, and click Start.
On the Application Pools page, review all application pools for Team Foundation.
Under .NET Framework Version, verify that v2.0 appears.
Under Managed Pipeline Mode, verify that Classic appears.
If the assignments are different from those indicated in step 5, click the application pool. In the Actions pane, click Basic Settings.
The Edit Application dialog box opens.
Under .NET Framework version, click .NET Framework v2.0.50727.
Under Managed pipeline mode, click Classic, and then click OK.
To verify or change the identity of an application pool, click it, and then click Set Application Pool Defaults.
Under Process Model, click the Identity property, and then click the properties button (…).
The Application Pool Identity dialog box opens.
To specify an identity option, perform one of the following steps:
For the ReportServer application pool, click Built-in account, and then click either Local System or Network Service.
For all other application pools, click Custom account, and then click Set.
The Set Credentials dialog box opens. In User name and Password, type the user name and password for the TFSService account.
Note
You do not need to recycle application pools or use the iisreset command when you reconfigure an application pool in IIS 7.0. All IIS 7.0 features automatically pick up configuration changes.
Close Internet Information Services (IIS) Manager.
See Also
Tasks
Resolving Problems Accessing Web Services