Posts to my blog are like buses - you don't get any for months and then three come along at once! So why this sudden spate of posts? Because I've spent much of the last 4 days trying to upgrade our TFS 2005 installation to TFS 2008 and, as with previous TFS upgrades/installs, it has not been the smoothest of rides. So I thought I'd post some tips here in the hope that it helps others avoid similar issues.
As usual, I followed the installation guide to the letter but the upgrade failed about 50% of the way through with
Error 29019: Team Foundation Report Server Configuration: SQL Reporting Services configuration encountered an unknown error. Verify that you have sufficient permissions to configure SQL Reporting Services, and try again.
At this point the TFS 2008 install had failed but the TFS 2005 installation had been removed and I was left without a working TFS server. Numerous attempts at repeating the installation also failed so I resorted to re-installing TFS 2005 but this also wasn't trouble free (see my earlier post).
After four days of experimenting with virtual servers instances I finally got the upgrade to work. If you want yours to work too, try following these suggestions
- Download and run the TFS Best Practices Analyzer tool against your existing TFS installation before you start the upgrade. Apparently it's vital that the existing installation is properly configured and fully working before you begin. The Analyzer will alert you to any problems with your existing configuration which you should fix before proceeding with the upgrade.
- Download and install version 2 of the Team Foundation Server Quiescence tool. Make sure you've definitely got version 2 installed, this certainly seems to be important if you're running SQL Server 2005 SP2.
- Don't follow Item 11 of the Upgrading Team Foundation Server instructions in the How to: Upgrade Team Foundation Server section of the install guide! This instruction states
On the Reporting Services Data Source Account page, click Use Team Foundation Server service account, and then click Next
Don't do this!! The upgrade wizard actually states that you must use the existing Reporting Services Data Source Account which you created when you first installed TFS 2005.
Following all of these steps certainly made my upgrade work properly, hopefully it will work for you too.
del.ico.us | 
Digg It | 
Technorati | 
StumbleUpon | 
Furl | 
reddit
As I mentioned in my previous post I have been doing a lot of work with out Team Foundation Server (TFS) recently. One of the things I've had to do is reinstall our existing TFS 2005 instance. Why so? Because upgrading to TFS 2008 repeatedly failed leaving us with no TFS installed and the only way back was to reinstall TFS 2005. The only problem was that the TFS 2005 reinstall also kept failing with the message
Error 28100: Error loading Event Web service
This occurred late in the installation process and confused because I was able to use my Web browser to test that Event web service was operating. A bit of Googling turned up the solution on a thread on the MSDN Team System forums.
It appears that the TFS installer looks to a registry key to find server information during an upgrade or reinstallation. If a previous failed install has left incorrect or missing data in this registry key then the 28100 error will occur. The solution is to delete the entire
\HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\8.0\TeamFoundation\Servers
key from the registry and try the installation again. It worked for me!
del.ico.us | Digg It | Technorati | StumbleUpon | Furl | reddit
As part of some messing around that I've had to do recently with Team Foundation Server (TFS) (more about that in a future post...) I need to move the Reporting Services database used by TFS to a new computer. I followed the steps in this Knowledge Base article to backup the encryption key and databases from the original server and to restore them on the new server. Unfortunately this didn't work and navigating to the report server page in a browser produced the following error message:
Reporting Services Error
Feature "Scale-out deployment" is not supported in this edition of Reporting Services
It took me a while to sort this out. When you restore the database and encryption key to the new server the database will then contain two key in the ReportServer database Keys table, one for the old server and one for the new server. When Reporting Services is started it spots the two keys and things that its operating a scaled-out front end but this feature isn't supported by Reporting Services standard edition.
To restore Reporting Services to working order on the new server you simply need to delete the record corresponding to the old server from the Keys table and restart IIS.
del.ico.us | Digg It | Technorati | StumbleUpon | Furl | reddit