> -Ursprüngliche Nachricht-
> Von: Mark Phippard [mailto:markp...@gmail.com]
> Gesendet: Freitag, 8. Februar 2013 18:34
> An: Michael Zender
> Cc: users@subversion.apache.org
> Betreff: Re: Could not read chunk size: connection was closed by
> server on Windows 7
>
On Fri, Feb 8, 2013 at 10:28 AM, Michael Zender
wrote:
> I finally solved my problem and wanted to share my solution with you.
Thanks for letting us know.
> It turned out, that Kaspersky Endpoint Security 8 and its Web-Anti-Virus
> feature in particular were causing this problem to show up. We
> -Ursprüngliche Nachricht-
> Von: Michael Zender [mailto:michael.zen...@mos-tangram.com]
> Gesendet: Donnerstag, 7. Februar 2013 17:34
> An: users@subversion.apache.org
> Betreff: AW: Could not read chunk size: connection was closed by
> server on Windows 7
>
-Ursprüngliche Nachricht-
Von: Mark Phippard [mailto:markp...@gmail.com]
Gesendet: Donnerstag, 7. Februar 2013 15:26
An: Michael Zender
Cc: users@subversion.apache.org
Betreff: Re: Could not read chunk size: connection was closed by server on
Windows 7
Sorry for top posting, but see
OPFIND of '//!svn/bc//': Could not read
> chunk size: connection was closed by server (http://)
>
> svn co http:////
> svn: REPORT of '//!svn/vcc/default': Could not read chunk size:
> connection was closed by server (http://)
> An interesting fact about the
on was closed by server (http://)
svn co http:
svn: REPORT of '//!svn/vcc/default': Could not read chunk size:
connection was closed by server (http://)
An interesting fact about the checkout is, that the working copy has
been created and so far I've had no problem with it.
I s
On Wed, Nov 23, 2011 at 11:46 AM, Justin Johnson
wrote:
>>
>>> during a checkout.
>>>
>>> Could not read chunk size: connection was closed by server
>>>
>>> In the server logs the following errors appear around the same time.
>>>
>
>> during a checkout.
>>
>> Could not read chunk size: connection was closed by server
>>
>> In the server logs the following errors appear around the same time.
>>
>> Provider encountered an error while streaming a REPORT response. [500, #0]
>
Justin Johnson writes:
> during a checkout.
>
> Could not read chunk size: connection was closed by server
>
> In the server logs the following errors appear around the same time.
>
> Provider encountered an error while streaming a REPORT response. [500, #0]
>
; been getting the following error every once in a while, typically
> during a checkout.
>
> Could not read chunk size: connection was closed by server
>
> In the server logs the following errors appear around the same time.
>
> Provider encountered an error while streaming a R
.
Could not read chunk size: connection was closed by server
In the server logs the following errors appear around the same time.
Provider encountered an error while streaming a REPORT response. [500, #0]
A failure occurred while driving the update report editor [500, #130]
Error writing
11 matches
Mail list logo
