Visual Studio 2005 Team Foundation Server Readm...

Visual Studio 2005 Team Foundation Server Readme

Updated December 14, 2006

See Microsoft Visual Studio 2005 Team Foundation Server Known Issues for non-setup related issues.

1. System Requirements

The system requirements for Team Foundation Server and Team Explorer are located in the Team Foundation Installation Guide. The most current version of the Installation Guide is available for download from the Microsoft Download Center. For more information, see http://go.microsoft.com/fwlink/?LinkId=40042.

1.1    Installing Team Foundation Server That Has Microsoft SQL Server 2005 (32-Bit) on a 64-Bit operating system is not supported.

If you try to install Team Foundation Server on a 64-bit operating system with Microsoft SQL Server 2005 (32-bit), setup does not detect the SQL Server services and blocks installation.

To resolve this issue

Use dual-server deployment, complete the installation steps for the Team Foundation data tier using Microsoft SQL Server (64-bit). For more information, see the topics "Team Foundation System Requirements" and "Overview of Team Foundation Server Dual-Server Deployment" in the Installation Guide.

2. Product Installation

2.1   Antivirus applications that are configured to clean the \temp folder will cause setup to fail if it must restart.

If setup must restart, and the antivirus application is set to clean the \temp directory on start, required setup files will be deleted and setup will fail with a program not found error.

To resolve this issue

Restart setup after restarting the computer.

2.2    Time-Out errors occur when the Team Foundation Server application and database tiers are separated by many network hops.

In this release, high latency between the Team Foundation Server application and database tiers may cause time-out errors when you are trying to transfer large files between the two tiers.

To resolve this issue

Minimize the number of network hops between the Team Foundation Server application and the database tiers.

2.3    Installing SQL Server 2005 using the provided answer file fails on non-English editions of Windows Server 2003.

When you use the provided answer file to install SQL Server 2005, you may receive the following error:

"SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account."

To resolve this issue

The answer file provided with Team Foundation Server contains English user account names that will cause setup to fail on non-English editions of Windows Server 2003. Modify the answer file to use the correct localized names for the specified accounts.

2.4   Error 32000 (ConfigureNTLM.exe /addntlm "Team Foundation Server" returned non-zero value: 1) during Team Foundation Server setup.

If you install Team Foundation Server on a server that is already using TCP port 8080, Team Foundation Server setup will fail because this port is required for the Team Foundation Server Web site, even if the Web site on port 8080 is stopped during setup.

To resolve this issue

Make sure TCP port 8080 is not already being used before you install Team Foundation Server. Delete all Web sites bound to port 8080 or change their port number.

2.5    Error 32000 (ConfigureNTLM.exe /addntlm "Team Foundation Server" returned non-zero value: 1) during Team Foundation Server Proxy setup.

If you install Team Foundation Server Proxy on a server that is already using TCP port 8081, setup will fail, even if the Web site on port 8081 is stopped during setup.

To resolve this issue

Make sure TCP port 8081 is not already being used before you install Team Foundation Server Proxy. Delete all Web sites bound to port 8081 or change their port number.

2.6    Error 28918 TFServerStatusValidator: ErrorMakingWebServiceCall when you run Team Foundation Server (services) Setup.

When you run Team Foundation Server (services) Setup, you may receive the following error:

Error 28918.TFServerStatusValidator: ErrorMakingWebServiceCall - the tool did not succeed calling Tfs Registration Web service. Either IIS is not running or is not configured correctly.

The default settings for the URLScan Security Tool installed on IIS can cause this error. If the URL contains more than one period, such as http://localhost:8080/services/v1.0/registration.asmx), URLScan rejects the request.

To resolve this issue

Configure the URLScan Security Tool in the urlscan.ini file to allow for multiple periods in requested URLs by setting AllowDotInPath=1. For more information, see How to configure the URLScan Tool.

2.7   Entering a password with Unicode characters may cause setup to fail.

Although some Unicode characters are allowed in Windows passwords, Team Foundation Server setup may fail if Unicode characters are used in passwords.

To resolve this issue

