title: Subversion: Locking files fails
body: <p>I just migrated some Subversion repositories from a Windows 2003 server to a Windows 2008 server, and upgraded Subversion from 1.5 to 1.7 in the process. Checkout and commit works, however when users try to lock files, they get this message:</p>
  
  <blockquote>
    <p>Error: LOCK of '/SVN/TempRepo_OnlyToPlayWith/Documents/Test.docx': Could not read<br>
    Error:  status line: An existing connection was forcibly closed by the remote host.<br>
    Error:  (https://subversion.mysite.com)</p>
  </blockquote>
  
  <p>(Where <a href="https://subversion.mysite.com" rel="nofollow">https://subversion.mysite.com</a> is the site where subversion is hosted)</p>
  
  <p>I've been searching for what the problem might be, without luck.</p>
  
  <p>Help me, StackOverflow - you're my only hope.</p>
  
  <p>Edit:</p>
  
  <p>Some more investigation has uncovered that, when I don't go through https, but use Tortoise on the server directly to the repo using file:///, I get the following error message:</p>
  
  <blockquote>
    <p>Error: Can't open file
    'D:\SVNRepositories\TempRepo_OnlyToPlayWith\db\write-lock':<br>
        Error:  Access is denied.</p>
  </blockquote>
  
  <p>However, using the command-line svn tool from a console with administrator privileges works without problems.</p>
  
  <p>Could this really just be a problem with read/write permissions? And if so, why does checkout/commit/etc. work, but not locking files in the repository?</p>
  
  <p>More edit:</p>
  
  <p>Apparently, after investigating the event log, it seems that httpd.exe keeps crashing, blaming mod_dav.so:</p>
  
  <blockquote>
    <p>Faulting application name: httpd.exe, version: 2.2.21.0, time stamp: 0x4e6a3015
    Faulting module name: mod_dav.so, version: 2.2.21.0, time stamp: 0x4e6a3023</p>
  </blockquote>