1.7 - The POST request returned invalid XML in the response

1,156 views
Skip to first unread message

James Marsh

unread,
Oct 18, 2011, 4:42:27 AM10/18/11
to us...@tortoisesvn.tigris.org
Hi there, i'm a new user of the forum.
I hope this is the right place to post this.

We've just upgraded to SVN 1.7 and TortoiseSVN 1.7 and a recent check in attempt resulted in the following error being shown by TortoiseSVN, I initially thought it might have been the upgrade causing a problem:-

“The POST request returned invalid XML in the response: XML parse error at line 3: not well-formed (invalid token) (/svn/[REPOPATH]/!svn/me)”


I couldn't find any reference to this error anywhere on here, or via google etc.

Tried various things... Cleanup and try again (fail), Only checking in one file (fail), Checking out the repository again and making the change then checking back in - no joy.

There isn't really any specific enough information to identify the problem - it was only when we noticed that disk space on the server had got low that the cause was identified - svn couldn't check the file in because there wasn't enough space on the server!

I'm posting this in the hope that anyone else who gets this error will find this post and realise that a likely candidate is disk space on your server.

Also - might be worth amending TortoiseSVN so that it gives possible solutions to the errors it encounters?


James.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2858308

To unsubscribe from this discussion, e-mail: [users-un...@tortoisesvn.tigris.org].

Simon Large

unread,
Oct 18, 2011, 6:18:46 AM10/18/11
to us...@tortoisesvn.tigris.org
On 18 October 2011 09:42, James Marsh <james...@poz.co.im> wrote:
> Hi there, i'm a new user of the forum.
> I hope this is the right place to post this.
>
> We've just upgraded to SVN 1.7 and TortoiseSVN 1.7 and a recent check in attempt resulted in the following error being shown by TortoiseSVN, I initially thought it might have been the upgrade causing a problem:-
>
> “The POST request returned invalid XML in the response: XML parse error at line 3: not well-formed (invalid token) (/svn/[REPOPATH]/!svn/me)”
>
> I couldn't find any reference to this error anywhere on here, or via google etc.
>
> Tried various things... Cleanup and try again (fail), Only checking in one file (fail), Checking out the repository again and making the change then checking back in - no joy.
>
> There isn't really any specific enough information to identify the problem - it was only when we noticed that disk space on the server had got low that the cause was identified - svn couldn't check the file in because there wasn't enough space on the server!
>
> I'm posting this in the hope that anyone else who gets this error will find this post and realise that a likely candidate is disk space on your server.
>
> Also - might be worth amending TortoiseSVN so that it gives possible solutions to the errors it encounters?

Thanks for the info. Unfortunately it is hard to diagnose a server
error when the error message from the server itself is misleading. As
you say this is not a common error at all because it doesn't come up
in Google, so adding a suggestion to TortoiseSVN is unlikely to be
helpful to anyone.

But it would be worth sending this information to the Subversion users
mailing list in the hope that the server code can be fixed to produce
a better error message.

Simon

--
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2858345

Methuselah Ngetich

unread,
Oct 24, 2011, 7:58:50 AM10/24/11
to us...@tortoisesvn.tigris.org
I had this exact error having recently upgraded to version 1.7 but on further scrutiny i discovered that the was not enough space on the server. You could be having a different issue tho.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2862366

Alan Howard

unread,
Nov 3, 2011, 7:05:29 PM11/3/11
to us...@tortoisesvn.tigris.org
I got the same error message also having recently upgraded to 1.7. Clearing some space on the server also fixed it for me. Thanks for the pointer.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2872564

Cristian Lorand

unread,
Nov 12, 2011, 4:41:17 AM11/12/11
to us...@tortoisesvn.tigris.org
Hi,

I'm new to this forum. I found this post searching google for the error you
mentioned, in the mean time I resolved the issue:
the subversion project folder had the user set to "root" and the group to
"www-data", but the group didn't have write rights to the project folder. I
changed the rights to (2)775 and it works great.

Cristian

--
View this message in context: http://old.nabble.com/1.7---The-POST-request-returned-invalid-XML-in-the-response-tp32673269p32830488.html
Sent from the tortoisesvn - users mailing list archive at Nabble.com.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2877494

Felix Saphir

unread,
Nov 12, 2011, 9:36:17 AM11/12/11
to us...@tortoisesvn.tigris.org
Am 12.11.2011 10:41, schrieb Cristian Lorand:

[TOFU fixed]


>
> James Marsh-2 wrote:
>>
>> We've just upgraded to SVN 1.7 and TortoiseSVN 1.7 and a recent check in
>> attempt resulted in the following error being shown by TortoiseSVN, I
>> initially thought it might have been the upgrade causing a problem:-
>>
>> “The POST request returned invalid XML in the response: XML parse error at
>> line 3: not well-formed (invalid token) (/svn/[REPOPATH]/!svn/me)”

[...]

>> There isn't really any specific enough information to identify the problem
>> - it was only when we noticed that disk space on the server had got low
>> that the cause was identified - svn couldn't check the file in because
>> there wasn't enough space on the server!
>

> I'm new to this forum.

What forum?

> I found this post searching google for the error you
> mentioned, in the mean time I resolved the issue:
> the subversion project folder had the user set to "root" and the group to
> "www-data", but the group didn't have write rights to the project folder. I
> changed the rights to (2)775 and it works great.

Well, thank you for sharing this information, but please note that this
is a server issue and therefore not a problem with Tortoise-SVN.

The error message is generated in the svn library AFAIK, you might want
to post your request on their mailing list.

Felix

P.S. Please don't top-post

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2877533

perl forst

unread,
Dec 27, 2011, 5:17:46 AM12/27/11
to us...@tortoisesvn.tigris.org
I got the message "XML parse error at line 5..." (Tortoise Client 1.7)
because the file was still locked on another workstation (Tortoise
Client 1.6). Unlocking the file resolved the issue.

perl

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2902184

Reply all
Reply to author
Forward
0 new messages