How to handle "The path X is already mapped in workspace Y"

Workspace Mapping 出現問題 ?

Refines.Info["Polo Lee"] — Wed, 13 Sep 2006 03:13:06 GMT

過去幾個月，零零星星的聽見到某些正在使用 TFS 與 TE 的團隊提到， Workspace Mapping 好像怪怪的，常常會有問題明明對應好了，好像會跑掉東西放不完整... 這個抱怨就進階的...

VSTS Links - 09/13/2006

Team System News — Wed, 13 Sep 2006 15:50:10 GMT

Andy Johns on Bye Bye TFS.

Rob Caron on Team Foundation Server Language Change Package.

Aaron Hallberg...

An introduction, 1350 posts later

BUGBUG: poor title — Tue, 17 Oct 2006 10:23:34 GMT

On the Microsoft forums , that is...no, I didn't suddenly eclipse Raymond . As you probably haven't noticed,

re: How to handle "The path X is already mapped in workspace Y"

pb — Wed, 27 May 2009 19:10:28 GMT

But this doesn't help when trying to remove the temporary workspaces TFS creates during the build. I have a temporary workspace that has been left "hanging" and can't get rid of it.

re: How to handle "The path X is already mapped in workspace Y"

buckh — Wed, 27 May 2009 20:12:00 GMT

pb, you'll want to run tf workspaces /owner:<whatever your build service account is> /computer:* to get a list of the workspaces. You can then delete it with tf workspace /delete:workspaceName;workspaceOnwer.

Buck

re: How to handle "The path X is already mapped in workspace Y"

David Quinlan — Thu, 11 Jun 2009 13:32:20 GMT

I am getting this error also, but I'm not sure it is for the same reason.

Our projects share our core frame work solutions.

So DevPathA will have a build configured and reference Source Control for main solutions and frame work solutions, DevPathB will have build configured and reference source control for it's branch of solutions and the same framework solutions.

When we run build on DevBathB, we receive the error.

Basically, 2 builds on 2 different branches of source, referencing the same set of shared sources.

Any ideas?

Thanks,

David

re: How to handle "The path X is already mapped in workspace Y"

buckh — Thu, 11 Jun 2009 16:13:48 GMT

David, that should be fine, but you will need to make sure that the local paths for the workspace mappings in each of the build definitions do not overlap. They can both map the same thing from version control, but they cannot use the same local path (i.e., they each need their own independent local copy).

If you've had to rename or re-arrange builds, it could be that you need to delete the old build workspaces to make way for the new ones. You can use the tf workspace /delete command. The form would be tf workspace /delete workspaceName;workspaceOwner /s:http://yourserver:8080, which an admin could do. Or you could log in as the build service account and delete the workspace(s) with the tf workspace /delete command without needing to be admin.

Buck

re: How to handle "The path X is already mapped in workspace Y"

David Quinlan — Thu, 11 Jun 2009 16:57:23 GMT

Cheers Buck,

What about having 2 builds for the same branch, one that deploys to a DEV server on a daily basis, the other, that deploys to a TEST server on demand (or weekly).

David

re: How to handle "The path X is already mapped in workspace Y"

buckh — Thu, 11 Jun 2009 17:50:42 GMT

David, that should work very well. We do this internally, for example, where we have CI and nightly builds for the same branch.

As long as you keep the local paths in the workspace mappings disjoint, you should be good.

Buck

re: How to handle "The path X is already mapped in workspace Y"

Anton de Gruchy — Tue, 23 Jun 2009 15:42:02 GMT

I have removed all references in Version.config for both VS 2005 and VS 2008 and I have deleted the workspace using fs workspace command utility. Yet I still have the problem. They changed our domain name and the old domain is in the "workspace" but I cannot seem to find out where to delete it.

re: How to handle "The path X is already mapped in workspace Y"

buckh — Thu, 09 Jul 2009 04:05:42 GMT

Anton, did you clone a server? If so, that can cause issues. Changing the domain name won't confuse the client.

http://blogs.msdn.com/buckh/archive/2006/10/17/creating-a-new-server-from-an-old-one-beware-of-the-instanceid.aspx

Buck

re: How to handle "The path X is already mapped in workspace Y"

Srikanth — Mon, 13 Jul 2009 17:33:54 GMT

Running "tf workspaces /remove:*" from VS command prompt helped me fix the error.

I also had to reboot the VS IDE and removed the old workspace and created a new one and everything started working.

Thank you !