Do not use Unicode characters in passwords.

2.8   Documentation is outdated or displays pre-release content.

If you previously installed MSDN Library for Visual Studio 2005 or if you use locally installed Help for Team Foundation or Team Explorer as the primary source of documentation, you might have outdated or missing Help documentation.

To resolve this issue

Download and install the most recent edition of MSDN Library to make sure that you have the latest product documentation for Team Foundation and Team Explorer.

2.9   When working through the installation checklist, use the answer files for SQL Server 2005 installation.

The most efficient way to install SQL Server 2005 is to use the answer files instead of the installation wizard.

To resolve this issue

For single server installation, see the answer file procedure in “How to: Install Microsoft SQL Server 2005 for Team Foundation Server (Single-Server Deployment)” in the Installation Guide.

For the data-tier of a dual server installation, see the answer file procedure in “How to: Install Microsoft SQL Server 2005 for Team Foundation Server (Dual-Server Deployment)” in the Installation Guide. For the application-tier of a dual server installation, see the answer file procedure in “How to: Install Microsoft SQL Server 2005 Reporting Services for Team Foundation Server (Dual-Server Deployment)” in the Installation Guide.

2.10   Error 28100: Error loading Event Web service when you install Team Foundation Server.

Setup was unable to confirm the application-tier server name. In the MSI log, you find the following entry: "Failed to load EventService proxy object: TF30076: The server name provided does not correspond to a server URI that can be found. Confirm that the server name is correct."

To resolve this issue

Open the registry and delete the registry key HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers, and then restart setup.

2.11    Changing service accounts after installation of Team Foundation Server can cause installation failure. 

If you find that you must change the service accounts you provided during a previous installation of Team Foundation Server, make the changes using the security setting options available in Team Explorer or using the TFSAdminUtil command-line utility before you uninstall Team Foundation Server. Changing the service accounts using tools other than those provided with Team Foundation Server could lead to unexpected results. For example, changes to the accounts using Windows Services Manager and Internet Information Services (IIS) Manager are not automatically registered in Team Foundation Server.

To resolve this issue

We recommend that you change the accounts after reinstalling or repairing Team Foundation Server if it is possible. If you must change the accounts when Team Foundation Server uninstalled, create the accounts and then update the service accounts for the application pools of Windows SharePoint Services and Report Server. You can use Internet Information Services (IIS) Manager to update the application pools.

We recommend that you use domain accounts for the service accounts. If you chose a single-server deployment and you must use local accounts, make sure that you include the prefix "machine\" before the account name. For example, the Installation Guide uses "domain\TFSSERVICE" as a placeholder for the services account. If you want to change to a local account by that name, you must specify the prefix "

2.12   Moving the Internet Information Services (IIS) root directory from the Inetpub folder to another folder causes Error 32000.

Installation of Team Foundation Server fails with Error 32000. "The Commandline D:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe ...' returned non-zero value: -2130242250." because the Windows SharePoint Services administration site is not setup and Team Foundation Server cannot configure the site.

The site should be set up during installation of Windows SharePoint Services but if the Internet Information Services (IIS) root directory was moved from the Inetpub folder to another folder and the AdminScripts subfolder was not included in the move, the setup fails silently.

To resolve this issue

  1. Uninstall Windows SharePoint Services.
  2. Move the AdminScripts subfolder from the Inetpub folder to the new root directory for IIS.
  3. Re-install Windows SharePoint Services.
  4. Re-install Team Foundation Server.

2.13   Unable to install the application tier across domains that have the firewall enabled on the data tier.

System Health Check uses remote Windows Management Instrumentation (WMI) when you install the application tier. WMI requires that the remote administration port be open on the data tier. If this port in not open, you receive warnings that the data tier does not appear to be correctly configured.

To resolve this issue

Verify that the port is open on the data tier and then continue past the System Health check. If you have the Microsoft Firewall enabled, the data-tier setup opens the required ports for Team Foundation Server to operate correctly.

2.14   Unable to re-install because of service accounts.

When you uninstall Team Foundation Server and then try to reinstall on a single server or on the application-tier of a dual-server deployment, you must use the same service account that was used to install originally.

