Skip to main content

Team Foundation Server Service Pack 1 Beta Readme

Visual Studio Team System 2008 T

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.

  1. In Control Panel, open Add or Remove Programs.
  2. Select Visual Studio 2008.
  3. Click Change/Remove.
  4. 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:

  1. After the computer has restarted, in Add Remove Programs, uninstall Windows SharePoint 3.0.
  2. Run Team Foundation Server setup again and select to install Windows SharePoint 3.0 as part of the setup.
1.3.5   In some localized versions of Microsoft SharePoint, the default SharePoint Web site is
different than Team Foundation Server expects.

If either a German or Italian version of Microsoft SharePoint was installed on a Microsoft Windows 2008 Standard Server computer before Visual Studio 2008 Team Foundation Server was installed, Team Foundation Server cannot locate the default SharePoint Web site.

The following error message is displayed: TF220041 The specified Windows SharePoint Service URL (http://servicename) is not the default site collection site: ().

To resolve this issue:

If you are installing Visual Studio 2008 Team Foundation Server on Windows Server 2008, you must specify an existing deployment of SharePoint Products and Technologies.

To find the default collection site for the existing SharePoint deployment, follow these steps:

  1. On the application-tier server, open a browser window.
  2. Type http:’’<server_name>:17012. Where 17012 is the default port for SharePoint Central Administration.
  3. On the Central Administration page, click the Application Management tab.
  4. In the Application Management tab, click Site collection list to display the URLs of the site collections.

The Site Collection List page is displayed in the Application Management tab.

Note   You must be a SharePoint administrator to complete this procedure.

1.3.6   Integrate the installation of Team Foundation Server and Service Pack 1.

You must integrate the installation of Visual Studio Team System 2008 Team Foundation Server and Service Pack 1 under the following circumstances:

  • Your data-tier server is running Microsoft SQL Server 2008. In this environment, installation will fail if you try to install Team Foundation Server without SP1. 
  • Your application-tier server is running Windows Server 2008 and you want to automatically install and configure Windows SharePoint Services 3.0 when you install Team Foundation Server. In this environment, the option to automatically configure Windows SharePoint Services 3.0 will be unavailable if you install Team Foundation Server without SP1.
  • You want to update a build server that has more than 1,000 build cases that were migrated from Visual Studio 2005 Team Foundation Server.

To resolve this issue:

You can integrate the installation files of Service Pack 1 and Visual Studio Team System 2008 Team Foundation Server.  For more information, see "How to: Integrate the Installation of Team Foundation Server and Service Pack 1" in the Team Foundation Installation Guide.

1.3.7   You may need to update the client components of Team Foundation Server with
Microsoft Visual Studio 2008 Service Pack 1 Beta.

When you install SP1 for Visual Studio Team System 2008 Team Foundation Server, you update the server components of Team Foundation. To update the client components such as Team Explorer, you install Microsoft Visual Studio 2008 Service Pack 1 Beta.

To resolve this issue:

You must download and install these service packs separately. You must install Microsoft Visual Studio 2008 Service Pack 1 Beta under the following circumstances:

  • The client component must connect to a deployment of Team Foundation Server that uses SQL Server 2008. If you do not update the client, it will not be able to connect to that deployment.
  • The client component is installed on an application-tier server for Team Foundation, on which SP1 for Team Foundation Server has been or will be installed. If you install only one of these service packs, you will create an unsupported configuration.

Important Note: You must install Microsoft Visual Studio 2008 Service Pack 1 Beta before you install SP1 for Team Foundation Server. Otherwise, you will not be able to install SP1 for Team Foundation Server.

For example, you should first install Microsoft Visual Studio 2008 Service Pack 1 Beta and then install SP1 for Team Foundation Server on any server that is running both Team Foundation Server and Team Explorer. If you update Team Foundation Server first, you will not be able to update Team Explorer. If you update Team Foundation Server but not Team Explorer, you will encounter errors if you try to use that installation of Team Explorer to perform certain administrative tasks on Team Foundation Server.

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.2.2   The Visual SourceSafe converter tool (VSSConverter.exe) checks for a
Visual SourceSafe hotfix that is not installed.

When you start migrating source files by running VSSConverter.exe, you are prompted with a message that indicates that you must update Visual SourceSafe, and that you should install the update before you proceed. This message references KB article 950185 which is not yet released.

To resolve this issue:

Ignore the message and continue migrating source files without installing the update. When prompted, select 'Y' to continue without the Visual SourceSafe hotfix.

2.3 Office Integration

2.3.1   You receive an error when you open work items in
Microsoft Excel or Microsoft Project.

If you install Visual Studio 2008 Team Explorer and then install Visual Studio 2005 Team Explorer (in that order), the Microsoft Excel and Microsoft Project add-ins for both versions are registered and you may observe one or more of the following issues:

  • When opening a Microsoft Excel file from a Windows SharePoint document library, you see the following error: "Team Foundation could not insert the work item list because adding it at the selected location exceeds the row or column limitations in Microsoft Excel. Select a location where there is enough space to insert the list."
  • You see duplicate menu entries in Microsoft Excel and Microsoft Project.
  • When opening a selection of work items from Team Explorer into Microsoft Excel or Microsoft Project, you see the following error: "TF80076: The data in the work item is not valid or you do not have permissions to modify the data. Please correct the problem and retry."

To resolve this issue:

Unregister one of the add-ins using one of the following procedures:

To use the Visual Studio 2008 Team Explorer add-in

1.     At the command prompt, change directories to:
        C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

2.     Unregister the Visual Studio 2005 Team Explorer add-in by running the following command:
        regsrv32 /u TFSOfficeAdd-in.dll

3.     At the command prompt, change directories to:
        C:\Program Files\Microsoft Visual Studio 9\Common7\IDE\PrivateAssemblies\

4.     Register the Visual Studio 2008 Team Explorer add-in by running the following command:
        regsrv32 TFSOfficeAdd-in.dll

To use the Visual Studio 2005 Team Explorer add-in

1.     At the command prompt, change directories to:
        C:\Program Files\Microsoft Visual Studio 9\Common7\IDE\PrivateAssemblies\

2.     Unregister the Visual Studio 2008 Team Explorer add-in by running the following command:
        regsrv32 /u TFSOfficeAdd-in.dll

3.     At the command prompt, change directories to:
        C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PrivateAssemblies\

4.     Register the Visual Studio 2005 Team Explorer add-in by running the following command:
        regsrv32 TFSOfficeAdd-in.dll

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.

  1. In Control Panel, open Internet Options.
  2. On the Security tab, click Local Intranet, and then click Custom Level. The Security Settings dialog box appears.
  3. In the User Authentication section, under Logon, select Prompt for user name and password, and then click OK.
  4. 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:

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

2.6 Team Explorer

2.6.1   If you are not a Team Foundation Administrator, the
New Team Project wizard does not work on a Visual Studio Team System client in Windows Server 2008.

Team project creation fails if you run the New Team Project wizard in Windows Server 2008 when Windows SharePoint Server 3.0 is installed on the same server.

To resolve this issue:

Do not run a Visual Studio Team System client (such as Team Explorer) on the same computer where Windows SharePoint Server 3.0 is installed.

If you run a Visual Studio Team System client on the same computer as Windows SharePoint Server 3.0, you must run the applications in the Administrator mode.

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.

2.8 Test Integration

There are no known issues.

2.9 Version Control

There are no known issues.