Skip to main content

TFS 2010 bug in upgrade process

Last week after upgrading a TFS 2008 environment to TFS 2010, we discovered that our merge history was no longer correct. After some investigation I found this post by Brian Harry where he explains that their is a bug in the TFS upgrade process.

'”We have discovered a potentially serious issue that can affect upgrades from TFS 2005 or TFS 2008 to TFS 2010.  The issue is triggered by a specific pattern of labels, renames, deletes and/or branches that existed before the upgrade.  Once the upgrade is complete the contents of the affected labels could be incorrect.  Also some internal merge tracking data could be incorrect, resulting in the need to reapply previous merges.” 

There is already a hot fix available here: http://code.msdn.microsoft.com/KB2135068. Apply the fix after the initial installation, but before you start the Team Foundation Server configuration. Therefore uncheck the “Launch Team Foundation Server Configuration Tool” checkbox at the end of the installation. 

Unfortunately you probably will only discover the issue when you start doing merges. So I suggest to run the scripts attached to Harry’s post to see if your environment is impacted. They describe it as a rare problem, but I was already able to reproduce the problem in 2 environments!

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more