Product:
Dynamics 365 for Finance and Operations
Purpose:
The purpose of this blog is to explain how can we resolve the version control workspace issue while working with Azure DevOps version control, previously known as VSTS or TFS.
Error:
The path % is already mapped in workspace %
Resolution:
First make sure that no other workspace is mapped to this path (including remote workspaces).
Sometimes the trick could be to clear the TFS cache on client machines
- Close all instances of Visual Studio on the client machine
- Manually delete the corresponding TFS client cache folder
- Start Visual Studio
The path to TFS client cache folder varies depending on the TFS version. Delete contents of the cache folder to resolve the issue:
Tfs 2017: “%localappdata%\Microsoft\Team Foundation\7.0\Cache\”
Tfs 2015: “%localappdata%\Microsoft\Team Foundation\6.0\Cache\”
Tfs 2013: “%localappdata%\Microsoft\Team Foundation\5.0\Cache\”
Tfs 2012: “%localappdata%\Microsoft\Team Foundation\4.0\Cache\”
D365 for Finance and Operations 
You saved the day Muhammad! I inherited a VM that was used by another developer, but wanted to setup VS and map to DevOps. So, I deleted all workspaces using TFS command: tf workspace /delete but I kept getting the error that the workspace was already mapped! Anyhow, deletion from the cache as you suggested did the trick. I am not sure why the tf delete workspace command does not delete the cache as well.
Pleasure!