Team Foundation Server Readme

Team System Developer Center > Downloads > Team Foundation Server Readme

Team Foundation Server Readme

This is the readme for the released version of Team Foundation Server. For the Service Pack 1 version of the readme, see Team Foundation Server Service Pack 1 Readme.

1. Installation Issues
1. 1.1 System Requirements
2. 1.2 Prerequisites
3. 1.3 Installing
4. 1.4 Uninstalling
2. Product Issues
1. 2.1 Administration
2. 2.2 Converters
3. 2.3 Office Integration
4. 2.4 Process Templates and Team Project Portal
5. 2.5 Reporting
6. 2.6 Team Explorer
7. 2.7 Team Foundation Build
8. 2.8 Test Integration
9. 2.9 Version Control
3. Related Links

1. Installation Issues

1.1 System Requirements

The system requirements for Team Foundation Server and Team Explorer are located in the Team Foundation Installation Guide.

1.2 Prerequisites

There are no known issues.

1.3 Installing

1.3.1. Installation of SQL Server on Windows 7 RC generates a compatibility warning

When you try to install SQL Server 2008 RTM or SQL Server 2005 RTM/SP1/SP2 on Windows 7 RC, you may receive a warning that SQL Server has known compatibility issues with this version of Windows. Because SQL Server is redistributed by Visual Studio, installations in which the user selects to install SQL Server together with Visual Studio may be affected. The issues that trigger the compatibility warning have been fixed in SQL Server 2008 SP1 and SQL Server 2005 SP3.

To resolve this issue:

Install Visual Studio 2008 and select to install SQL Server 2005 Express Edition SP2 (selected by default).

1. During installation, click “Run Program” when you receive the compatibility warning.

2. After installation is completed, download and install SQL Server 2005 Express Edition SP3 here. (NOTE: The x64 version is located near the bottom of the page.)

3. During SQL Server 2005 Express Edition SP3 setup, make sure to upgrade the already installed instance.

4. You can verify your version of SQL Server 2005 Express Edition by following the instructions here.

As an alternative, you can install SQL Server 2005 Express Edition SP3 before you install Visual Studio 2008.

More Information:

If you have to install SQL Server 2008 on Windows 7 RC and want to avoid the warning messages, you can create the SQL Server 2008 with Service Pack 1 package yourself. Follow the steps described by Peter Saddow: Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

1.3.2 E-mail notification settings are removed when you upgrade to Visual Studio Team System 2008 Team Foundation Server.

E-mail notification settings in the server's web.config file are cleared when you upgrade from Visual Studio 2005 Team Foundation Server to Visual Studio Team System 2008 Team Foundation Server. This file is located at %PROGRAMFILES%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services\web.config. This causes all users to stop receiving e-mail notifications from Team Foundation Server after the upgrade. To resolve this issue: Before you upgrade, open the file located at %PROGRAMFILES%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\Services\web.config and record the values of the following elements:

<add key="emailNotificationFromAddress" value="" /> <add key="smtpServer" value="" />

The upgrade clears these values. After you have completed the upgrade, modify the file located at %PROGRAMFILES%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services\web.config and type the values that you had previously recorded.

1.3.3 JavaScript IntelliSense, coloring and syntax validation may not work in Visual Studio 2008 after installing Visual Studio Team Explorer.

If you install Visual Studio Team Explorer after you install Visual Studio 2008 and JavaScript IntelliSense, coloring and syntax validation in Visual Studio 2008 might become unavailable. This is caused by a setup conflict for the JavaScript authoring component.

To resolve this issue:

Repair the Visual Studio 2008 installation by running the setup again. This will restore the JavaScript functionality in Visual Studio 2008.

In Control Panel, open Add or Remove Programs.
Select Visual Studio 2008.
Click Change/Remove.
When the Change/Remove dialog box appears, click Repair, and then click Next.

1.3.4 Windows SharePoint Services 3.0 may restart the computer during Team Foundation Server setup.

If you install Team Foundation Server and select Windows SharePoint Services 3.0, SharePoint might initiate a computer restart during the Team Foundation Server installation. If this happens, Team Foundation Server installation does not resume automatically. If you run setup manually, the SharePoint configuration page will stop responding.

To resolve this issue:

After the computer has restarted, in Add Remove Programs, uninstall Windows SharePoint 3.0.
Run Team Foundation Server setup again and select to install Windows SharePoint 3.0 as part of the setup.

1.4 Uninstalling

There are no known issues.

2. Product Issues

2.1 Administration

2.1.1 Running TFSAdminUtil ChangeAccount disables Visual Studio Team Foundation Server Task Scheduler.

After you run TFSAdminUtil changeaccount to change service accounts, the Visual Studio Team Foundation Server Task Scheduler will stop working.

