When an instance of TFS2008 (or 2005) is to be upgraded to TFS2010 the SQL Server must be upgraded to 2008 (sp1) as a minimum. I expected this to be the smallest issue but the problem that:

"Rule 'Consistency validation for SQL Server registry keys' failed". The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.

It turned out to be a problem with the permissions for a registry key for SQL Server. Even though I tried to upgrade with an account with local admin rights there was a registry key which didn't allow access. For this particular instance it was the key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\UDDI\MSSQLServer\SuperSocketNetLib\Lpc

The solution was to add the account which was used for the upgrade to have full access to this key. Probably write acces would have been sufficient.

The way to find out which key(s) it is/are is to look in the SQL Server installation log:

Folder: .\Microsoft SQL Server\100\Setup Bootstrap\LOG\ ("and then the date and time of the upgrade attempt")

Look for "System.UnauthorizedAccessException" in the Details.txt file

///Jørn

Error:

TFS Error 2900: Execution of a full-text operation failed. 'Access is denied.' Creating full text index on Workitem

This error (actually the generic error 29000) came when installing TFS2008 on a dual-server configuration, where the data-tier was clustered. It turned out that the SQLFullTextService was running under the TFSService account and it didn't have sufficient rights to the databases.

Resolution: 

After the TFSSerice was made sysadmin on the database and the full-text service was restarted (from within SQLServer Mangement Studio or Cluster Admin - not the Service MMC as that would have made the fulltext service to fall to the secondary node) it worked.

The link below is a guide to upgrading TFS2005 to TFS2008. It includes descriptions of different errors and work arounds for these found during a number of upgrades of various TFS installations. Further a number of the steps in the official upgrade guide is further detailed or corrected.

Team Foundation Server upgrade from 2005 to 2008.docx (35,18 kb)

If the Team Explorer is installed right after TFS has been installed the following error might occur:

This error can be ignored as long as it still says Succesfully installed in the end dialog. It seems to be related to the setup process running and some files still locked from the TFS install.

Projektledelse med Team System 2008:

Projektledelse med Team System 2008.pdf (797,04 kb)

Projektledelse med Team System 2010:

Projektledelse med Team System 2010.pdf (383,65 kb)

Reports for VSTS 2008:

VSTS 2008 Reports.pdf (852,24 kb)

In relation to the upcomming Launch of Microsoft Visual Studio Team Foundation Server 2008 we have made a couple of web casts about new version control features and customization of builds:

http://blogs.commentor.dk/downloads/WebCast - Customisering af builds.wmv

http://blogs.commentor.dk/downloads/TFS2008 SC features.wmv

///Jørn

Last week we should upgrade a TFS2005 dual server installation to TFS2008. Pretty straight forward as we didn't wanted to upgrade SharePoint services from WSS 2.0 to WSS 3.0. So the installation followed the standard upgrade guide:

1) Uninstall TFS on the data-tier server

This should actually never have been there, but is just a left-over, which the MS team doing the Setup program didn't get rid of before the release - Unfortunately it has been a source of frustration as no database team in an IT department wants anything installed on their database servers :-(

2) Installation of TFS2008 on the Application-tier.

First we had to restore the changes we had made for accessing the TFS server over SSL/Basic authentication. This to ensure that the Setup program could access the WSS and reporting services. After we had ensured access to both wss and rs we could do the upgrade-installation. The process went well untill we got the following error:

The Error: 32000 on TfsDb.exe is pretty generic, so we had to run the step from the command line and then we could actually see that it stopped in processing the cube files:

\\[AS Files folder]\MSSQL.2\OLAP\Data\TfsWarehouse.0.db\Team System.13093.cub.xml

This file was for some reason corrupted, as it ended in the middle of the XML statements. The TfsDb.exe program couldn't instantiate an object based on that. The solution was to delete the file and then process the dataware house.

 After that the upgrade was successful.