Can't commit to SVN server
Solution 1
You can use Fiddler2 as a proxy, and inspect the XML request/responses. Maybe that'll give you some more to go on. It looks like TortoiseSVN doesn't use WinInet, so the proxy won't be automatic. You'll need to set a proxy in the network panel of Tortoise. ex: localhost port 8888. Then you'll see data arriving in Fiddler. Shut down your browser and stuff so you don't have clutter. Now see if you can do something simple like view a log or commit a small change. You should see the packets, and then you can use the "inspector" on the right-hand panel to view the XML (use XML or RAW tab).
Solution 2
Check your server's disk space. It's probably really low. Once you free some up it should work.
Edit: Reference = http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2858308
Second Edit: Another suggestion would be to back up the files, delete the offending directory, update, restore changes, and then commit.
And another Post (http://osdir.com/ml/version-control.subversion.tortoisesvn.devel/2005-03/msg00140.html) discusses editing the SVN entries file.
Solution 3
I'm running VisualSVN Server 2.5 on Windows 2k8. Recently I upgraded my server and used Acronis Backup to transfer the current state of the server to a new SSD array in a new machine. Everything went smoothly, but when I attempted to commit a few files to one of the repos on this box, I got a very weird error:
The POST request returned invalid XML in the response: XML parse error at line 3: not well-formed (invalid token) (/svn/repo-name/!svn/me)
It turns out that with my particular case, this was a PERMISSIONS issue. After spending an hour and a half on this I finally tracked down a simple solution that "worked for me". The million dollar fix?
Open the VisualSVN Server GUI.
Right-Click on "VisualSVN Server (domain)" at the root of the left navigation pane and select "Properties".
-
Under the General Tab, you will see a check box for "Automatically adjust permissions".
A. If this is not checked, check it and click "Apply". This will stop and restart the VisualSVN service and should fix the issue.
B. If this is checked, un-check it and click "Apply". This will stop and restart the Visual SVN service. Once complete, re-check the option and click "Apply" once more. After the service is restarted, the issue should now be resolved.
I hope this helps someone in need!
Solution 4
We had a very similar problem, but using Apache HTTPd server on Linux. TortoiseSVN 1.6 worked without error on XP/32. ToroiseSVN 1.7 on Win7/64 could checkout, but could not commit; it returned the error /svn/!svn/me path not found. Solution: added a missing "alias" directive to the httpd.conf section for svn.
The correctly-functioning httpd.conf section with the new alias directive looks like:
alias /svn /srv/svn/repos
<Location /svn>
DAV svn
SVNPath /srv/svn/repos
AuthType Basic
AuthUserFile /path/to/.htpasswd
Require valid-user
</Location>
Solution 5
I had exactly the same problem. When i used tortoise 1.6 I did get a better error message indicating access denied. Fixing the access on my server to the repositories fixed my problem.
CaTz
Updated on July 09, 2022Comments
-
CaTz almost 2 years
When I commit to the server this returns:
The POST request returned invalid XML in the response: XML parse error at line
3: not well-formed (invalid token) (/svn/site/!svn/me)I am using VisualSVN Server 2.5.1 and the client is TortoiseSVN 1.7.1 64Bit.
The server by itself is working, I can update from repository or browse.
Any suggestions?
-
CaTz over 12 yearsits not low... i have 300 GB free space
-
CaTz over 12 yearsTried to delete the folder and checkout an new directory, make the changes and to commit. Got the same error.
-
CaTz over 12 yearsFound the problem. I returned to tortoiseSvn 1.6 And tried to commit, then i got other error, SVN “Can’t create directory” Error and by that site: troyhunt.com/2010/01/svn-cant-create-directory-error.html, i added those folders (i copy the repositories folder from other HDD) the commit started to work. then i returned to the 1.7.1 version. and its work there also!
-
Tony over 12 yearsI had the same error and the file permissions on the repo were wrong o n the SVN server.
-
Luke almost 12 yearsCheers, fixed my issue. "svn: Server sent unexpected return value (500 Internal Server Error) in response to POST request for /svn/<site>/!svn/me"
-
bahrep over 11 yearsJIC: such solution doesn't apply to VisualSVN Server.
-
Michael Kennedy over 11 yearsThanks! Same problem, same fix!
-
Pino over 8 yearsAfter having migrated my VisualSVN repository to a VM I was getting a different error msg on commit ("could not begin a transaction") but your solution worked, thanks.