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] I am also seeing this error in the event log: The locktoken specified in the "Lock-Token:" header did not specify one of this resource's locktoken(s). [400, #0] [client 192.168.0.239] I have tried to downgrade back to version 1.6.4, but this seems to be not allowed (Error message: Newer version of VisualSVN Server is already installed.) Is there either a quick fix to the locking problem, or an easy way to downgrade? Or am I going to have to dump the repository and completely uninstall VisualSVN, reinstall/configure, and import the repository, do permissions... etc... ? Thanks for any advice, David
