I removed all possible NAT problems by running the SVN client on the same box as the SVN server, but the problem didn’t go away.
#Smartsvn out of memory update#
A failure occurred while driving the update report editor Provider encountered an error while streaming a REPORT response. ```asciidocErrorLog c:/errorlogs/visualsvn_apache.logLogLevel warn
I figured I'd dig deeper, so I turned on errors in apache by adding the following to c:\program files\visualsvn server\conf\nf and restarting VisualSVN: (I had to create the c:\errorlogs folder to get this to work) What in the world is a chunking error? I tried Google, but all that turned up there was a (). I set up VisualSVN to listen on both ports 443 (with SSL) and 80 (without SSL) by adding the following to c:\program files\visualsvn server\conf\nf and then restarting VisualSVN server:īut I still saw chunking errors like this: It mentioned a ‘secure connection’, and so I figured that SSL could be an issue. I had been using this for a short while, and I soon saw this error when trying to scan for changes:Ĭould not read chunk Size: secure connection truncated We have purchased licenses for RedGate’s SQL Source Control, which allows you to use SQL Manager to check in SQL objects into a SVN repository. I use Visual SVN for the server and Smart SVN for the client, but there are lots of other great options out there. (If all you want to do is solve the same problem, you only need to add a Timeout 1800 line to your c:\program files\visualsvn server\conf\nf file and restart Visual SVN server - you can, of course, adjust the number of seconds as you like)įirst off, if you are doing any kind of software development and you aren’t using source control of some kind, you are missing out big time.