Cannot connect to a SVN repository using Tortoise SVN?

Subversion Edge will not be able to start the Apache server if there is another application using that port. You will also see an error on the top of the console that it could not bind to the port On the Administration tab of Subversion Edge you will see "Server Logs". Look at the logs named "access_YYYY_MM_DD.

Log". These are the Apache access logs. If the client request is reaching the Apache server it will be logged here Other than that, I would say you need to share the error message the user receives.

I would also try a few things like intentionally misspelling the hostname and changing to a port number that is not used so you can see how the error message changes (or does not change) as you introduce those options For example (this is with latest 1.7 release candidate and messages are a little different): $ svn ls foo/svn/repos svn: E175002: OPTIONS of 'foo/svn/repos': Could not resolve hostname `foo': Host not found (http://foo) $ svn ls http://cu171.cloud.sp.collab.net:8888/svn/repos svn: E175002: Unable to connect to a repository at URL 'http://cu171.cloud.sp.collab.net:8888/svn/repos svn: E175002: OPTIONS of 'http://cu171.cloud.sp.collab.net:8888/svn/repos': could not connect to server (http://cu171.cloud.sp.collab.net:8888).

Subversion Edge will not be able to start the Apache server if there is another application using that port. You will also see an error on the top of the console that it could not bind to the port. On the Administration tab of Subversion Edge you will see "Server Logs".

Look at the logs named "access_YYYY_MM_DD. Log". These are the Apache access logs.

If the client request is reaching the Apache server it will be logged here. Other than that, I would say you need to share the error message the user receives. I would also try a few things like intentionally misspelling the hostname and changing to a port number that is not used so you can see how the error message changes (or does not change) as you introduce those options.

For example (this is with latest 1.7 release candidate and messages are a little different): $ svn ls foo/svn/repos svn: E175002: OPTIONS of 'foo/svn/repos': Could not resolve hostname `foo': Host not found (http://foo) $ svn ls http://cu171.cloud.sp.collab.net:8888/svn/repos svn: E175002: Unable to connect to a repository at URL 'http://cu171.cloud.sp.collab.net:8888/svn/repos' svn: E175002: OPTIONS of 'http://cu171.cloud.sp.collab.net:8888/svn/repos': could not connect to server (http://cu171.cloud.sp.collab.net:8888).

I checked the access logs and see 408 HTTP errors from the workstation IP address that is having issues – Michael Kniskern Sep 20 at 23:03.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.