Top-level SVN Update no longer works. Any advice, please?

29 views
Skip to first unread message

adds...@gmail.com

unread,
Feb 7, 2018, 10:02:23 AM2/7/18
to TortoiseSVN
Whenever I try to do a top-level SVN update these days, I get the following error message(s):


The XML response contains invalid XML

Malformed XML: not well-formed (invalid token)


And no files are added/updated.

Executing the Cleanup command (checking all but the bottom three boxes) doesn't fix the problem, although I find I can usually still successfully update individual directories.

A workmate suggested there might be too many subdirectories and/or some filenames that are too long.

I'm afraid I'm an example of "A little knowledge is a dangerous thing" when it comes to Tortoise SVN :-)

I couldn't see any obvious help in the FAQ. If a kind and knowledgeable soul could steer me in the right direction, I'd be grateful.

Thanks for reading.

Stefan

unread,
Feb 7, 2018, 2:03:03 PM2/7/18
to TortoiseSVN


On Wednesday, February 7, 2018 at 4:02:23 PM UTC+1, (unknown) wrote:
Whenever I try to do a top-level SVN update these days, I get the following error message(s):


The XML response contains invalid XML

Malformed XML: not well-formed (invalid token)


And no files are added/updated.

Executing the Cleanup command (checking all but the bottom three boxes) doesn't fix the problem, although I find I can usually still successfully update individual directories.

A workmate suggested there might be too many subdirectories and/or some filenames that are too long.

You can try a few things:
* use the repo browser dialog and check if there are files with weird names in the folder which is your working copy root. If there are files with chars in their names like "/\?*" or filenames that start with "con", "prn", "com", then that might be a hint. Delete those files directly in the repo browser.
* try to check out a fresh working copy
* configure your virus scanner to leave the TortoiseProc.exe process alone, and also your working copy

Usually, this error happens due to interference from virus scanners.

If that doesn't work, you should ask on the svn users list for help, since the error is from the svn library code:
http://subversion.apache.org/mailing-lists.html

Stefan

adds...@gmail.com

unread,
Feb 8, 2018, 5:52:54 PM2/8/18
to TortoiseSVN
Thanks, Stefan. I will try those things.
Reply all
Reply to author
Forward
0 new messages