I've been using VisualSVN for over half a year now and it's been working flawlessly and been very stable.
All this changed after I removed one of the repositories (out of 2; I wanted to change name but it wasn't possible so I removed it and added a new one). After this had been done, all I got was "403 Forbidden" whenever I tried to contact the server in any way. The same behaviour was met with a number of other user accounts and even when trying to browse the repository locally (on the server) caused this error. After a bit of investigation, it turned out that the authorization information for the recently removed repository still existed in the "authz" file located on repository root level (the very, very top level, meaning the one globally used for all repositories). After I removed the obsolete authorization data, everything was back to normal again. So if you've just hit the "403 Forbidden" problem after having removed a repository, check the "authz" file and remove the authorization data for the repository you just removed. I suspect this is due to buggy parsing of the file by VisualSVN; and also, VisualSVN does not remove obsolete authorization data from the file upon deletion of a repository.
