For the latest version of the Readme click here.
When you upgrade from Team Foundation Server 2010 Beta2, the command IISRESET may fail with "The system cannot find the file specified". This is caused by a known issue when upgrading the "Microsoft .NET 4 Framework Client Profile" program from Beta2 to Release.
To resolve this issue:
Repair the Microsoft .NET Framework 4 Client Profile by doing the following:
1. In Control Panel, open Programs and Features.
2. Click "Microsoft .NET Framework 4 Client Profile".
3. Click "Uninstall/Change".
4. Choose "Repair .NET Framework Client Profile to its original state."
5. Click Next to start the repair.
System Requirements: Team Foundation Server 2010 is not supported on operating systems that were installed with the "Server Core" option.
To resolve this issue:
Customers should install the full server operating system and not the "Server Core" option when they install the Windows operating system. See the online installation for a complete list of system requirements.
Before installing Team Foundation Server 2010, use the following commands to remove the event log registry keys on computers where pre-release versions of Team Foundation Server 2010 have been installed.
After installing Team Foundation Server 2010, Event Log entries will be missing Team Foundation Server specific description text on computers where a pre-release (Beta2 or RC) version of Team Foundation Server 2010 had previously been installed. Instead you will see the following text: "The description for Event ID 9010 from source TFS Services cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer."
To resolve this issue:
Remove the Team Foundation Server specific registry keys before installing Team Foundation Server 2010. Use Notepad to create a batch file that contains the following commands to remove the registry keys, and run this batch file from a Command Prompt window with elevated permissions:
@echo off
set CURRENT_CTL=HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application
reg delete "%CURRENT_CTL%\Team Build Service" /f
reg delete "%CURRENT_CTL%\Team Foundation Error Reporting" /f
reg delete "%CURRENT_CTL%\Team Web Access" /f
reg delete "%CURRENT_CTL%\TFS Build" /f
reg delete "%CURRENT_CTL%\TFS Deployment Rig" /f
reg delete "%CURRENT_CTL%\TFS Lab Management" /f
reg delete "%CURRENT_CTL%\TFS Proxy Server" /f
reg delete "%CURRENT_CTL%\TFS Scheduler" /f
reg delete "%CURRENT_CTL%\TFS Services" /f
reg delete "%CURRENT_CTL%\TFS Test Management" /f
reg delete "%CURRENT_CTL%\TFS Test Rig" /f
reg delete "%CURRENT_CTL%\TFS Version Control" /f
reg delete "%CURRENT_CTL%\TFS Warehouse" /f
reg delete "%CURRENT_CTL%\TFS WorkItem Tracking" /f
reg delete "%CURRENT_CTL%\VSTF Coverage Analysis" /f
reg delete "%CURRENT_CTL%\VSTF Test Tools Adapter" /f
reg delete "%CURRENT_CTL%\TFSJobAgent" /f
Acceptable output from each of the above "reg delete" commands will be either: "The operation completed successfully." Or "ERROR: The system was unable to find the specified registry key or value."
During initial configuration of Team Foundation Server, with the Advanced or Standard wizards, you may encounter the following error message "TF252031: A SharePoint site could not be created for the team project collection. The following error occurred: Server was unable to process request. ---> Exception from HRESULT: 0x80040E09" during the creation of the first team project collection. This error will occur if the TCP/IP protocol is disabled in SQL Server (this protocol is disabled by default for SQL Server Developer Edition and SQL Server Trial Edition).
To resolve this issue:
Enable the TCP/IP protocol for SQL Server. For a step-by-step walkthrough of this process, refer to the "How to: Verify SQL Server 2008" topic in the installation guide for Team Foundation.
If you are upgrading or patching Team Foundation Server with SQL mirroring enabled, additional steps are required.
To resolve this issue:
See the following page on the Microsoft Web site:
http://go.microsoft.com/fwlink/?LinkId=186754
There are no known issues.
Chinese Minority Characters are supported in Project/Collection names only in Team Foundation Server Basic (provided a proper SQL Collation is selected).
Even if you select an appropriate SQL collation for the Team Foundation Server full product, SharePoint Products and SQL Server Reporting Services do not support Chinese Minority Scripts in metadata. Therefore, Team Foundation Server cannot support those characters when relying on SQL Server Reporting Services or SharePoint Products.
To resolve this issue:
Use a Team Foundation Server Basic configuration, with a properly (and manually) configured SQL collation that supports Chinese Minority Scripts.
Team Foundation Server Basic does not use SharePoint Products or SQL Server Reporting Services, which is why Chinese minority characters are supported in this case.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
There are no known issues.
This issue occurs only when using a Team Explorer 2010 client to modify permissions on Team System 2008 Team Foundation Server. When users select the "Inherit security settings" check box on the "Security" tab of the "Properties" dialog box for an item in version control, some users may hit a condition that results in a null reference exception. This null reference is the result of a pre-existing condition with out of sync identities that some instances of Team System 2008 Team Foundation Server may exhibit. If this null reference is hit while modifying permissions, the state of permissions displayed in the "Security" tab may be inaccurate. Clicking "OK" to save the permissions changes may then result in permissions being set that differ from what the user expected. Clicking "Cancel" on the dialog box will result in no changes being applied to the permissions.
To resolve this issue:
Use Team Explorer for Visual Studio Team System 2008 to modify version control permissions for Team System 2008 Team Foundation Server.
Many customers may need to connect to Team Foundation Server 2010 from Team Explorer for either Visual Studio 2005 or Visual Studio Team System 2008. Several features in Team Foundation Server 2010 exceed the capabilities of earlier versions of Team Explorer.
To resolve this issue:
Install an update that enables Team Explorer for Visual Studio Team System 2008 to perform scenarios as it did for earlier versions of Team Foundation Server.
To download this update, see the following page on the Microsoft Web site: Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010 (Installer).
To download an update for Team Explorer for Visual Studio 2005, see the following page on the Microsoft Web site: Visual Studio Team System 2005 Forward Compatibility Update for Team Foundation Server 2010 interoperability
For a description of the scenarios that this update supports, see the following page on the Microsoft Web site: Compatibility Matrix for 2010 Team Foundation Server to Team Explorer 2008 and 2005.
Customers cannot connect to Team Foundation Server 2010 without a newer client or an earlier client with a Forward Compatibility Update. If a customer uses an earlier client to add a server that is running Team Foundation Server 2010, an error message appears, but it does not specify that the customer needs a Forward Compatibility Update.
To resolve this issue:
If you are using Team Explorer for Visual Studio Team System 2008, you can install the Forward Compatibility Update for that client from the following page on the Microsoft Web site: Visual Studio Team System 2008 Service Pack 1 Forward Compatibility Update for Team Foundation Server 2010 (Installer).
If you are using Team Explorer for Visual Studio 2005, you can install the Forward Compatibility Update for that client from the following page on the Microsoft Web site: Visual Studio Team System 2005 Forward Compatibility Update for Team Foundation Server 2010 interoperability.
Team project collections, new to Team Foundation Server 2010, change the path to the server.
To resolve this issue:
Use the full path in the server field. Example connection string looks like: http://myserver:8080/Collection1 or http://server:8080/tfs
For more information about compatibility, see the following page on the Microsoft Web site: Compatibility Matrix for 2010 Team Foundation Server to Team Explorer 2008 and 2005.
The customer may not know whether they were successful.
To resolve this issue:
The customer can check Build Explorer (just like in Team Explorer 2010) or use the build notification applet (Visual Studio Team System 2008 Team Foundation Server power tools release rather than Team Foundation Server 2010 release).
For more information about compatibility, see the following page on the Microsoft Web site: Compatibility Matrix for 2010 Team Foundation Server to Team Explorer 2008 and 2005.
New build definitions will be automatically upgraded to Team Foundation Server 2010 build definitions using the upgrade build process template, so users of Team Explorer for Visual Studio Team System 2008 or older clients will not be able to edit them.
To resolve this issue:
Use Team Explorer 2010 to edit build definitions. Alternatively, you can use a text or XML editor to edit the build process template.
For more information about compatibility, see the following page on the Microsoft Web site: Compatibility Matrix for 2010 Team Foundation Server to Team Explorer 2008 and 2005.
Although users of Team Explorer for Visual Studio Team System 2008 will be able to use the Manage Build Agents dialog box when connected to Team Foundation Server 2010, they will not be able modify the properties of Team Foundation Server 2010 Build Controller. If they attempt this, they will get the following error message: Updating build agents is not supported from this client. Please use a client compatible with Team Foundation Build 2010 and try again.
To resolve this issue:
Use Team Explorer 2010.
For more information about compatibility, see the following page on the Microsoft Web site: Compatibility Matrix for 2010 Team Foundation Server to Team Explorer 2008 and 2005.
There are no known issues.
© 2010 Microsoft Corporation. All rights reserved.