On Wed, Jan 12, 2022 at 10:45 AM Gavli, Gangaram <gga...@horizonglobal.com> wrote:
> Thank you. > > > > We tried upgrading Client to 1.14 but still same issue. > The issue you are experiencing appears to be server side. There are, of course, many variables involved in any client/server software, and so it is possible that the issue could be caused by any number of other components. A google search for the error message brings up this Stack Overflow question as the first result: https://stackoverflow.com/questions/22965847/svn-error-running-context-an-existing-connection-was-forcibly-closed-by-the-rem If you look through those answers, there doesn't seem to be a common theme as to the cause or fix. The bottom line is that we can't say with certainty what is causing this issue, but we do know that the 1.6 version running on your server is quite old and many, many bugs have been fixed, not to mention security issues, in subsequent releases, and I doubt if anyone could offer any meaningful help for such an old version. Therefore, it might be that the best path forward is to consider upgrading the server to Subversion 1.14.1. That might fix the problem, but whether it does or not, it will eliminate old already-fixed bugs and security issues. It does not escape me that upgrading the server could be a non-trivial undertaking. You might, for example, consider setting up an entirely new server in parallel and making a clean switchover to minimize service interruption. Hope this helps, Nathan
