Export (0) Print
Expand All
4 out of 7 rated this helpful - Rate this topic

Troubleshooting Installation of Team Foundation

Visual Studio 2008

This topic provides information useful in isolating the cause of a problem that can occur when you install Visual Studio Team System Team Foundation Server and its prerequisites, and provides solutions for resolving these problems. The most common reasons for an installation of Team Foundation Server to fail are:

  • One or more procedures were skipped during the installation of a prerequisite component.

  • Not all components from a previous installation were completely removed.

  • Changes were made to one or more prerequisite components to increase secure connections, but these changes interfere with the successful installation of Team Foundation Server.

Each of the following sections describes a symptom and explains how to solve the underlying problem. If these sections do not help resolve the problem and resume the installation, you can uninstall Team Foundation Server, and try to install it again. For more information, see "How to: Uninstall Team Foundation Server" in this document on the Microsoft Web site: Team Foundation Installation Guide for Visual Studio Team System 2008.

By default, the log files are located in the following directory on the computer where you installed Team Foundation Server. The two types of log files that are useful for troubleshooting purposes are described in the following table:

Log file

Description

Drive:\Documents and Settings\SetupAccount\Local Settings\Temp\dd_install_vstf_at_90.txt

Cumulative log for the installation of the application tier.

Drive:\Documents and Settings\SetupAccount\Local Settings\Temp\dd_install_vstf_tfc_90.txt

Cumulative log for the installation of Team Explorer.

Drive:\Documents and Settings\SetupAccount\Local Settings\Temp\VSMsiLogRandomFourDigitNumber.txt

In the preceding path, RandomFourDigitNumber represents an actual random number in the file name.

Verbose text file for the installation of a Team Foundation component. A new log file is created each time the setup wizard reaches the progress bar page.

NoteNote:
If the installation fails or you cancel the installation prior to the setup wizard reaching the progress bar page, then no log file is generated.

Because the dd_*.txt files are cumulative, look towards the end of the file for information that pertains to the current setup. Also, search for the text string ERRORLOG EVENT, but be aware that not all instances of these entries may indicate the cause of an installation problem.

Check the time stamp on the VSMSI*.txt log file, to make sure that you are looking at the most recent setup attempt. In this file, start at the end and scroll up. Also, perform a search for any error messages that were written to the setup wizard.

The following symptoms match the problems that most frequently occur during installation of Team Foundation Server. The symptoms are listed from most frequent to least frequent. These errors appear in the installation wizard for Team Foundation Server. To isolate the cause of the error, open the VSMsiLog file, search for the error number, and analyze the command and parameters that are logged as part of the error. For information about viewing the log files, see Installation Log Files

Error 32000

When installing Team Foundation Server or upgrading to Visual Studio Team System 2008 Team Foundation Server, the following error appears in the installation wizard:

Error 32000. The Commandline ‘[1]’ returned non-zero value: [2]

This error appears when a failure occurs that the setup process does not explicitly capture. Review the VSMsiLog file to help pinpoint the cause of the error. Search for the text "Return value 3" and review the command and parameters that were logged just prior to this text. To gain more insight into the cause of the failure, open a command prompt and run the same command and parameters.

Problem

Solution

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.

NoteNote:
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. 

Error 29112

When installing Team Foundation Server, the following error appears in the installation wizard:

Error 29112. Team Foundation Report Server Configuration: Either SQL Reporting Services is not properly configured, or the Reporting Services Web site could not be reached. Use the Reporting Services Configuration tool to confirm that SQL Reporting Services is configured properly and that the Reporting Service Web site can be reached, and then run the installation again. For more information, see the Team Foundation Installation Guide.

Possible causes and solutions for this error are described below:

Problem

Solution

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.

NoteNote:
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.

Error 29109

When installing Team Foundation Server, the following error appears in the installation wizard:

Error 29109. Team Foundation Report Server Configuration: SQL Reporting Services configuration encountered an unknown error. Verify that you have sufficient permissions to configure SQL Reporting Services, and try again.

Possible causes and solutions for this error are described below:

Problem

Solution

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.

    NoteNote:
    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.

Error 28806

When installing Team Foundation Server, the following error appears in the installation wizard:

