I experienced the same issue in VisualSVN 3.2.2. While re-installing the application would solve the problem, I was able to solve the problem by restarting the VisualSVN Server service.
I've submitted a bug report to VisualSVN (they don't appear to have a public issue tracker).