RE: FW: The REPORT request returned invalid XML in the response: XML parse error at line ...

That path was manually altered, it pointed to an existing file
in the repository.

Can't give you that reproduction recipe, was afraid you were going
to ask that. In fact, that particular project has 30+ people working
on a 15k files repository. This was the second time I encountered
this problem in almost 3 months.

Next time we encounter it I'll make a copy of that working copy so
I can try out some actions.

regards,

Lieven.

-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net] On
Behalf Of kfogel@collab.net
Sent: maandag 29 augustus 2005 18:03
To: GOVAERTS Lieven
Cc: dev@subversion.tigris.org
Subject: Re: FW: The REPORT request returned invalid XML in the response:
XML parse error at line ...

"GOVAERTS Lieven" <Lieven.GOVAERTS@post.be> writes:
> Perhaps more a question to the developers.

If we can get a reproduction recipe, we can debug tihs. If we can't get a
recipe, we probably can't go anywhere with it.

That's a strange path in the error message. Is it a real path, or is path
corruption part of the problem here?

-Karl

--
www.collab.net  <>  CollabNet  |  Distributed Development On Demand
> -----Original Message-----
> From: GOVAERTS Lieven [mailto:Lieven.GOVAERTS@post.be] 
> Sent: vrijdag 26 augustus 2005 16:48
> To: users@subversion.tigris.org
> Subject: The REPORT request returned invalid XML in the response: XML
> parse error at line ...
> 
> Hi, 
> 
> 
> One of my colleagues encountered this error when updating his working
> copy:
> 
> Error: REPORT request failed on '/svn/P003/!svn/vcc/default'  
> Error: The REPORT request returned invalid XML in the response: XML
> parse error at line   
> Error: 3239: no element found (/svn/P003/!svn/vcc/default)  
> 
> While I have seen this error before, I was under the impression that
> this problem was Solved in the SVN 1.2 version. 
> 
> Our environment:
> 
> TortoiseSVN-1.2.1-svn-1.2.1.msi
> Subversion 1.2.0 (r14790)
> Suse linux
> Apache 2.0.54 + mod_dav_svn
> 
> The apache error log file shows:
> 
> [Fri Aug 26 16:00:55 2005] [error] [client 10..........] Provider
> encountered an error while streaming a REPORT response.  [404, #0] 
> [Fri Aug 26 16:00:55 2005] [error] [client 10..........] A failure
> occurred while driving the update report editor  [404, #160013] 
> [Fri Aug 26 16:00:55 2005] [error] [client 10..........] Working copy
> path 'Client/WinUI/Controls/yyyyyyyyyy.yyyyy' does not exist in
> repository  [404, #160013] 
> [Fri Aug 26 16:02:38 2005] [error] [client 10..........] Provider
> encountered an error while streaming a REPORT response.  [404, #0] 
> [Fri Aug 26 16:02:38 2005] [error] [client 10..........] A failure
> occurred while driving the update report editor  [404, #160013] 
> [Fri Aug 26 16:02:38 2005] [error] [client 10..........] Working copy
> path 'Client/WinUI/Controls/yyyyyyyyyy.yyyyy' does not exist in
> repository  [404, #160013] ...
> 
> Basic workaround is to start again with a checkout in a clean folder.
> 
> Any ideas what can be the cause of this? And what to do to solve it?
> 
> Kind regards,
> 
> Lieven Govaerts
> ICT Processes
> Post.be
> 
> 
> 
> 
> STRICTLY PERSONAL AND CONFIDENTIAL
> This message may contain confidential and proprietary material for the
sole use of the intended recipient. Any review or distribution by others is
strictly prohibited. If you are not the intended recipient please contact
the sender and delete all copies.
> 
> Dit bericht is enkel bestemd voor de aangeduide ontvangers en kan
vertrouwelijke informatie bevatten. Als u niet de ontvanger bent, dan mag u
de inhoud van dit bericht niet bekendmaken noch kopiëren. Als u dit bericht
per vergissing ontvangen heeft, gelieve er de afzender of De Post
onmiddellijk van op de hoogte te brengen en het bericht vervolgens te
verwijderen.
> 
> Ce message est uniquement destiné aux destinataires indiqués et peut
contenir des informations confidentielles. Si vous n'êtes pas le
destinataire, vous ne devez pas révéler le contenu de ce message ou en
prendre copie. Si vous avez reçu ce message par erreur, veuillez en informer
l'expéditeur, ou La Poste immédiatement, avant de le supprimer.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
> 
-- 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.16/83 - Release Date: 26/08/2005
 
-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.16/83 - Release Date: 26/08/2005
 
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org