SVN Error - 501 Not Implemented Commit Failed

16,615

Solution 1

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!

Solution 2

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.

Solution 3

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.

Share:
16,615
dodegaard
Author by

dodegaard

Updated on June 08, 2022

Comments

  • dodegaard
    dodegaard almost 2 years

    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!

  • dodegaard
    dodegaard about 15 years
    thanks stefan....we are using https but will check the DAV piece and let you know
  • Deqing
    Deqing about 10 years
    Proxy issue is what I came across regarding this problem