Path already mapped in another workspace
February 6, 2007 7 Comments
Today we ran into a little problem with workspaces. We have a VPC with our projectcode in VS2003. We are using the MSSCCI provider to connect to the Team Foundation Server. When i want to share my VPC with another project member we logically ran into a SID problem. We ran the tool NewSid to make sure that our VPC’s have a different Identity. To make sure that the other project member works on another workspace we also created a new TFS account. To be sure we deleted al the local files. When we wanted to connect to TFS we get the error message “The path ….. is already mapped in workspace …..”. This was a bit strange. A workspace is created on a computername and a TFS useraccount. We changed both! After some research we visited the Team System blog. Our problem was located at “C:\Documents and Settings\[user]\Local Settings\Application Data\Microsoft\Team Foundation\1.0\Cache\VersionControl.config“. take a look at this config file and it makes a lot clear. We deleted the cache folder and it works! The Team System blog saved me a lot of time thanks!
Dennis van de Laar 
Thank you, less another frustration
you’re welcome!
Hey Dennis, great article I just got this working on our VPC.
Now onto the next problem… Now TFS doesn’t think I’ve downloaded any of our projects, even though structure exists locally and the workspace mapping is correct.
Any ideas?
Thank you!
Tim
Hey Tim,
Try “get specific version” and check both checkboxes (overwrite and force). This will force a download of all the code files within your team project. Let me know if this helps.
Regards
Great post. This one really helped me a lot 🙂
3 years later and still a helpful post, thanks! Had the same issue after upgrading TFS 2005 to 2010 and using the same local paths.
Thanks for the post. It helped me as well when upgrading to TFS 2010.