On Mon, Apr 20, 2009 at 6:20 PM, David <c0br...@gmail.com> wrote: > > I have just upgraded from version 1.6.4 to version 1.7.1, and I am now > experiencing issues with locking. I have also upgraded my local > clients (TortoiseSVN and AnkhSVN) to their latest build. > > Steps to reproduce: > Their exists a file (a crystal report file) with the needs-lock > property set. > Lock the file. > Edit the file. > When trying to commit the file it gives errors, here are the errors > from the VisualSVN server event log: > > This resource is locked and the "If:" header did not specify one of > the locktokens for this resource's lock(s). [423, #0] > [client 192.168.0.239] > Hi David,
I cannot reproduce your error with latest VisualSVN Server 1.7.1 and TortoiseSVN 1.6.1. Please try to remove locks on the server. To do this please execute following command on the server command line prompt (accessible from VisualSVN Server Manager): svnadmin rmlocks REPOS_PATH LOCK_PATH Where REPOS_PATH is path to your repository (C:\repositories\repos e.g.), and LOCK_PATH is path in repository (/test/file e.g.) -- Ivan Zhakov VisualSVN Team
