Can't commit to SVN server

R

10

7

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?

Rent answered 26/10, 2011 at 21:21 Comment(0)

C

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).

Centistere answered 26/10, 2011 at 21:48 Comment(2)

Found 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! – Rent 26/10, 2011 at 22:19

I had the same error and the file permissions on the repo were wrong o n the SVN server. – Probabilism 4/11, 2011 at 21:49

A

8

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.

Aegina answered 26/10, 2011 at 21:27 Comment(4)

its not low... i have 300 GB free space – Rent 26/10, 2011 at 21:27

Tried to delete the folder and checkout an new directory, make the changes and to commit. Got the same error. – Rent 26/10, 2011 at 21:53

Cheers, fixed my issue. "svn: Server sent unexpected return value (500 Internal Server Error) in response to POST request for /svn/<site>/!svn/me" – Upon 4/5, 2012 at 21:28

Thanks! Same problem, same fix! – Dowzall 14/11, 2012 at 22:6

W

4

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!

Waterside answered 30/1, 2012 at 20:4 Comment(1)

After 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. – Suppositious 22/12, 2015 at 11:10

R

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>

Ron answered 29/3, 2012 at 17:25 Comment(1)

JIC: such solution doesn't apply to VisualSVN Server. – Billie 26/10, 2012 at 12:5

F

2

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.

Fluidize answered 16/12, 2011 at 23:37 Comment(0)

B

2

There are two possible reasons for the error:

Service account under which VisualSVN Server runs does not have permissions to access
- C:\Repositories\<repo>\ and/or
- C:\Repositories\<repo>\db\,
- C:\Repositories\<repo>\db\transactions\,
- C:\Repositories\<repo>\db\txn-protorevs\.
Some of folders located under C:\Repositories\<repo>\db\ are missing. E.g. the same
- C:\Repositories\<repo>\db\transactions\ and
- C:\Repositories\<repo>\db\txn-protorevs\.

Billie answered 9/10, 2013 at 11:3 Comment(0)

C

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).

Centistere answered 26/10, 2011 at 21:48 Comment(2)

Found 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! – Rent 26/10, 2011 at 22:19

I had the same error and the file permissions on the repo were wrong o n the SVN server. – Probabilism 4/11, 2011 at 21:49

R

1

Also ensure that you haven't deleted the following directories within the repository store.

.../db/transactions
.../db/txn-protorevs

If you have, simply recreate them. They are usually empty directories.

I had this problem on a repository which had been working. I checked & modified the permissions as suggested in earlier posts but it didn't help.

What happened? I stupidly ran a program which removes empty directories. I had to create a new repository & do a comparison of the directory structure before realising my mistake.

Ridenhour answered 18/8, 2012 at 16:29 Comment(0)

C

0

if you use an Tortoise SVN client: this is an authentication issue on your actual client and does not have anyting to do with your read/write permissions on the server or anything else.

right click on your working folder (copy) -> TortoiseSVN -> SVN Settings -> saved data -> authentication data and click clear all.

I had a similar issue and after reseting of my saved authentication data I was able to commit and update with no probs.

cheers.

Clava answered 2/2, 2014 at 15:43 Comment(0)

S

-1

when i backup my svndb from another computer, i can not commit and tsvn return the same errors"The POST request returned invalid XML in the response..." i found the " YOURsvnDB\db\txn-current" file is different with my old svndb, after recovering it, the commit works well

Scan answered 2/11, 2011 at 3:28 Comment(0)

S

-2

Hi if you use httpd as proxy, might be ownership of svn repository causing the issue. should be

drwxr-xr-x   apache apache   svnrepository

please make sure the configuration something like this subversion.conf

Sangsanger answered 10/7, 2016 at 3:47 Comment(0)

Recommended topics

Hot tags