Hello, > I have a Windows 2008 server running Visual SVN Server 2.7.12 - I attempted > via TortoiseSVN 1.8.10 to right-click and "Edit Log Message" (after an SVN > Show Log) and when I clicked OK after edit received the following error > message: > > “DAV request failed; it’s possible that the repository’s pre-revprop-change > hook either failed or is non-existant. Repository has not been enabled to > accept revision propchanges; ask the administrator to create a > pre-revprop-change hook.” > > This error seemed straight forward to me - no script! I went into my visual > server manager, right-clicked on my repository and selected properties. I > then selected the "Hooks" tab. I selected the "Pre-revision property change > hook" and then clicked "Edit". The only entry I put in the script for > testing was "exit 0" and then clicked "OK". I still am receiving the same > error from the Tortoise SVN client. > > I thought it must not have saved the changes but I can browse to the "hooks" > folder in my repository and I do see a "pre-revprop-change.cmd" file in this > folder. I also can edit this file directly as well but putting anything in > this script yields the same error. > > Is there another configuration setting I might be missing?
The error that you've specified indicates that most likely the hook script does not exist at all. It's just a wild guess, but are you sure that you created the hook script for the same repository that you access using TortoiseSVN? Entering just "exit 0" (without quotes) to pre-revision property change hook (pre-revprop-change.cmd) should be enough to allow any authorized user to modify revision properties, so I suggest double-checking whether you added the hook to the correct repository. There is another possible cause to this issue. This behavior can occur when the service account that runs VisualSVN Server services (it's Network Service by default) lacks access permissions to the "/hooks" directory of the particular repository. In such case none of the hook scripts configured for this repository will work. The service account must have Modify access to the directory where you store your repositories (e.g. C:\Repositories) and all its contents. See the KB article "Permissions required to run VisualSVN Server" at https://www.visualsvn.com/support/topic/00037/ -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at http://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
