Please don't directly edit the SQL tables. Whether or not it worked out for you this time, you will get burned at some point. I appreciate the fact that you needed to get your work done. I just don't want to see you get yourself into a situation where the only recovery is to restore from backup.
The first error message was correct, and you did the right thing by changing
the exlusive checkout setting.
Pending changes are scoped to a workspace, and that includes locks because we
use pending changes to implement them. The lock command supports a workspace
parameter to unlock changes in other workspaces, assuming you have sufficient
permissions.
d:\Program Files\Microsoft Visual Studio 9.0\VC>tf lock /?
TF - Team Foundation Version Control Tool
Copyright (c) Microsoft Corporation. All rights reserved.
Locks or unlocks a file or folder to deny or restore the permissions of users
to check out an item for edit into a different workspace or to check in pending
changes to an item from a different workspace.
tf lock itemspec /lock:(none|checkout|checkin) [/workspace:workspacename]
[/server:servername] [/recursive]
Buck
From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Hunter
Sent: Sunday, March 01, 2009 8:10 PM
To: [email protected]
Subject: RE: Phantom lock issue
Just an Update.
Deleted the records...
Seems fine now....
Cheers
Matt.
From: Matthew Hunter [mailto:[email protected]]
Sent: Monday, 2 March 2009 12:59 PM
To: [email protected]
Subject: RE: Phantom lock issue
Did a little more research...
Looking at the tbl_lock table in SQL, there are 4 PNG files locked and using
the below SQL statement, I can see that there's not corresponding pending
change file....
select * from tbl_lock l
left join tbl_pendingchange pc on l.pendingchangeid = pc.pendingchangeid
where fullpath like '$\CRM\%png%'
Does anyone know if it's safe to delete these records from tbl_lock table -
seeing there's no corresponding pending change record?
Cheers
Matt.
From: Matthew Hunter [mailto:[email protected]]
Sent: Monday, 2 March 2009 12:42 PM
To: [email protected]
Subject: Phantom lock issue
Hi Guys,
I've been having a bit of trouble unlocking a PNG file in TFS.
I first found out when I tried to move the files in VS 2008 and it came up
with a message indicating that the file was checked out.
I then had a look and could not find any indication that the file was actually
checked out, apart from the tooltip when you hover above the file - indicating
that it's still checked out
Running the 'tf lock /lock:none etc....' command rendered the following error:
TF10152: The item <file path> must remain locked because its file type
prevents multiple check-outs.
So then I allowed multiple checkouts on that type of file and now I'm getting
the following error with the same command:
TF14090: Cannot unlock <file path>. It is not currently locked in your
workspace.
Tfs seems that Visual Studio thinks the file is checked out when clearly it
isn't.
I also doesn't appear to be shelved and I've even got the user to un-map the
path from their workspace which didn't help - clearing the cache from my
profile didn't help either.
Any ideas?
Cheers
Matt.
________________________________
[cid:[email protected]]
Matthew Hunter
Dynamics CRM Lead Technical Consultant
Stargate Group
Level 3, 600 Victoria Street
Richmond Victoria 3121
Telephone:
03 8420 3033
Facsimile:
03 8420 3133
[cid:[email protected]]<http://www.stargategroup.com.au/>
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately if you have received this e-mail by mistake and delete this e-mail
from your system. No responsibility is assumed by the company or its employee
to any other person for any loss or damage (whether caused by negligence or
not) arising from the use of the information and advice contained herein.
Finally, it is your responsibility to check any attachments for viruses and
defects before opening or sending them on.
________________________________
________________________________
Support procedure: https://www.codify.com/lists/support
List address: [email protected]<mailto:[email protected]>
Subscribe: [email protected]<mailto:[email protected]>
Unsubscribe: [email protected]<mailto:[email protected]>
List FAQ: http://www.codify.com/lists/oztfs
Other lists you might want to join: http://www.codify.com/lists
________________________________
Support procedure: https://www.codify.com/lists/support
List address: [email protected]<mailto:[email protected]>
Subscribe: [email protected]<mailto:[email protected]>
Unsubscribe: [email protected]<mailto:[email protected]>
List FAQ: http://www.codify.com/lists/oztfs
Other lists you might want to join: http://www.codify.com/lists
________________________________
Support procedure: https://www.codify.com/lists/support
List address: [email protected]<mailto:[email protected]>
Subscribe: [email protected]<mailto:[email protected]>
Unsubscribe: [email protected]<mailto:[email protected]>
List FAQ: http://www.codify.com/lists/oztfs
Other lists you might want to join: http://www.codify.com/lists
--------------------------------------------------------------------------------
Support procedure: https://www.codify.com/lists/support
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/oztfs
Other lists you might want to join: http://www.codify.com/lists
<<inline: image001.gif>>
<<inline: image002.jpg>>
