Hello Marc, On Mon, Jul 24, 2017 at 11:58 PM, <panthe...@gmail.com> wrote:
> Hello, > > We recently implemented a new network topology using some VLANs to segment > our network traffic and we just noticed that for some of our users, they > are unable to switch branches or do a full checkout of some of our larger > repositories. When they attempt to do so the process runs, but you see the > throughput of the checkout go up and down (like usual), but then eventually > it drops to zero, starts up, drops to zero and then throws the error (as > shown in the subject, REPORT request on '/svn/<RepoName>/!svn/me' failed. > It is the exact same error very single time. This also occurs on another > workstation we have tested with. > > I already upgraded the Visual SVN to the latest version and had my users > download the version of Tortise that matched SVN (1.9.5) to see if that > would help. I've attempted to change the http-timeout up to 6000 and > enabled the http-compression as well, all to no avail. > Revert these configuration changes, please. > The event logs show as follow every time in this order: > > Provider encountered an error while streaming a REPORT response. [500, #0] > [client x.x.x.117] > > A failure occurred while driving the update report editor [500, #106] > [client x.x.x.117] > > Unknown error [500, #106] > [client x.x.x.117] > > Prior to the upgrade to 3.6.1, the errors were: > > Provider encountered an error while streaming a REPORT response. [500, #0] > [client x.x.x.117] > > A failure occurred while driving the update report editor [500, #106] > [client x.x.x.117] > > Error writing base64 data: Unknown error [500, #106] > [client x.x.x.117] > > The only thing remotely similar that I could find was this thread -> > https://groups.google.com/d/topic/visualsvn/7TtIeTLYAyI/discussion > > NOTE: we are engaging our network team to troubleshoot as well, however > what's more strange is from my workstation, I can download at very high > speeds without any errors/problems and never encounter that error message > at all. > > If there are any further suggestions or ideas, please let me know. We > would like to ensure our users can properly switch and checkout without > getting this strange /!svn/me error. > You should focus on checking the network and antivirus. Something between the server and SVN clients makes the connection drop. According to these log events, the client SVN client drops the connection while in middle of operation (e.g. when you press Ctrl-C while `svn checkout` is in progress). Any intermediate service that's working between SVN client and the server could also break the connection and you will see these errors on the log, too. -- With best regards, Pavel Lyalyakin VisualSVN Team -- You received this message because you are subscribed to the Google Groups "VisualSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to visualsvn+unsubscr...@googlegroups.com. To post to this group, send email to visualsvn@googlegroups.com. Visit this group at https://groups.google.com/group/visualsvn. For more options, visit https://groups.google.com/d/optout.
