Commentor Blog

When Quality Matters

Commentor A/S

When Quality Matters

Contact usSend mail

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2010

Upgrading TFS2005 to TFS2008 - AS problem

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.

 

Currently rated 5.0 by 1 people

  • Currently 5/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Posted by jorn.floor.andersen on Thursday, February 14, 2008 3:49 PM
Permalink | Comments (1) | Post RSSRSS comment feed

Related posts

Comments

Joe Z us

Friday, May 09, 2008 11:41 AM

Joe Z

Thanks for the post, it was a big help. We ran into a similar problem during our upgrade. After we ran the step from the command line it mentioned a problem with a file: Team System.2738.cub.xml. In our case the XML file was missing a default root node (it was empty). So we moved the file, and clicked the retry button. The rest of the upgrade went well. FYI - Microsoft support suggested we try to create a new team project after our upgrade to test that it was successful. This process touches almost every part of the server and will let you know in a hurry if you have any problems.

Add comment


(Will show your Gravatar icon)  

  Country flag

[b][/b] - [i][/i] - [u][/u]- [quote][/quote]



Live preview

Friday, July 30, 2010 8:38 AM