Error 28806. An unexpected error occurred. Verify that SQL Server Reporting Services is installed and running on the Team Foundation app tier and that you have sufficient privileges to access it. For more information, see the setup log.

The possible cause and solution for this error are described below:

Problem

Solution

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.

Error 29000

When installing Team Foundation Server, the following error appears in the installation wizard:

Error 29000. An unexpected error occurred. Verify that SQL Server Reporting Services is installed and running on the Team Foundation app tier and that you have sufficient privileges to access it. For more information, see the setup log.

The possible causes and solutions for this error are described below:

Problem

Solution

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.

Error 28805

When installing Team Foundation Server, the following error may appear in the installation wizard:

Error 28805. The setup program cannot complete the request to the server that is running SQL Server Reporting Services. Verify that SQL Server Reporting Services is installed and running on the Team Foundation app tier and that you have sufficient permissions to access it. For more information, see the setup log.

The possible causes and solutions for this error are described below:

Problem

Solution

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.

Error Message About SQL Server Collation

When installing Team Foundation Server, the following error may appear during the health check:

There is an error with the collation settings for SQL Server. The collation settings are not compatible with Team Foundation Server.

Team Foundation Server requires that collation is case insensitive and accent sensitive. If you want to use an installation of SQL Server with Team Foundation Server, the collation settings of SQL Server must meet these requirements. You cannot change the collation settings after you install SQL Server. For more information, see this page on the Microsoft Web site: Collation Settings in Setup

The two most common problems and their solutions that users encounter when installing Windows SharePoint Services Extensions are described in the following table:

Problem

Solution

SharePoint Products and Technologies is not installed.

  1. Install SharePoint Products and Technologies as described in the topic: "Installing SharePoint Products and Technologies" provided in the installation guide for Team Foundation.

  2. Exit the installation of Windows SharePoint Services Extensions, and then restart it.

The version of SharePoint Products and Technologies that is installed is not supported.

  1. Uninstall the version of SharePoint Products and Technologies that is installed.

  2. Install Windows SharePoint Services 2.0 or later.

  3. Exit the installation of Windows SharePoint Services Extensions, and then restart it.

For more information, see Windows SharePoint Services Extensions.

When installing Team Foundation Build, the following error may appear in the installation log file:

ca_addlogonserviceprivilege_x86_enu.3643236f_1603

The cause and solution for this error is described below:

Problem

Solution

The Domain Controller for the domain in which the server is a member is not available and Team Foundation Build is being installed by using Network Service as the service account.

  1. Make sure that the domain controller is running and that the network connection from the server where you are installing Team Foundation Build is working.

  2. Check the user account being used to install Team Foundation Build.

    NoteNote:
    If you do not want to install under the Network Service account you can install Team Foundation Build using a domain user account.
  3. Retry installing Team Foundation Build..

Team Explorer is a separate product that you install from the Team Foundation Server installation media. It is accessible from the Team Foundation Server Setup page.

The most common failure that may occur when installing Team Explorer is when it is installed on a computer on which Visual Studio is not installed. If both Visual Studio and Team Explorer are installed on the same machine, installing Visual Studio first will reduce the likelihood that a Team Explorer installation will fail.

NoteNote:

These failures occur when installing Team Explorer because if Visual Studio is not already installed, Team Explorer installs a light version of Visual Studio, called Preferred Partner Edition (PPE). Rebooting resolves most of the problems associated with the Team Explorer installation because under some systems the computer must be reset in order to use PPE.

Problem

Solution

Team Explorer is not accessible.

  1. Reboot the computer.

  2. Reinstall Team Explorer.

Team Explorer is both a standalone client, in the absence of Visual Studio Team System 2008, and also an integrated part of Visual Studio. If you install Visual Studio and then install Team Explorer, Team Explorer will be available through Visual Studio. If you install Team Explorer but do not install Visual Studio, you can use Team Explorer only from Visual Studio PPE. You can also uninstall either Visual Studio or Team Explorer without incurring any problems.

Common problems that occur when creating a team project, accessing documents and reports from Team Explorer, or not being able to access Web site are addressed below.

Project Creation Wizard Fails

Two common errors that cause the Project Creation Wizard to fail are addressed below. For more information, see Troubleshooting Team Project Creation and Deletion.

