A problem that involves SQL Server Reporting Services.

Open Internet Information Services (IIS) Manager, remove the virtual directories and the application pool associated with Reporting Services, and then restart the installation of Team Foundation Server.

1. Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2. In the tree pane, expand the local computer, and then click Web Sites.

3. For each Web site except Default Web Site, right-click the Web site and click Stop.

4. In the tree pane, expand Web Sites, and then expand the Default Web Site.

5. Right-click Reports, click Delete, and then click Yes to confirm the deletion.

6. Right-click ReportServer, click Delete, and then click Yes to confirm the deletion.

7. In the tree pane, expand Application Pools.

8. Right-click ReportServer, click Delete, and then click Yes to confirm the deletion.

9. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry

The ISO image file is bad. This problem almost always involves a trial edition of Team Foundation Server.

Obtain a new ISO image file and retry the installation of Team Foundation Server.

1. Download a new image file from this page on the Microsoft Web site: Visual Studio Team System 2008 Team Foundation Server (90-day Trial).

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

You started the installation while logged on with an account that is not a member of the Administrators group on the local computer.

1. Add the user account to the Administrators group on the local computer, or log on as a user that is already a member of that group.

   For more information, see Add a User Account to the Local Administrators Group).

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The SQL Server sa account is named something other than sa.

Change the SQL Server system administration account name to sa, retry the installation, and then rename the account back to its former name.

Note:

A Microsoft recommended best practice is to change the name of the SQL Server system administration account. However, the installation of Team Foundation Server requires that this account be named sa. After installation, the account can be renamed.

1. Open SQL Server Management Studio. For more information, see How to: Correct the Data-tier Name Configuration.

2. Optional. To determine the name of the system administrator account, click New Query, type the following text, and then run the query:

   use master
   select * from sys.server_principals 
   where principal_id=1
   

3. In Object Explorer, expand Security, and then click Logins.

4. In Object Explorer Details, right-click the login for the system administrator account, and then click Rename. Change the account name to sa.

5. Retry the installation of Team Foundation Server. Press the Retry button on the Setup Failed page.

6. Optional. Rename the sa account back to the original name.

For more information, see this document on the Microsoft Web site: SQL Server 2005 Security Best Practices - Operational and Administrative Tasks.

A non-zero value of -1 and a command-line error that contains "\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe" indicates that a host header has been defined for Default Web Site.

Remove the server binding assigned to Default Web Site, and then retry the installation of Team Foundation Server.

1. Open IIS Manager.

2. Right-click Default Web Site and click Properties.

3. Click Web Site, and then click Advanced.

4. Click the identity of the Web site, and then click Edit.

5. Clear the text from Host Header value, and then click OK.

6. Click OK twice again.

7. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

A non-zero value of -2130246810 in the error message indicates that the Default Web Site is bound to a specific IP address.

Remove the server binding assigned to Default Web Site, and then retry the installation of Team Foundation Server. 

1. Open Internet Information Services (IIS) Manager and change the IP address of Default Web Site to All Unassigned.

   For more information, see How to: Verify or Correct Server Binding Assignments.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

At least one of the report schema files in the database has become corrupted.

• Contact Microsoft Support to obtain new schema files, and then retry the installation.

The return value in the error message is -2130242250 or -1, which indicates an error in the installation of Windows SharePoint Services 2.0.

1. Uninstall Windows SharePoint Services 2.0.

2. Either reinstall Windows SharePoint Services 2.0 or else install Windows SharePoint Services 3.0. 

   Make sure to install all service packs that are available for the version you choose to install.

   Make sure that you install Windows SharePoint Services using the Server Farm option. For more inforamtion, see "How to: Install SharePoint Products and Technologies on Windows Server" in the installation guide of Team Foundation.

3. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry. 

Various reasons.

In some cases, the installation of Team Foundation Server continues if, on the Setup Failed page of the installation wizard, you click Retry repeatedly: as many as four times. 

SQL Server Reporting Services is not configured properly.

Correct the configuration of Reporting Services and then retry the installation of Team Foundation Server.

1. To verify and correct the configuration for Reporting Services, see the procedures provided below: Verify or Correct the Configuration of SQL Server Reporting Services.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard click Retry.

The default application pool in IIS Manager is not running under the Network Service account.

Correct the account configuration of the ReportServer application pool, and then retry the installation of Team Foundation Server.

1. Verify that the ReportServer application pool is running and correct its service account assignment as needed. For more information, see How to: Verify or Correct the IIS Configuration for an Application Pool.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