To resolve this issue

To determine the service account that was used, open Services Manager, sort by “Log on as,” and then locate the services for Team Foundation Server at the bottom of the list. Examine the “Log on as” value for the services at the bottom; such as TFSServerScheduler. That value indicates the service account you must specify during the re-installation.

2.15   Unable to install because of the Reporting Services application pool.

Setup has detected a SQL Server 2005 Reporting Services IIS application pool on this computer and cannot continue.

To resolve this issue

Before running setup again, remove the Reporting Services application pool by opening Internet Information Services Manager, expanding the Application Pool node, and then deleting the pools for Reporting Services.

2.16   Unable to install because of insufficient "Log on as a service" permissions.

The service accounts must have the "Log on as a service" permission set to Allow.

To resolve this issue

Verify that "Log on as a service" is allowed for both service accounts.

  1. On the Start menu, click Control Panel, click Administrative Tools, and then click Local Security Policy.
  2. Expand Security Settings, click Local Policies, and then click User Rights Assignments.
  3. In the details pane, locate and double-click Log on as a service.
  4. In Log on as a service Properties, locate the services you have specified for Team Foundation Server. For example, this guide uses the placeholders domain/tfsservice and domain/tfsreports for the service accounts.

2.17   Installation fails when the default Web site is configured to require a secure channel (SSL), with error code: 28804 or 28805.

Team Foundation Server single- or dual-server (application tier) install fails with error code 28804 or 28805. Further inspection of the installation logs will indicate that the problem occurred with the CreateDS custom action, and that the “operation you are attempting requires a secure connection (HTTPS).” This is probably due to Report Server being automatically configured to require SSL connections when an SSL certificate is required for the default Web site. Team Foundation Server installation cannot automatically configure the server for SSL-only connections. This is a post-install configuration operation.

To resolve this issue

For single server, open %ProgramFiles%\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportServer\RsReportServer.config. Change the "SecureConnectionLevel" value from “2” to “0.” On the Team Foundation Server installation error dialog box, click Retry, or restart the installation.

For dual server, click Cancel. Go to IIS manager and configure the default Web site so that it does not require a secure channel (SSL) connection, and then re-run the application tier installation.

2.18   TF53011 error when upgrading Team Foundation Server from trial to workgroup edition.

After upgrading from the trial edition to the workgroup edition, trying to connect to the server from Team Explorer causes a TF53011 error: "The Team Foundation Server returned the following error: The request failed with HTTP status 403: TF53011: domain\user is not a licensed user...". This error appears because upgrading from trial to workgroup edition does not create the Licensed Workgroup Users group.

To resolve this issue

After upgrading to workgroup edition, re-run the Team Foundation Server setup (application tier installation or single server installation), in repair mode.

2.19   Using different versions of SQL Server on a two server install may cause setup to fail.

If you use different editions of SQL Server on the data tier and application tier, some combinations (for example, SQL Standard on the application tier and SQL Developer on the data tier) may cause setup failure.

To resolve this issue

Use the same edition of SQL on both the application tier and data tier machines in a two server configuration.

2.20   Using a 64-bit operating system to run Team Foundation Server and SQL Server 2005.

Team Foundation Server needs SQL Server 2005 (64-bit) installed on a 64-bit operating system. If SQL Server 2005 (32-bit) is installed on a 64-bit operating system, the System health check for the Team Foundation Server data tier setup will fail.

To resolve this issue

Use SQL Server 2005 (64-bit) on a 64-bit operating system.

2.21   Reinstalling the Team Foundation Server application tier after uninstalling and reinstalling the data tier causes an error.

Uninstalling and reinstalling the Team Foundation Server data tier does not add the required registration stored procedure to the Team Foundation Server Integration database, which causes the application tier installation to fail.

To resolve this issue

Repairing the Team Foundation Server data tier installation will insert the required stored procedures, allowing the application tier to install successfully.

2.22   Final Installation Page for Team Foundation Server Proxy Contains Misleading Information.

