Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I was struggling with exactly the same issue. I got my work laptop replaced and suddenly I stopped being able to connect to server. Strangely, initially I was getting errors only blocking me from committing, like: Command : Commit Error : Commit failed (details follow): Error : MKACTIVITY of '/svn/<strong><em>/!svn/act/c511b853-23b4-db4a-8991-0bc689a63353': Error : Could not parse response status line (http://</em>*</strong>.<em>*</em>*.com) Completed! : </p> <p>When I moved to work in another branch (the SVN server was accessible with no issues for everyone on both branches, who has proper security), I started getting error like:</p> <p>Command : Checkout from http://<strong><em>.com/svn/fineos</em></strong>/<em><strong></em>/trunk, revision HEAD, Fully recursive, Externals included Error : Unable to connect to a repository at URL Error : 'http://<em>*</em>*</strong>.com/svn/fineos*<strong>/*<em></strong>/trunk' Error : OPTIONS of Error : 'http://<strong></em>*</strong>.com/svn/fineos*<strong>/*<em></strong>/trunk': could Error : not connect to server (http://<strong></em>*</strong>.com) Completed! : </p> <p>Note: In each case, I could access repository through browser and it was working for everyone else, so obviously it wasn't network or repository issue. </p> <p>This what worked for me was to uninstall Tortoise client, then remove Tortoise cache folder from Local and Roaming folders under C:\Users\<i>user</i>\AppData. Additionally I renamed TortoiseSVN node in Windows registry so the old configuration cannot be found. Then after reinstallation, client connected to repo beautifully. I am not sure if both steps are required, maybe just changing registry will be enough, I will leave that to you to confirm. </p> <p>Apologies for long response, but as I haven't seen response to this problem after googling for longer while, I thought that may be helpful for different cases. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload