Team Build Error: The Path ... is already mapped to workspace

Use the command line utility TF - Team Foundation Version Control Tool (tf).

You can get a list of all workspaces by bringing up a Visual Studio Command Prompt then changing to your workspace folder and issuing the following commands:

C:\YourWorkspaceFolder>tf workspaces /owner:*

You should see your problem workspace in the list as well as it's owner.

You can delete the workspace with the following command:

C:\YourWorkspaceFolder>tf workspace /delete /server:BUILDSERVER WORKSPACENAME;OWNERNAME

I received this error, which was caused by having two build definitions that pointed to the same source. The issue was that I used a static build directory in the Build Agent.

This forum post describes my issue and resolution exactly: http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/60a4138a-9b28-4c46-bdf4-f9775ce43c3e/

Here is what I did (well what I do):

Using TFS Sidekicks clear out the user and server filters so they are blank. This will let you get all workspaces.

Check the build error for the workspace name. In the OPs case it is BuildServer_23. It is different in my environment but basically just match up the error name with the one in the tfs sidekick list.

Click the red x to delete the workspace.

Viola!

I couldn't get any other solution to work.

I had a new account created and the old account no longer had permissions (both on same machine).

I tried: 1) Deleting the workspace (couldn't see in VS with or without remote workspaces checked) 2) Deleting from the command line 3) New owner command 4) Deleting the cache

So I simply opened VS as admin and mapped to a different folder.

Deleting the workspace and cache was not sufficient for me. I had to also restart the "Visual Studio Team Foundation Build Service Host" service.

1. Go to the Source Control Explorer
2. In the toolbar there is a dropdown list of Workspaces.
3. Click the dropdown and go to workspaces.
4. Remove the unwanted workspace.
5. Map to your local.

I had this issue with this with Azure DevOps automated builds in an on-prem TFS build agent. Removing the workspace using TFS Sidekicks did not work. And tf.exe could not even find the workspace to delete it.

This solution should work for TFS 2017, TFS 2018, Azure DevOps, and possibly other versions:

1. Take note of the workspace GUID in the error message.
2. On the machine where the build is taking place, navigate to: %USERPROFILE%\AppData\Local\Microsoft\Team Foundation\ (where %USERPROFILE% belongs to the user that triggered the build).
3. Search for and remove all instances of the workspace GUID under that directory. There will likely be a folder in a 'cache' directory, as well as entries in 'LocationServerMap.xml' and 'LocalItemExclusions.config'. Remove them all.

That worked in my circumstance.

Simply delete the workspace:

workspace /delete "the-workspace-name"