Unable to connect to the specified SQL Server Reporting Services at TFSServerName.

The cause and solution for this error is described below:

Problem

Solution

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.

TF30170: The plugin Microsoft.ProjectCreationWizard.Portal failed during task SharePointPortal from group Portal.

The cause and solution for this error is described below:

Problem

Solution

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.

Documents and Reports are Unavailable in Team Explorer

When you connect to Team Foundation Server using Team Explorer, the Documents and Reports nodes of a project may be unavailable. This is indicated by a red x on the nodes. This may indicate that the firewall on the computer that hosts Team Foundation Server does not have an exception configured for port 80. You must add this port to the exception list for your firewall application. For more information, see How to: Verify or Correct Port Assignments.

Service Unavailable Error for a Team Foundation Web Site

If you installed SharePoint Products and Technologies interactively and the Web browser cannot open the Configure Administrative Virtual Server page, verify that network connections to local addresses bypass the proxy server.

To bypass the proxy for local addresses

  1. Click Start, click Control Panel, and then click Internet Options.

  2. On the Connections tab, click LAN Settings.

  3. In the Local Area Network (LAN) Settings dialog box, select Bypass proxy server for local addresses.

  4. Click OK, and then click OK again.

  5. Click Refresh to display the page.

You can review the installation log files for detailed information about installation of Team Foundation Server, including errors that might have occurred. By using these logs, you can often pinpoint a solution to resolve a failed installation. For information about how to troubleshoot some of the prerequisites, see the following sections.

Internet Information Services (IIS)

For more information about how to troubleshoot IIS, see this page on the Microsoft Web site: IIS 6.0 Documentation.

SQL Server

For more information about how to troubleshoot SQL Server issues, see this page on the Microsoft Web site: SQL Server documentation.

SharePoint Products and Technologies

The following section offers resolutions for a variety of issues you might experience as you install SharePoint Products and Technologies. Best practices suggest that you try the resolutions found in the Team Foundation Server documentation first. For more information about the installation of SharePoint Products and Technologies, see this page on the Microsoft Web site: Windows SharePoint Services Administrator's Guide.

Verify or Correct the Configuration of SQL Server Reporting Services

To verify or correct the configuration of SQL Server Reporting Services

  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, make sure that the name of the current data-tier server appears and that the instance name is MSSQLSERVER, and then click Connect.

    NoteNote:

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

  4. If a green check mark does not appear next to Server Status, click Server Status, and then click Status to restart it.

  5. If a green check mark does not appear next to one of the next five objects in the list, for each of those objects, click the object, and correct its configuration.

  6. In the Explorer pane, click Report Server Virtual Directory. Make sure that the value of Name is ReportServer and the value of Website is Default Web Site.

  7. In the Explorer pane, click Windows Service Identity. Make sure that the value of Service Name is ReportServer, and that the value of Service Account is defined as follows:

    • If this is a single-server deployment, Service Account must be set to Local System.

    • If this is a dual-server deployment, Service Account must be set either to Network Service or to a domain user account.

  8. With Orcas install guide we have been recommending customers to use domain user accounts in place of built in account for SSDE, SSAS & SSRS services.

  9. In the Explorer pane, click Database Setup. Make sure that the correct server is defined for Server Name, that Database Name is ReportServer, and that Service Credentials is selected for the Credentials Type.

  10. (Optional) In the Explorer pane, click Initialization. Make sure that the correct values are defined for Machine, Instance, and ID. Verify that the Initialized check boxes are selected. If they are not, select the instance and click Initialize.

    NoteNote:

    The Initialization page is used to view the initialization status for a scale-out deployment or to join a report server to a scale-out deployment. This page does not show initialization status for a single server installation. A single server installation is initialized automatically when you set the database connection.

  11. Close Reporting Services Configuration Manager.

Add a User Account to the Local Administrators Group

To add a user to the local administrators group

  1. Click Start, click Administrative Tools, and then click Computer Management.

  2. In the navigation pane, expand System Tools, expand Local Users and Groups, and then expand Groups.

  3. Right-click Administrators, and then click Add to Group.

In the Administrators Properties dialog box, click Add.

  1. In the Select Users, Computers, or Groups dialog box, add the user account, and click Check Names.

  2. Click OK, and then click OK again.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.