Поделиться через

Solved: The working folder is already in use by the workspace

  • Статья

When trying to map a local folder to a TFS server as a different user than the one under which I was logged in, I kept getting the message:

The working folder [source path] is already in use by the workspace [workspace name];[owner] on computer [tfs server].

I was finally able to map the folder by first deleting the local workspace as the logged in user:

tf workspace /delete /server:[tfs server] [workspace name];[owner]

Note that the "owner" was the currently logged-in user.

Thanks to the "Geek-A-Boo" blog for the solution at this page.

Rob

Comments

  • Anonymous
    January 18, 2014
    The comment has been removed

  • Anonymous
    January 18, 2014
    The comment has been removed

  • Anonymous
    January 29, 2014
    tf workspace /delete /server:http://tfs.my.url.com:8080 WorkspaceSomething;DomainNameSomethingUserInitialsSomething

  • Anonymous
    January 30, 2014
    Thank you It worked :)

  • Anonymous
    February 04, 2014
    Use tf workspaces /owner:* /computer:* /server:http://MyServer:8080/tfs/MyCollection to find all workspaces Use tf workspace /delete /server:https://[yours].visualstudio.com/DefaultCollection [workspacename];[username] to delete a specific workspace. More here: stackoverflow.com/.../change-computer-name-for-a-tfs-workspace

  • Anonymous
    April 08, 2014
    Why do we have to go back to the 1990's? I hate the console.

  • Anonymous
    April 14, 2014
    This worked for me : Eg - tf workspace /delete /server <TFS Server Name> <WorkspaceName>;<Owner> P.S. - Remove the angular brackets

  • Anonymous
    June 29, 2014
    this work perfectly to resolve the issue

  • Anonymous
    July 01, 2014
    Well, almost resolved.  It depends which user your visual studio is logged in as (MSDN registration), as well as which user your TFS is logged in as. And here's a way to get it from not the console .... mostly. Scenario: Change the active TFS current developer user that is checking-in. Error when trying to map to the same folder as previous user. i.e. C:Dev Aim: To change from UserA to UserB. Both are registered as users in Visual Studio Online/TF. Note 1 This will delete the folders and files of code - please ensure you have a backup. Note 2 If you leave files not under source control then step 9 will fail. Remove them and try again. Preparation: 1 Close VS 2 List the current user's workspaces: open Command prompt: "C:Program Files (x86)Microsoft Visual Studio 12.0Common7IDEtf.exe" workspaces If UserA is not listed here then you will have to do 'Switch User', as per Step 4 below. 3 Rename C:Dev to C:DevBackup Solution: 1 Open VS. 2 Open Team Explorer 3 Up near home there is a little down arrow, click it choose 'Projects and My Teams', choose 'Connect to Team Projects' Option 1 no popup appears, click 'Select Team Projects ...' under the Team Explorer pane's Connect item. 4 A popup appears, in the bottom left, if not UserA, then click Switch User and type in UserA's credentials. 5 Confirm Current userA has a mapped folder 6 Click the Home/House icon, 7 Click Source Control Explorer 8 Right click the top Folder on the left pane, choose Advanced | Remove mappings 9 Make sure the root path matches your original UserA Local Folder 10 Click Remove Mapping button (ensure 'recursive' is selected) 11 open up most of the tree of projects in Source Control Explorer and make sure no folders are still mapped.

  • Anonymous
    October 12, 2014
    Boy, I was angry back in January.. lol

  • Anonymous
    January 08, 2015
    before you can find peace with the server you must find peace within your sole

  • Anonymous
    February 01, 2015
    Thanks guys, Sidekicks worked very well for me.

  • Anonymous
    March 12, 2015
    Thankyou all, Sidekicks also worked very well for me, note that must choose wide range of access time to display all the workspaces

  • Anonymous
    July 15, 2015
    You can use a product called Team Foundation Sidekicks if you do not like the console.

  • Anonymous
    December 01, 2015
    Another way around this issue is to change the workspace to a shared workspace; thus if you have a machine on which multiple developers will be working (e.g. a build server) you can resolve the issue without having to delete another user's workspace each time.  More info here: dev.goshoom.net/.../shared-workspace