title: 'Folder' already locked by 'Folder'
body: <p>I have this very VERY annoying issue where I'm attempting to merge our trunk into my branch for some updates. I have been doing this on a daily basis but almost every single day I get the following error:</p>
  
  <pre><code>Error - 'D:\Code\Website' is already locked via 'D:\Code\Website'.
  </code></pre>
  
  <p>Only very randomly does this error not happen and I am able to successfully merge trunk back into the branch. However, all day I've been trying to get the latest from the trunk without success. I have looked high and low for answers to this issue.. SO, Google, random forums on the internet... etc. I'm hoping someone can shed some light on why this might be happening.</p>
  
  <p>This is what I've already tried:</p>
  
  <ul>
  <li>Run "Clean up" on every single folder within the directory.</li>
  <li>Checked for "lock" file in .svn directory - doesn't exist.</li>
  <li>Opened wc.db file and checked WC_LOCK table - nothing in there.</li>
  <li>Disabled anti-virus.</li>
  <li>Disabled IIS.</li>
  <li>Checked out a fresh copy of the branch.</li>
  <li>Updated TortoiseSVN</li>
  <li>Completed uninstalled and re-installed TortoiseSVN with latest MSI from TortoiseSVN.net (1.7.10.23359, SVN 1.7.7).</li>
  </ul>
  
  <p>I am able to Update the branch and Commit it.. there has never been an issue with that. It's just Merging trunk back in that is causing me issues. No one else on the team seems to have this problem (with this branch, or any others). They can freely check the branch out.. merge trunk in and commit it without issues.</p>
  
  <p>I am using TortoiseSVN. Any help you guys/gals have would be fantastic!</p>
  
  <p>EDIT: Also, a Test Merge works.. but an actual Merge doesn't.</p>
  
  <p><strong>UPDATE</strong></p>
  
  <p>It turns out TSVNCache.exe CONSTANTLY holds locks on the wc.db file. I have no idea why. Even if I kill the process; once I go through the TSVN Merge GUI it fires up the cache again and locks it. I have managed to successfully merge via the command line.. is there any way to fix the cache locking issue to avoid having to rely on the command line?</p>