The Web page that appears after installing Team Foundation Server Proxy contains incorrect information. In the XML example for configuring the proxy, an extra space appears in the value for the Uri element of the Server node of the proxy.config file, http:// TeamFoundationServerName:8080/VersionControl. The product name is also incorrectly listed as Team Foundation Version Control Proxy.

To resolve this issue

When you open the proxy.config file, you can copy the example, but be sure to remove the extra space after http://. For more information about configuring the proxy, see "How to: Enable Source Control Caching for Team Foundation Server Proxy" in the Team Foundation Server Administrator's Guide.

3. Microsoft® .NET Framework 2.0

3.1   Installing Windows Server 2003, installing .NET Framework 2.0, and then upgrading to Windows Server 2003 SP1 using a full CD breaks .NET Framework 2.0 applications.

Upgrading using a CD with the full Windows Server 2003 SP1 installation, replaces the shared file mscoree.dll on a computer that has the .NET Framework 1.1 mscoree.dll file.

Any applications compiled against the .NET Framework 2.0 will not run after the service pack is installed.

Note   This does not occur when updating Windows Server 2003 with just the service pack. This is a problem when you upgrade with a CD that contains Windows Server 2003 and Windows Server 2003 SP1 bundled together.

To resolve this issue

After you install the Service Pack, the .NET Framework must be repaired.

1.      In Control Panel, open Add or Remove Programs.

2.      Select Microsoft .NET Framework 2.0.

3.      Click Change/Remove.

4.      When the Change/Remove dialog box appears, click Repair, and then click Next.

5.      If prompted to restart, restart the computer.

4. Microsoft® Office Primary Interop Assemblies

4.1  Installing the Required Primary Interop Assemblies

Certain Visual Studio features require the presence of the following primary interop assemblies (PIAs):

  1. Microsoft Office Excel 2003†‡
  2. Microsoft Office Word 2003†
  3. Microsoft Office Outlook 2003†
  4. Microsoft Forms 2.0†
  5. Microsoft Graph†
  6. Smart Tag†
  7. Microsoft Office Project 2003†‡

† Required for creating Microsoft Visual Studio Tools for the Microsoft Office System projects. When you create an Office project, Visual Studio tries to install any required PIAs that are not installed. If the PIAs were not set to “Installed on first use” during Office installation, you might need the Office installation media and administrative rights to install them. You can now either create Excel, Word, and Outlook projects or manually install the PIAs (see in the following section).

‡ Required for Microsoft Office integration with Visual Studio 2005 Team Explorer.

To manually install the required Primary Interop Assemblies (PIAs)

You can manually install the PIAs by following these instructions if you are running a full edition of Office 2003. Follow similar steps for stand-alone versions of Excel, Outlook and Word, but note that not all the PIAs are available.

1.      In Control Panel, open Add or Remove Programs.

2.      Make sure that Change or Remove Programs is selected.

3.      Select Microsoft Office in the Currently installed programs list.

4.      Click Change.

5.      Select Add or Remove Features and then click Next.

6.      Select Choose advanced customization of applications and then click Next.

7.      Expand Microsoft Office Excel, select the option for .NET Programmability Support, and then click Run from My Computer.

8.      Expand Microsoft Office Outlook, select the option for .NET Programmability Support, and then click Run from My Computer.

9.      Expand Microsoft Office Word, select the option for .NET Programmability Support, and then click Run from My Computer.

10.  Expand Office Tools, select the option for Microsoft Forms 2.0 .NET Programmability Support, and then click Run from My Computer.

11.  Select the option for Smart Tag .NET Programmability Support and then click Run from My Computer.

12.  Under Office Tools, expand Microsoft Graph, select the option for .NET Programmability Support, and then click Run from My Computer.

13.  Click Update.

14.  Click OK.

15.  Select Microsoft Project in the list of programs installed and then click Change.

16.  Select Add or Remove Features and then click Next.

17.  Expand Microsoft Office Project for Windows, select the option for .NET Programmability Support, and then click Run from My Computer.

18.  Click Update.

19.  Click OK.

Top of Page

Page view tracker