Skip to main content

TFS Local Workspaces error -TF400030: The local data store is currently in use by another operation.

On a large Visual Studio project I started getting the following error message:

TF400030: The local data store is currently in use by another operation.

This project is using the local workspace feature of TFS, which has a lot of advantages, but has it own set of problems when your solution gets quite large(think 50.000 items or more).

I tried multiple solutions to solve the issue:

  • One possible solution is to delete the local workspace and recreate it again. This will clear the local version table, and allows you to start over with a clean slate. We noticed a small performance improvement after doing this.
  • An alternative could be to evaluate your current workspace and see if some server side folders should not be mapped. This can help decrease the size of your workspace.
  • Another option you have is to change back from a local workspace to a server workspace. As mentioned before, this option is useful only when your workspace contains a lot of items. In that case switching to a server workspace can help as they are proven to scale to up to 10,000,000 items in a single workspace.

More information: http://blogs.msdn.com/b/phkelley/archive/2013/05/31/tf400030-the-local-data-store-is-currently-in-use-by-another-operation.aspx

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