All:
My question/problem is this:
A TFS user has a number of files checked out for exclusive checkout. The user has subsequently left the company. His domain user account has been deleted.
We've tried a number of command line commands to unlock the files, undo the operation, delete the workspace etc. However these approaches all seem to require workspace/owner information, & are unable to find/process the workspace the files were checked out to.
How can I undo/delete the checkout operation if the workspace or domain user account no longer exists?
Thanks in advance,
Dave Riches
|
| Dave Riches |
There are a few options. First, see my post on this thread regarding how to undo or unlock a file in another workspace as a user with appropriate permissions. Another option is to simply delete the user's workspace. This will remove all pending changes in that workspace.
Best of luck-
Cheers,
Adam
This posting is provided "AS IS" with no warranties, and confers no rights. |
| Adam Singer MSFT |
Adam:
Thanks for the response. I've tried the commands you suggested All the recommended approaches appear to require a workspace name to work against, however I'm getting messages stating the workspace does not exist, when I try unlocking the files, or deleting them. The message is shown below:
TF14061: The workspace catl0w33ronnras-1;CORP\rrastogi does not exist.
I ran a "tf status /format:detailed" command to verify the info for those workspaces.
Is there any mechanism I can use to unlock/delete the files without using a workspace name?
Dave Riches
|
| Dave Riches |
What is the user name? If you specify the workspace as just "workspacename", it will use your username instead of the other person's username. You can try to completely delete the workspace by running "tf workspace /delete workspacename;username /server:servername" as an administrator. You can find the complete syntax of the command line commands here.
Best of luck-
Cheers,
Adam
This posting is provided "AS IS" with no warranties, and confers no rights. |
| Adam Singer MSFT |
I tried deleting the workspace using the deleted Windows domain account name with the tf command tool; that didn't work.
I also ran the Team Foundation Sidekicks tool (http://www.attrice.info/cm/tfs/TeamBuildAddin.htm) that's been mentioned in Rob Caron's blog.This provides querying capability around both users and workspaces, amongst other things. It showed neither the user account in question or the workspace the files were checked out to still existed.
So my problem now appears to be: if the user account doesn't exist AND the workspace doesn't exist, but TFS still shows files exclusively checked out against those items, how do I remove the exclusive checkout? (BTW, the user applied the exclusive checkout to an entire project tree ~ 100+ files)
Any suggestions you can offer will be helpful.
Thanks,
Dave
|
| Dave Riches |
| The Sidekicks tool should tell you which workspace is holding the lock. You could also use tf status $/path/to/file /user:* |
| Richard Berg MSFT |
In addition to Richard's suggestion, I'm curious what error you see when you try to delete the workspace? Which version of TFS are you running? If it's Beta 3 or Beta 3 Refresh, we had a known issue that you couldn't delete workspaces for users that no longer existed.
Cheers,
Adam
This posting is provided "AS IS" with no warranties, and confers no rights. |
| Adam Singer MSFT |
Adam/Richard
TFS was put in place before I started working at this customer.
I'm told we were originally running Beta 3, which in turn was updated to Beta 3 refresh, which in turn was updated to RTM bits.
I suspect we may be encountering the problem with B3 you mentioned in your last post. If so, can you provide details on how to fix the problem please?
Thanks,
Dave
|
| Dave Riches |
Here's a post that tells you how to check what version of TFS and the client are installed: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=619290&SiteID=1
Please check to make sure both the client and server are RTM, and then run the "tf status $/path/to/file /user:*" command Richard mentions. That should tell you who has the file locked, and thus which workspace needs to be deleted or have changes forcibly undone by an administrator.
Cheers,
Adam
This posting is provided "AS IS" with no warranties, and confers no rights. |
| Adam Singer MSFT |
The TFS version my company is running is RTM (8.0.50727.147).
When any of the 'tf status' command, the Team Explorer tool in VS .Net or the Sidekick tool against the specific files, they all show the file is checked out to the user. When I query for, or try to delete information about the user account OR the workspace that the files are checked out against, I get the following message:
TF14061: The workspace <workspace_name;user> does not exist
As I mentioned in an earlier post, this implementation was upgraded from Beta 3 TFS, to the Beta 3 refresh version, and then updated to the RTM bits; is it possible the Beta 3 bug you mentioned in an earlier post regarding deleting previously-existing workspaces/users may have stayed in the TFS system during the upgrade?
Thanks,
Dave
|
| Dave Riches |
Does the user have any other workspaces? You can check via "tf workspaces /owner:username /computer:* /server:servername"
As for the bug in the beta3 code causing this issue- when was the user's account delete- was it before or after your upgrade to RTM?
Cheers,
Adam
This posting is provided "AS IS" with no warranties, and confers no rights. |
| Adam Singer MSFT |
index > Team Foundation Server - Version Control > Undoing exclusive checkouts