Patches for Team Foundation Server 2008 Beta 2 available

We have released patches for some known issues with Team Foundation Server 2008 Beta 2 upgrades that have been causing headaches for some of you.  Thanks for all your feedback that helped us uncover, diagnose, and fix these issues!

You can download the patches here.

Here are some more details on the issues:

 

Overview

SYMPTOMSWhen you upgrade a Microsoft Visual Studio 2005 Team Foundation Server installation to Visual Studio Team Foundation Server 2008 Beta 2 you may receive one of the following errors:• "There is no team project named' in source control"• "TF220059: The installation process cannot continue"Installation will fail to complete when these errors are encountered.CAUSE• The first error, "There is no team project named' in source control", occurs when a Team Project is deleted and then re-created with the same name in Microsoft Visual Studio 2005 Team Foundation Server and then the database is upgraded as part of Visual Studio Team Foundation Server 2008 Beta 2 installation. • The second error, "TF220059: The installation process cannot continue", occurs when upgrading a Microsoft Visual Studio 2005 Team Foundation Server installation configured to run using a local account to Visual Studio Team Foundation Server 2008 Beta 2. The Visual Studio Team Foundation Server 2008 Beta 2 installer incorrectly tries to contact an Active Directory instance to authenticate the local account.

Instructions

To resolve this problem:1. Download this update. 2. Copy the Visual Studio Team Foundation Server 2008 Beta 2 installation update to a writeable location such as your local hard-drive.3. Run the update to extract the files to a known location.4. Overwrite the files in the Visual Studio Team Foundation Server 2008 Beta 2 installation media location from step 2 with the files from the update in step 3:a. AT\Setup\TeamBuildUpgrade.exeb. AT\GetCurrentTfsProperties.exe5. Re-run the setup.exe from the Visual Studio Team Foundation Server 2008 Beta 2 installation media location from step 2.