A return value of - 2147220956 and a notice of invalid namespace in the MSI log file indicates that IIS 5.0 isolation mode may be enabled.

Disable IIS 5.0 isolation mode and retry the installation of Team Foundation Server.

Note:

By enabling isolation mode in IIS 5.0, you disable application pools that SharePoint Products and Technologies requires to connect to the configuration database. You can install SharePoint Products and Technologies with application pools disabled, but Team Foundation Server does not install correctly.

1. Click Start, click Control Panel, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2. Right-click the Web Sites folder, and then click Properties.

3. On the Service tab, clear the Run WWW service in IIS 5.0 isolation mode check box.

   Click OK.

4. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The virtual directories for SQL Server Reporting Services are not in the correct location. The most common cause of this problem is that you install SharePoint Products and Technologies after you install Reporting Services.

Correct the configuration of Reporting Services and then retry the installation.

1. On the server that is running Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools

2. If the server runs Windows Server 2003, click Reporting Services Configuration. If the server runs Windows Server 2008 , click Reporting Services Configuration Manager.

3. In the Report Server Installation Instance Selection dialog box, ensure that the name of the current data-tier server appears, that the instance name is MSSQLSERVER, and then click Connect.

   Note:

   If you used a named instance for Team Foundation Server, you must specify the instance name instead of MSSQLSERVER.

4. In the Explorer pane, click Report Server Virtual Directory.

5. Ensure that the value of Name is ReportServer and the value of Website is Default Web Site.

6. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The server that hosts Reporting Services is not running.

1. Restart the server that hosts SQL Server Reporting Services.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

SQL Server Reporting Services is not running as the TFSService account.

Configure Reporting Services to use the TFSService account, and then retry the installation.

1. Open the Reporting Services Configuration Manager.

   For instructions, see the procedures provided below: Verify or Correct the Configuration of SQL Server Reporting Services.

2. In the Explorer pane, click Database Setup.

3. In Credentials Type, click Windows Login.

4. In Account Name and Password, type the username and password of the TFSService account.

5. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The server that hosts SQL Server Analysis Services is not running or the service account for Reporting Services has insufficient permissions.

Restart the server or add permissions to the service account for Reporting Services, and then retry the installation.

1. If the server that hosts Analysis Services is not running, restart it.

2. Grant the required permissions to the setup account on the server that hosts Analysis Services.

   The simplest way to grant the permissions is to add the setup account to the local administration group on the server that hosts Analysis Services. For detailed instructions, see Add a User Account to the Local Administrators Group.

3. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

SQL Server FullText Search is either not installed or is not running.

Open Services Manager and start SQL Server FullText Search. If Full Text Search is not installed, install it. Then retry the installation.

1. Click Start, click Administrative Tools, and then click Services.

   Services Manager opens.

2. If SQL Server FullText Search appears but the status is not Started, right-click the service and then click Restart.

3. If SQL Server FullText Search is not listed, open Add or Remove Programs from the Control Panel, click Microsoft SQL Server 2005 or Microsoft SQL Server 2008, and then click Change.

4. In the SQL Server Maintenance dialog box, click To install a new component, click here.

5. In the Installation Media dialog box, browse to the location of the setup.exe file for your version of SQL Server. 

6. When the setup wizard launches, select FullText Search to add the missing service.

7. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The credentials for SQL Server Reporting Services are insufficient to create the Reporting Services data source.

1. Make sure the credentials for Reporting Services are set to use Network Service and then retry the installation. For more information, see "Update the Identity of the Service Account for Reporting Services" in How to: Redirect Reporting Services to Connect to a Different Data-Tier Server.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

Certificates are installed on a Web site, and those certificates are not ignored.

Change the certificate settings for Reporting Services and then retry the installation.

1. To ignore certificates, change SecureConnectionLevel to 0.

   For detailed instructions, see this page on the Microsoft Web site: RSReportServer Configuration File.

2. To retry the installation of Team Foundation Server, on the Setup Failed page of the installation wizard, click Retry.

The firewall for the application-tier server does not have an exception configured for port 80.

Add port 80 to the exception list for your firewall application. For more information, see How to: Verify or Correct Port Assignments.

The Windows SharePoint Services Extensions for Team Foundation Server on the computer that is running SharePoint Products and Technologies.

If the deployment of SharePoint Products and Technologies is not located on the application-tier computer, you must install the Windows SharePoint Services Extensions for Team Foundation Server on the computer that is running SharePoint Products and Technologies. This process installs the site templates necessary for project creation. You should install these extensions after you install Team Foundation Server. For more information, see Windows SharePoint Services Extensions.