Hello again, Who has not gone to work with source control (Team Foundation Server, for example) are going to work on a file and says it has "caught" another person and this is on vacation and no way to find her? Well today me but instead of being on vacation was at a meeting. I followed to solve / the following steps: - Using console (a lifelong cmd) I set to "C: \\ Program Files \\ Microsoft Visual Studio 9.0 \\ Common7 \\ IDE" (this path may vary depending on the OS and the version of Visual Studio installed) - Run the command: tf lock / lock: none / workspace: developerWorkspace; developerUsername / project / folder / file / s: http://tfsserver:8080/ (replacing the data generated by our own) - I get the following message: TF30063 : You are not Authorized to access XXXXXX. and asks us to put our admin user
TFS Now two things can happen: it is resolved or the following message appears:
TF10152: The item $ / XXXXXXX / XXXXXXXXX / XXXX.cs Because Must Remain locked STI Prevents file type multiple check-outs. If it appears to us we put the following: - tf undo / workspace: developerWorkspace; developerUsername $ / Project / folder / file / s: http://tfsserver:8080/ - TF30063: You are not Authorized to access XXXXX. We put user and pass y. .. BIEEENNNNNN
The operation completed successfully. Because the workspace XXXXX, username is Not on this computer, You Must Perform a get operation in That Separate workspace to update it with the Changes That Have Been Made on the server.
As always, make a backup just in case.
Published 21/05/2010: It is important to specify the workspace of the person who has left caught the file and the username of the person. Later, when we ask the user / pass we introduce the person with privileges Salu2
0 comments:
Post a Comment