views:

4999

answers:

6

Users attempting to check out files from a particular Subversion 1.4.x repository with Apache 2.2 on Windows 2003 have suddenly begun getting an error message in their log windows upon checkout with TortoiseSVN 1.4:

Error REPORT request failed on '/[path_to_repo]/!svn/vcc/default'
Error REPORT of '/[path_to_repo]/!svn/vcc/default': 200 OK (http://[server_name])

This started following an hd crash on the server and subsequent restore of about 10 subversion repositories. Only one repository is having this problem after an attempted working directory reconciliation. The repo owner reconcile their working directory with the repository by modifying/deleting the hidden .svn directories (though this was not advised).

I can't find anything on the Internets that represents my situation. The restored server is exactly as the original and no other repositories on this server are throwing errors. Any ideas on 1) what this error is and 2) how to fix it?

A: 

i have the same problem when i check out one projects from my repositories,but the other projects is ok? can any one fix it? email me

A: 

I came cross the same problem when using TortoiseSVN. If I use SLikSVN, then checkout is ok without any problem. I guess the issue is with TortoiseSVN. It may send unsupported protocol/command to SVN server like "!svn/vcc/default/report".

bionicoder
+1  A: 

this helped me: http://programmers-blog.com/2008/09/05/svn-target-path-does-not-exist

A: 

I came across this using both Sliksvn and TortoiseSVN (when doing a fresh checkout of the same branch in a large repo) under WinXPsp3-32.

Every time it happens in the same place. If one restarts the checkout by executing the same syntax again, the checkout starts at the same point and finishes successfully- no matter whether one uses the TortoiseSVN or the command line client. Can't say more than that, except I don't get the above link is really sayinng.

dr0wn3d
+2  A: 

The incidence of the SVN error {REPORT of '/svn/xxxx/!svn/vcc/default': 200 OK} when attempting the Checkout or Update in SVN was eventually resolved on our site by restarting the SVN Server.

Georgia
A: 

Simply restart the svn server this will solve your problem

Bhushan G Ahire