Menu
I have a folder in a repository that cannot commit and even parent folders cannot commit. This happened several weeks ago, then worked, then on the blink again. I have cleared my authentication cache and no help. I can still work with other trunks but not this one and the error message does not help me where to go. I have done Clean Up. I have created a new directory from VisualSVN from the repository and same problem. Would you have any suggestions? Can I nuke the .svn folder and help? I don't want to start with a new repo because we have TeamCity integrated and watching. Help and thanks in advance! Doug
**Error: Commit failed (details follow):
Error: Server sent unexpected return value (501 Not Implemented) in response to
Error: PROPFIND request for '/svn/MAHCP/trunk/src/RssaSolution/Mahcp.Rssa'**
I posted to SVNForum as well but has anyone else had this crazy situation!
822
The HyperText Transfer Protocol (HTTP) 501 Not Implemented server error response code means that the server does not support the functionality required to fulfill the request. This status can also send a Retry-After header, telling the requester when to check back to see if the functionality is supported by then.
An svn commit of the file will fail with an “out-of-date” error. The file should be updated first; an svn update command will attempt to merge the public changes with the local changes. If Subversion can't complete the merge in a plausible way automatically, it leaves it to the user to resolve the conflict.
That's usually a proxy or virus scanner/firewall rejecting DAV requests (PROPFIND is not a 'normal' http request but used with DAV).
So: check your proxy and/or virus scanner/firewall and configure them to allow DAV requests.
Also, sometimes it help to use https instead of http so that those apps can't check the network traffic anymore and interfere with it.
75
There was an old outdated URL to the repository trunk. I wish the error was a bit more descriptive. Thanks guys....if I had more reputation I'd grant you both points!
40
answered Oct 04 '22 12:10
The answer was that the svn server URL had been changed previously and then when trying to check it back in it would error. The trick then was to nuke the .svn folders, pull down fresh and then copy over with my new changes. I wish the error message had been better.
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
