Subversion error messages and how to resolve them.
Why do I get random "Access Denied" errors on Windows?
These appear to be due to the various Windows services that monitor the filesystem for changes (anti-virus software, indexing services, the COM+ Event Notification Service).
Why doesn't svn switch work in some cases?
In some cases if there are unversioned or ignored items in the working copy, svn switch can produce an error. The switch stops, leaving the working copy half-switched.
Why can't I see the log entry for the file I just committed?
Assume you run svn checkout on a repository and receive a working copy at revision 7 (aka, r7) with one file in it called foo.c. You modify the file and commit it successfully. Two things happen: The repository moves to r8 on the server and in your working copy, only the file foo.c moves to r8. The rest of your working copy remains at r7.
Why does my --diff-cmd complain about -u when I try to override it with --extensions?
When using an external diff command, Subversion builds a fairly complicated command line. If your preferred diff command does not support these arguments, you may need to create a small wrapper script to discard arguments and just use the last couple file paths.
My repository keeps giving errors "Cannot allocate memory". What should I do?
It usually means that a Berkeley DB repository has run out of database locks (this does not happen with FSFS repositories). It shouldn't happen in the course of normal operations, but if it does, the solution is to run database recovery as described here. If it happens often, you probably need to raise the default lock parameters (set_lk_max_locks, set_lk_max_lockers, and set_lk_max_objects) in the db/DB_CONFIG file. When changing DB_CONFIG in an existing repository, remember to run recovery afterwards.
My repository seems to get stuck, giving me DB_RUNRECOVERY errors. What could be the cause?
The Berkeley DB database in your repository is sensitive to interruptions. If a process accessing the database exits without "cleanly" closing the environment, then the database is left in an inconsistent state. Common causes of this include: the process exiting when it hits a permission problem the process crashing/segfaulting the process being forcibly killed running out of disk space.
VS.NET/ASP.NET seems to have a problem with the ".svn" directory name. What should I do?
VS.Net has a subsystem called ASP.Net, which uses WebDAV to do remote publishing through IIS. This subsystem rejects any pathname that starts with ".", which causes a problem when you try to remotely publish a Subversion working copy, because of the ".svn" subdirectories. The error message says something like "unable to read project information".
Why doesn't HTTP Digest auth work?
This is probably due to a known bug in Apache HTTP Server (versions 2.0.48 and earlier), for which a patch is available. See the links below for more information.