For the latest version of the Readme click here.
For Beta 1, the latest version of the Readme is available here.
1.2 Supported Operating Systems:
1.4 Prerequisites:
If .NET Framework 4 Beta 1 is installed on the computer when you install Visual Studio 2010 Team Foundation Server Beta 2, the Team Foundation Server installation fails.
To resolve this issue:
Important step-by-step instructions for avoiding or resolving this issue are in the Beta 2 Installation Readme Addendum.
When backing up Team Foundation Server 2010, you should create a consistent backup at the same point in time across all Team Foundation Server databases, including the configuration database and any team project collection databases. If this is not possible, you must back up your configuration database last.
To resolve this issue:
Create a backup plan that backs up all Team Foundation Server databases at the same time. If this is not possible, back up all the team project collection databases first and the configuration database last.
No 64-Bit edition of Windows Server 2003 is supported.
To resolve this issue:
You must use a supported operating system.
Configuration wizard for Team Foundation Proxy will not install or configure Internet Information Services (IIS).
To resolve this issue:
You must install and configure IIS before you install Team Foundation Proxy.
If you have SQL Server 2005 Express installed, you cannot install Team Foundation Server with SQL Server 2008 Express.
To resolve this issue:
You can either uninstall SQL Server 2005 Express or manually upgrade SQL Server 2005 Express to SQL Server 2008 Express. You can find the SQL Server Express installation file here:
%Program Files%\Microsoft Team Foundation Server 2010\Tools\SQLExpr32_x86_ENU
The actual file name is based on your platform and language.
When you use the advanced configuration wizard for Team Foundation Server on a client operating system (Windows Vista or Windows 7) and specify a SQL Server instance located on a server other than the computer running Team Foundation Server, SQL Server Express is installed on the computer running Team Foundation Server. Nevertheless, the wizard configures Team Foundation Server to use the specified remote SQL Server.
To resolve this issue:
You can uninstall SQL Server 2008 Express from the computer running Team Foundation Server.
The SQL Server Express installation fails. When you look in the installation log, you find error message 3010.
To resolve this issue:
You must restart the computer and attempt to configure Team Foundation Server again. Error code 3010 means the system requires a restart.
There is no documentation included on-disc for preparing a system to be cloned.
To resolve this issue:
Documentation on preparing a system to be cloned can be found here:
http://go.microsoft.com/fwlink/?LinkId=165763.
You installed Team Foundation Build Service and then used the Add/Remove Team Foundation Server Component to add the application tier to the computer. If you do this and then specify SQL Server Express, the installation fails.
To resolve this issue:
You must manually install SQL Server Express. You can find the SQL Server Express installation file here:
%Program Files%\Microsoft Team Foundation Server 2010\Tools\SQLExpr32_x86_ENU
The actual file name is based on your platform and language.
If you use the basic wizard to configure Team Foundation Server, you might have problems with selecting SQL Server instances in the following situations:
You have SQL Server Express 2005 installed. You may be able to select this instance, but SQL Server Express 2005 is not supported.
You are on a 64-Bit operating system, but have a 32-Bit edition or the WoW edition of SQL Server Express 2008 installed. Your SQL Server Express will not be detected and a SQL Server Express installation is attempted, but will fail.
To resolve this issue:
Manually type the name of the SQL Server Express instance you want to use, rather than letting the wizard automatically detect it. Use this format: MachineName\SQL Express.
If you have SQL Server Express 2005 installed, you must either uninstall or install SQL Server Express 2008 with a custom instance name. You can find the SQL Server Express installation file here:
%Program Files%\Microsoft Team Foundation Server 2010\Tools\SQLExpr32_x86_ENU
The actual file name is based on your platform and language.
There are no known issues.
If you configure Team Foundation Proxy by specifying a URL without the team project collection, the proxy does not cache any version control files for the remote location. Version control requests sent by the proxy are serviced correctly by the application tier, but none of the files are cached in the remote location. The proxy is effectively by-passed.
To resolve this issue:
1. On the computer that is running Team Foundation Server Proxy, open Windows Explorer, and locate the proxy installation directory at Drive:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControlProxy.
2. Open the Proxy.config file in a text or XML editor (you may have to launch your editor with elevated admin permission.)
3. Locate the <Servers> node, the <Server> element, and then the <Uri> element.
4. In the URI node, you must enter the full Team Project Collection URL, including the name of the Collection. An example would be <Server><Uri>http://ApplicationTierServerName:8080/tfs/Collection0</Uri></Server>.
5. Repeat step 4 for each Collection that the proxy is intended to service.
6. Save proxy.config and reset IIS to make the new settings take effect.
After renaming the team project collection the Team Foundation Administration Console might not reflect the new name. In addition, when opening the Administer Security or Group Membership dialogs for that collection you see a 404 error message indicating that the old collection name is no longer available in the server.
To resolve this issue:
The workaround is to delete the client cache data generated by the Team Foundation Administration Console on the application tier.
You can find the client cache here:
C:\Users\USERNAME\AppData\Local\Microsoft\Team Foundation\3.0\Cache
Where USERNAME is the username for your account.
If both Team Foundation Server and Team System Web Access are configured to use Basic Authentication, then Team System Web Access will redirect users to the login page with a "could not be authenticated" error when users try to connect. This configuration is most common when installing on a client operating system, such as Windows Home Premium, which does not support Windows Integrated Authentication through IIS.
To resolve this issue:
Use Forms Authentication in Web Access by enabling Anonymous Access in the Web Access IIS web site. In this configuration, users will be redirected to the Web Access login page after connecting. Users will be able to connect by entering their credentials in the Web Access login page and clicking Submit.
Team Foundation Server 2010 includes a new feature to generate Excel report from the results of a work item query. However, the data provider used when generating the report is not compatible with the Microsoft Office SharePoint 2007 dashboard, so it needs to be changed before publishing the workbook using Excel Services.
There is another known issue publishing generated workbook with multiple worksheets. The Microsoft Office SharePoint 2007 dashboard uses a specific connection name when refreshing published Excel workbooks. Since the generated reports use more than one connection and do not use the name the dashboard expects, these reports will not get refreshed along with other reports on the dashboard.
To resolve this issue:
1. Once the Excel report is generated from the query, select the Data tab and choose Connections.
2. In the Connection Properties dialog, change the name of the connection to 'TfsOlapReport'.
3. Select the Definition tab and change the Provider portion in the Connection string text area from "Provider=MSOLAP.4" to "Provider=MSOLAP.3". Leave the rest of the string as it is and click Ok.
4. Close the Connection Properties dialog by clicking the Close button.
The workbook can now be published to the Microsoft Office SharePoint 2007 dashboard but this only works when you have a single worksheet that was generated. The only workaround to fixing up connection names when multiple reports are generated that need to be published to the Microsoft Office SharePoint 2007 dashboard is to generate them one at a time and change the connection name and provider string per instructions above.
Team Foundation Server 2010 added a new feature to mark a work item field of type string to allow name to be automatically synced when display names change. The admin tool, witadmin.exe, also adds support for converting an existing string field to allow syncing name changes. However, converting string fields to allow name changes causes Team System Analysis Services cube to stop processing.
To resolve this issue:
The workaround is to rebuild the Team System Analysis Services cube after converting a string field to allow name changes. The Team System cube can be rebuilt by opening a command prompt on the application tier of Team Foundation Server and running this command:
"%ProgramFiles%\Microsoft Team Foundation Server 10.0\tools\tfsconfig.exe rebuildwarehouse /analysisservices".
When you create a network-isolated virtual environment using Team Lab Management on a host group that contains Windows Server 2008 R2 hosts, the network-isolation status of that environment might never transition to the 'Ready' state. This is a known issue because MAC spoofing on Windows Server 2008 R2 hosts prevents network isolation from functioning.
To resolve this issue:
To use network isolation with Windows Server 2008 SP2, create a host group on that server and use that host group when creating network-isolated environments.
Lab Management configuration fails when 1) Team Foundation Server and Virtual Machine Manager are installed on the same machine and 2) Network Service is used as the TFS Service Account. The configuration is blocked because the username/password dialog used to insert the TFS Service account into VMM becomes stuck in an infinite loop.
To resolve this issue:
Before configuring Lab Management, change the Team Foundation Server system account from Network Service to a domain account that is a member of the Team Foundation Server Administrator Group.
1. Open the Team Foundation Administration Console and, in the left pane, click Application Tier.
2. In the right pane, click Change Account.
3. In the Update Service Account dialog, click Use a user account.
4. Type the username and password of a domain account that is a member of the Team Foundation Administrator Group. Make sure that the new account has permissions to access the Team Foundation Server logical data-tier.
5. Click OK.
6. In the left pane of the Console, click the Lab Management node and proceed with the configuration.
When you install Windows SharePoint Services 3.0 during Team Foundation Server installation, the German language version of Team Foundation Server fails to create the team project collection.
To resolve this issue:
1. On the server that is running the application-tier for Team Foundation, open the Team Foundation Administration Console.
2. Expand the server name, expand Application Tier, and click SharePoint Web Applications.
3. Click your SharePoint Web application in the list, and then click Change. The Edit SharePoint Web Application dialog will open.
4. In "Default location for team project collection sites", change "sites" to "websites" and then click OK.
5. In the administration console, click the Team Project Collections node, and then click Create Team Project Collection to create your first collection.
The VSSConveter tool has several known issues that may prevent migrations from being successful, or it may lead to files being incorrectly migrated.
To resolve this issue:
If you are attempting to use VSSConverter to migrate data from Visual Source Safe to Team Foundation Server 2010, first test the migration in a preproduction environment. Only proceed migrating to a production environment if you are satisfied with the results of the test migration.
If you need VSSConverter to migrate data from Visual Source Safe to Team Foundation Server 2005 or Team Foundation Server 2008, use the version of VSSConverter available in Microsoft Visual Studio 2008 Service Pack 1. You can download this Service Pack here: http://go.microsoft.com/fwlink/?LinkID=116488
There are no known issues.
The problem is caused by the fact that the macro code used to retrieve history on the burndown chart does not respect iteration and area paths below the root.
To resolve this issue:
Do not use the burndown chart in the Iteration Backlog workbook. Instead use the Burndown and Burn Rate report found under the Reports/Project Management node in Team Explorer.
Process guidance for the CMMI 5.0 process template is incomplete.
To resolve this issue:
The draft process guidance can be found online at: http://go.microsoft.com/fwlink/?LinkId=177925
For team projects based on the MSF CMMI 5.0 process template, the process guidance context menu item is broken.
To resolve this issue:
Open a Web browser and navigate directly to the process guidance at: http://go.microsoft.com/fwlink/?LinkId=177925
There are no known issues.
There are no known issues.
When you associate an existing build machine with a new Team Foundation Server project collection temporarily, then attempt to associate it with its original Team Foundation Server project collection, you may get the following error "No Build Service Host was found with name <full machine name>".
To resolve this issue:
1. Click OK to dismiss error dialog
2. Change Build Service Endpoint on Build Service Host Properties dialog to include only the friendly name (not the fully qualified domain name) For example, you might change this fully qualified domain name:
http://MyBuildMachine.test.microsoft.com:9191/Build/v3.0/Services
To this friendly name:
http://MyBuildMachine:9191/Build/v3.0/Services
3. Click Start
If you setup a build controller on machine A and a build agent on machine B, then configure the build agent on machine B to be managed by the controller on machine A and have both running as network service, and then create a build definition with a gated check-in trigger and set its default controller to the one on machine A, all check-ins affecting that build definition will fail.
To resolve this issue:
You will need to run the Build Services as a domain account rather than Network Service. To do so, follow these steps:
1. Log into the machine running the build agent.
2. Run the TFS Administration Console.
3. Select the Team Foundation Build Configuration node on the left.
4. Click the first properties link to configure the build service host.
5. Click the stop to make changes link
6. Change the credentials to a domain user account rather than Network Service.
7. Click start.
8. Log into the machine running the build controller.
9. Run the TFS Administration Console.
10. Select the Team Foundation Build Configuration node on the left.
11. Click the first properties link to configure the build service host.
12. Click the stop to make changes link
13. Change the credentials to the same domain user account you specified in step #6.
14. Click start.
When Team Foundation Server is configured for network load balancing (NLB), there is a known problem synchronizing non-domain accounts across the Team Foundation Server logical application tiers.
For example, assume there are two servers, AT1 and AT2, in the Team Foundation Server logical application tier, and agentsvc is the local account used to configure the workflow integration capabilites of Lab Management. Adding both AT1\agentsvc and AT2\agentsvc to the Project Collection Build Service Accounts group in the team project collection is not supported and results in intermitted failures of the workflow capability for virtual environments.
To resolve this issue:
Use a domain user account instead of .\agentsvc to configure Lab Management workflow integration when Team Foundation Server is configured for Network Load Balancing. The limitation of this workaround, however, is that you cannot use the network isolation capability for virtual environments because that capability requires local user accounts for build and test agents.
Create a Team Build configuration, make it build a Solution/Project containing non-ASCII characters, enable Index source and publish symbols activity.
When the configuration is built, the build operation itself will succeed, but the Symbols will not be published to the drop location.
To resolve this issue:
Remove non-ASCII characters from the Solutions/Projects' names, modify the Items to Build parameter of the Build Definition to include the newly named Solution/Project and queue the build.
If you are running a Test Agent with IntelliTrace or Test Impact diagnostic data adapters on the Team Foundation Server, you may see the server report a 503 error.
To resolve this issue:
If you are testing a website:
If you are not testing a website:
Currently, there are multiple known incompatibilities that prevent Visual SourceSafe from being used as a source code control provider. For this reason, Visual Source Safe cannot be used with a Visual Studio 2010 Beta 2 client.
To resolve this To resolve this issue:
Use the standalone Visual SourceSafe client for source control operations.
If Basic Authentication is in use for a Team Foundation Server instance, attempting to use the following tf.exe command line commands will result in error messages indicating the authentication failed. The commands with this problem include "tf resolve", "tf folderdiff", and "tf history". Other commands correctly prompt the user for credentials.
To resolve this issue:
The /login option must be used with these commands to allow the user to be correctly authenticated. The command line help explains the correct usage of this parameter.
Many customers may need to continue to use the Team Explorer 2008 client while connected to Team Foundation Server 2010. Several of the new Team Foundation Server 2010 features exceed the capabilities of the Team Explorer 2008.
To resolve this issue:
A new update for Visual Studio Team System will enable Team Explorer 2008 to perform scenarios as it did for previous versions of Team Foundation Server. You can download the Visual Studio Team System 2008 Forward Compatibility Update for Team Foundation Server 2010 interoperability here
For a summary of the experience of using the Visual Studio Team System 2008 SP1 client without the update against the 2010 Team Foundation Server, visit the blog site here.
For a description of the scenarios that are supported by this update, visit this site here.
TeamTeam 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 a compatibility summary with Team Foundation Server 2010, visit the blog site here.
The customer may not know if they were successful or not.
To resolve this issue:
The customer can check the build explorer (just like in Team Explorer 2010) or use the build notification applet (Team Foundation Server 2008 power tools release rather than Team Foundation Server 2010 release).
For a compatibility summary with Team Foundation Server 2010, visit the blog site here.
New build definitions will be automatically upgraded to Team Foundation Server 2010 build definitions using the upgrade build process template, so Team Explorer 2008 or older client users will not be able to edit them.
To resolve this issue:
Use the Team Explorer 2010 to edit build definitions. Alternatively, you can use a text or XML editor to edit the build process template.
For a compatibility summary with Team Foundation Server 2010, visit the blog site here.
While users of Team Explorer 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 the Team Explorer 2010.
For a compatibility summary with Team Foundation Server 2010, visit the blog site here.
© 2009 Microsoft Corporation. All rights reserved.