At my current client we have about 15 or so users of Team Explorer Beta 2 that needed to be upgraded to the RC client (since I upgraded the server to RC). Out of those 15 there were 2 cases of users experiencing installs that would crash after reaching the Complete/Custom selection screen. One of the users was on a laptop running XP SP 3 and the other was on a desktop running XP SP 3. After many attempts (command line install w/ supressed UI, registry changes, etc.) at getting the setup to run correctly and install a working copy of Team Explorer 2010 RC failed I did some searching and found a few people running into the same problem.
The general idea for a fix was that the Language Bar needed to be disabled in order for the install to be successful. So I gave it a shot and it worked. Both users are now happily running complete installs of Team Explorer 2010 RC. My steps taken are defined below:
- Click Start, click Control Panel, and then double-click Regional and Language Options.
- On the Languages tab, under Text services and input languages, click Details.
- Under Preferences, click Language Bar.
- Deselect the Show the Language bar on the desktop check box.
- Extra step in my case: Remove handwriting recognition in the listbox on the parent window.
- If the language bar is still present on the taskbar right-click it and remove it.
Not sure what the language bar has to do with the setup.exe of Team Explorer or Visual Studio but this slight change turned a headache into a good day. If anyone has a reason of why this error is occuring please post it in the comments.
Hope this is helpful to those who find it.
I performed an in place upgrade of a TFS 2010 Beta 2 instance to and RC instance yesterday using this guide:
TFS Beta 2 to RC Upgrade Guide
The overall process was relatively smooth. There was only one hiccup at the very end of the "Upgrade from previous version" config wizard that almost had me in tears.
The last step was to upgrade all exisiting Project Collections. What it seemed to do was put each collection into a queue and then falg them as being serviced. While in this state nothing could be done to the collections and they were offline. The problem I had was that they never passed the first step of this process and remained in the offline/servicing status for about an hour. After searching for some sort of activity (logs, processes, etc..) I nearly cancelled the whole thing due to lack of information and the overall feeling that the process had hung up. Out of nowhere the config wizard closed, as if finished, and returned me to the TFS Admin Console.
I looked through the application tier and the project collections were still offline and still queued for servicing. So I made the decision to perform an almighty restart on the server and hope for the best. When the server finally botted back up I went back in the admin console to check the status again and what I found was what I had hoped for, the project collection upgrade process was back in full swing and completinhg without error.
Not sure if this was an isolated error or not, since it the RC was just released, but I hope that if others have this problem my journey will provide some help.
Seems as though the "destroywi" command has been moved from the Power Tools into the actual TFS administration executables. I case you were wondering here is the /? from the new destroy work item command in TFS 2010.
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE>witadmin destroywi /?
Work Item Tracking Administration tool. (C) Copyright 2006 Microsoft Corporation. All rights reserved.
Destroys a work item or work items. Currently, work items can only be destroyed. Destroying a work item means the work item is physically deleted and cannot be restored. The system does not support logical (and thus recoverable) deletion of work items.
Usage: witadmin destroywi /collection:collectionurl /id:id [/noprompt]
/collection Specifies the Team Foundation project collection. Use a fully specified URL such as
http://servername:8080/tfs/Collection0.
/id Specifies the ID of the work item to destroy. Supports multiple IDs delimited by commas
such as 12,15,23 (with no whitespace).
/noprompt Turns off the confirmation message.
I was looking for this using the old "tfpt destroywi" command and kept getting errors saying the command didn't exist when I finally did some searching and came across the new home for the command. Could be pretty helpful if needed.