Delete a TFS Workspace that already existsCategory: TFS2010-03-03 16:59 1239 people read comments (2) favorite reports Serverpathcommandcachefilegoogle job transfer to new TFS platform opens source control when creating workspace error message: The Path <local path> is Already mapped in workspace <machine name [old TFS server]> very weird BUG:)
Google search found that others have encountered the same problem (estimated that many people have encountered) http://geekswithblogs.net/aaronsblog/archive/2006/09/11/90878.aspx reference Kevin Jones's blog post, we know that client-side configuration information is stored in "C:/Documents and settings/[user]/local settings/application Data/microsoft/team Foundation/1.0/cache/versioncontrol.config "But it's not a good workaround to have everyone modify the config file.
Fortunately, Buck Hodges gave a more explicit explanation: The reason that's you hit this is due to switching servers. Every server has a unique identifier, which is a GUID. Each local path can is only is mapped in a single workspace. You originally had a workspace on the first server, that used the local path, you wanted, and the new server. Let's say that ' s c:/projects. When you create the new workspace in the new server (GUID2) that's also want to map to C:/projects, the client sees that The old server (GUID1) is already using the local path. Since the IDs for the servers does not match, the client complains that c:/projects are already mapped to the old workspace O n the old server.
And there's a clear solution:
The solution is to clear the cache file, as described above. The problem won't occur if you upgrade the same server (i.e., you don't create a new server). You can use the command "TF workspaces/remove:*" to clear out all of the cached workspaces (it is only affects the cache fil e). You can specify/s:http://oldserver:8080 to just clear out of the workspaces that were on the old server. The MSDN doc for the workspaces command is at http://msdn2.microsoft.com/en-us/library/54dkh0y3.aspx.
Hey, open VS2008 cmd, enter "TF worksapces/remove:*/s:http://oldserver:8080" Returns the teamexplorer found in VS or not. So decided to delete all the workspace in the cache "TF workspaces/remove:*" return to Teamexplorer again, everything OK:) to say a word, The MSDN documentation is really rotten, the content is not updated now, or requires input/s:servername, if this input, there will be an error to tell you: URI is illegal, can not recognize the format of the URI. Transferred from: http://blog.csdn.net/wenjie847/article/details/5342856
"Go" removes TFS Workspace that already exists