In Visual Studio Team System 2008 Team Foundation Server, the TFSAdminUtil changeaccount command does not change Access Control Lists (ACL's) on the file system. Therefore, a new service account that you create by using the Changeaccount command will not have the required access to the %windows%\temp folder. Access to this folder is needed for Visual Studio Team Foundation Server Task Scheduler to start.

To resolve this issue:

You must grant Read and Execute, List Folder Contents, Read, and Write permissions to the new service account for the %windows%\temp folder.

2.2 Converters

2.2.1 VSSConverter may not be able to correctly migrate files that reside in folders that have been renamed in Visual SourceSafe.

When a file or folder in Visual SourceSafe has a namespace change in its history, VSSConverter may be unable to migrate the data correctly. Editing events such as rename, archive and restore, sharing, branching, and move can create namespace conflicts in the Visual SourceSafe history. These conflicts result in files and folders not being migrated correctly. This problem can be identified if there are missing versions of converted files, or missing files from the conversion. In the log file or in the migration report, you will see the following errors: "The item already exists." and "The item could not be found in the workspace." This bug exists both in Visual Studio 2005 Team System and in Visual Studio Team System 2008.

To resolve this issue: In some cases, changing the mappings in the settings file can help to migrate files correctly. If the missing versions are located, the mappings can be changed to a subfolder. For example, the mappings:

<ProjectMap> <Project Source="$/Projects/ProjA" Destination="$/TFSProjects/ProjA" /> </ProjectMap>

Can be changed to:

<ProjectMap> <Project Source="$/Projects/ProjA/SubFolder1" Destination="$/TFSProjects/ProjA/SubFolder1" /> <Project Source="$/Projects/ProjA/SubFolder2" Destination="$/TFSProjects/ProjA/SubFolder2" /> <Project Source="$/Projects/ProjA/SubFolder3" Destination="$/TFSProjects/ProjA/SubFolder3" /> </ProjectMap>

Once these mappings are changed in the settings file, VSSConverter can be run again. If some of the files are still not migrated correctly, the data will not be migrated by VSSConverter.

2.3 Office Integration

2.3.1 Setting the ProjectField in the SyncField mapping to a field that is already being used, prevents publishing work items from Microsoft Project.

If the field used for the SyncField mapping is already being used in another one, you will not be able to publish any work items from Microsoft Project. Also, Microsoft Project will display incorrect values in the Publish and Refresh and other drop-down lists.

For example, if you use pjTaskText25 for both the System.Reason field and the SyncField mappings:

<Mapping WorkItemTrackingFieldReferenceName="System.Reason" ProjectField="pjTaskText25" /> <SyncField ProjectField="pjTaskText25" />

And then use TFSFieldMapping.exe to upload the mappings to Team Foundation Server, Microsoft Project will not be able to properly display the mapped fields.

To resolve this issue:

Before you upload the mappings for a team project, verify that the field used in the SyncField mapping is not already mapped.

2.3.2 You receive an error when opening query results or a selection of work items in Microsoft Excel or Microsoft Project after you uninstall a version of Team Explorer.

If you installed both Visual Studio 2005 Team Explorer and Visual Studio 2008 Team Explorer, and then uninstall one of the versions, the remaining version of Microsoft Excel and Microsoft Project add-ins will be unusable. You will see the following error message when you open query results or a selection of work items in Microsoft Excel or Microsoft Project:

TF80012: The document cannot be opened because there is a problem with the installation of the Microsoft Visual Studio 2008 Team Foundation Office integration components. Please see the Team Foundation Installation Guide for more information.

To resolve this issue: Repair the installation of Team Explorer by using the following procedure.

Open the Control Panel.
If you are using Microsoft Visual Studio 2008 Team Explorer select this entry in the control panel. Otherwise select Microsoft Visual Studio 2005 Team Explorer.
Click Change/Remove.
In the Setup dialog box, select Repair or Reinstall.
Click Next.
On the Ready to Repair page, click Repair.

2.4 Process Templates and Team Project Portal

There are no known issues.

2.5 Reporting

2.5.1 Credentials are not persisted when a user wants to access reports and use Team Foundation Server in a single-server, workgroup deployment.

When you visit the reporting Web site in a single-server, workgroup deployment of Team Foundation Server, you are prompted for credentials on the first visit. On subsequent visits, you receive no prompt for credentials and you cannot view reports. To resolve this issue: Configure Internet Explorer to always prompt for username and password in the Local Intranet Zone.

In Control Panel, open Internet Options.
On the Security tab, click Local Intranet, and then click Custom Level. The Security Settings dialog box appears.
In the User Authentication section, under Logon, select Prompt for user name and password, and then click OK.
In the Internet Options dialog box, click OK, and then restart Internet Explorer.

2.5.2 There are no dates on the X-axis when you examine the following reports: Bug Rates, Reactivations, Remaining Work, Unplanned Work.

When the Internet Explorer language settings differ from the Team Foundation Server product language, dates on the X-axis are not displayed.

To resolve this issue: Change the language settings of Internet Explorer to match the language used for Team Foundation Server. To change the language used by Internet Explorer:

In Internet Explorer, click the Tools menu, and then click Internet Options.
Click Languages.
Click Add and then select the same language used by Team Foundation Server.

2.6 Team Explorer

There are no known issues.

2.7 Team Foundation Build

2.7.1 Connection attempt fails when running remote tests from Team Foundation Build.

Running remote tests from Team Foundation Build fail with the following error: "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host failed."

When you run remote tests from Team Foundation Build, the user account used to run the build must be a member of the TeamTestControllerUser or TeamTestControllerAdmins local security accounts on the Team Test Load Agent controller computer. Also, if you use Windows Firewall (or another third-party firewall solution), MSBuild must be able to access the remote computers.

To resolve this issue:

Add the user account used to run the build to the TeamTestControllerUser or TeamTestControllerAdmins local security account on the Team Test Load Agent controller computer. Also, add MSBuild to the Windows Firewall (or other third-party firewall solution) exceptions list on the Team Foundation Build computer.