Unable to commit to Subversion

Question

I have a client who had to rebuild his automated build server. He checked out his project folder from my subversion server but is now no longer able to commit - he gets this err

Answer 1

Had same problem, restarting apache fixed the issue.

Answer 2

I had the same error code, but the error turned out to be caused the CNTLM proxy which I had recently installed on my local machine.
To resolve the issue I had to add an additional domain suffix to the proxy bypass exception list, in order to be able to commit to the team svn server hosted onsite.

Answer 3

Mount Point for SubVersion repository was full in our case, adding more space.

Answer 4

I did a one vote up for @DamianM answer. In my case it seems that had been the problem. File Corruption which made it not possible to write on server. Issue with SVN Commit for certain File Extension

But Instead of restarting your svn server process / reboot server I copied the dlls[files with problem] again to working folder and was able to commit.

Answer 5

You can clear this error w/out a reboot:

1. Identify (or create) a directory in the root SVN repository that was not a part of the failed commit.

2. Create a new file in the directory from step 1.

3. Commit the new file (and directory if created in step 1). Because the file is new, it doesn't conflict w/the previous commit and can update the revision # on the server.

4. Commit the original files/directories.

5. Delete the new file (and directory if created in step 1).

6. Commit the entire tree.

**Steps 5 & 6 aren't required, but I like to keep my repository tidy...

I get this error a lot b/c SVN frequently conks out in the middle of committing my large files, which in turn causes subsequent commits to try to write to the revision that was interrupted.

Answer 6

Ewan

I ran into the exact same issue with Visual SVN Server installed on Windows 2003, I had altered the default install to place the Repository folder onto a separate partition since the servers C drive is small. I had to change the permission to that folder (in this case D:\Repository), as a quick and dirty hack I simply added the "Everyone" user to this folder and selected "Modify" rights (not the most secure for sure but a dirty working hack none the less). This resolved the issue.