TFS Workspace Gotcha!

I have been working with a team that has recently migrated a TFS source project from a trail TFS to a full production server (different server). They disconnected their solution from source control (removes all the SCC stuff from .sln) files and then tried to add to the new TFS.

However, they were getting weird errors.

I suggested that they might not have their workspace mapped correctly to the new TFS project.

When they tried to map the workspace, they got the following error:

The Path <local path> is already mapped in workspace <machine name [old tfs server]>

Hmm, I thought we removed all the source stuff?

Turns out that the workspace mappings are stored in a file called:

VersionControl.config under the users local settings/application data directory.

I could find no way (other than manually editing the forementioned file) to remove the workspace mapping from that local folder to the other TFS server (which is no longer in usage).

Anyway, once that was done, all was good in the world.

Thanks go out to Kevin Jones for his excellent post on Workspaces in TFS.

posted on Monday, September 11, 2006 8:55 AM

Feedback

# VSTS Links - 09/12/2006 9/12/2006 6:23 AM Mickey Gousset

Aaron Kowall on TFS Workspace Gotcha!

Eric Jarvi on VSTS Tip: Tech Ed 06 Team System Sessions.
...

# re: TFS Workspace Gotcha! 9/12/2006 6:00 AM Buck Hodges

You can use the command "tf workspaces /remove:*" to clear out all of the cached workspaces (it only affects the cache file). You can specify /s:http://oldserver:8080 to just clear out the workspaces that were on the old server. The MSDN doc for the workspaces command are at http://msdn2.microsoft.com/en-us/library/54dkh0y3.aspx.

The reason that you hit this is due to switching servers. Every server has a unique identifier, which is a GUID. Each local path can only be mapped in a single workspace. You originally had a workspace on the first server that used the local path you wanted to use with the new server. Let's say that's c:\projects. When you create the new workspace on the new server (GUID2) that you also want to map to c:\projects, the client sees that the old server (GUID1) is already using that local path. Since the IDs for the servers do not match, the client complains that c:\projects is already mapped to the old workspace on the old server.

The solution is to clear the cache file, as described above. The problem will not occur if you upgrade the same server (i.e., you don't create a new server).

Buck

# How to handle &quot;The path X is already mapped in workspace Y&quot; 9/12/2006 7:35 AM Buck Hodges

This has come up before on the forums, but I don't think I've ever posted about it here.  Today...

Post Feedback

Title:
Name:
Email: (never displayed)
Url:
Comments:
Please add 5 and 3 and type the answer here: Remember Me?

Caffeinated Geek

News

Tag Cloud

Archives

Post Categories

Friends of Mine

Feedback

Post Feedback