We acquired a hotfix from Microsoft to fix the following issue: "The destination file may change if you use the "tf merge" command together with the /baseless and /discard options on a computer that has Team Foundation Server SP1 installed" You can find out more about this patch at either http://support.microsoft.com/kb/959168/ or http://support.microsoft.com/default.aspx/kb/959168
I found out the hard way that this install is not very fast (I had anticipated 30-45 minutes). After two hours and the normal work day shortly commencing, I had no choice but to cancel (and end task) the install and risk whatever state that put us in. The install has a progress bar that quickly made it to nearly the very end (installing the new files went quickly) and then it just sat there (without using any CPU resources on our TFS app tier production machine, but consuming about 50% of our resources on the DB machine). This install shuts down the TFS web sites so that no-one else can access TFS during the install. It then performs updates on the TFS source control database and depending on how many projects you have could take hours (we have over 50 projects).
Hopefully knowing the time restraints will save someone else what I went though. And thanks to a great Microsoft support engineer for his help on this issue. We'll try again on a scheduled weekend outage (since our TFS server is in use almost 24X7) in a few weeks - wish me luck.
No comments:
Post a Comment