I get the following error when trying to access the repository (svn://svn.lhotka.net/csla/):
Can't connect to host 'svn.lhotka.net': No connection could be made because the target machine actively refused it.
I'm able to use the web interface to access, so it seems to be relevant for remote clients only.
Does someone else experience the same problem?
Thanks!
I have just tried the address given using Tortoise SVN and have been allowed access with no problems. Maybe it is worth trying again?
Regards,
Patrick
Hey guys. What was the resolution to this issue. I've just installed Tortoise SVN and am experiencing the exact same error.
TIA,
Will
The best thing to try to start is to try the 'repro browser' option and see if you can browse the repository.
In your other post it appeared you might be trying the 'import' option - and since the repository is read-only for you, you can't import your folders into the repository.
You need to use check out or export options to get data from the repository.
Nope, sorry, forgot to mention that I tried that also and got the same error.
Thanks,
Will
I am able to access the repository
You are using this uri: svn://svn.lhotka.net/csla
In the repro-browser, and it fails to connect?
From: wjcomeaux
[mailto:cslanet@lhotka.net]
Sent: Tuesday, June 23, 2009 10:50 AM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] SVN repository error using TortoiseSVN
Nope, sorry, forgot to mention that I tried that also and got the same
error.
Thanks,
Will
And that did the trick. Wrong uri.
Thanks Rocky.
I should also point out that I have frequently encountered
organizations that have a firewall blocking the svn port. I don’t know
why, but it does happen from time to time. You should make sure your local
firewall, and your organization’s firewall aren’t interfering with
the svn port.
Rocky
From: Rockford Lhotka [mailto:cslanet@lhotka.net]
Sent: Tuesday, June 23, 2009 11:12 AM
To: rocky@lhotka.net
Subject: RE: [CSLA .NET] SVN repository error using TortoiseSVN
I am able to access the repository
You are using this uri: svn://svn.lhotka.net/csla
In the repro-browser, and it fails to connect?
From: wjcomeaux
[mailto:cslanet@lhotka.net]
Sent: Tuesday, June 23, 2009 10:50 AM
To: rocky@lhotka.net
Subject: Re: [CSLA .NET] SVN repository error using TortoiseSVN
Nope, sorry, forgot to mention that I tried that also and got the same
error.
Thanks,
Will
I should also point out that I have frequently encountered organizations that have a firewall blocking the svn port. I don’t know why, but it does happen from time to time. You should make sure your local firewall, and your organization’s firewall aren’t interfering with the svn port.
Port 3690 needs to be opened for SVN. I needed to open that up on the corporate internet router.
Use cmd.exe netstat to review the communication from your PC.
The TCP port from your PC might be from 0-65,534 to the 67.152.152.109:3690 port at the CSLA svn repository.
Is there a way to get the source without svn? I can't get to the repository with TortoiseHG so I'm guessing that the port is blocked in the corporate firewall and no way I'm getting that changed. I can browse the repository with the web view link but that only gives me access to one file at a time.
You can download released source via the download page (http://www.lhotka.net/cslanet/download.aspx).
The only way to get the current work-in-progress source is via svn, because the repository runs Subversion.
I've been able to get TortoiseHG to connect to the CSLA SVN repository via the SVN firewall port. I did have some troubles with different HG plugins (see - https://bitbucket.org/durin42/hgsubversion/issue/365/subversionconnectionexception-on-public) however it took me a few attempts to clone the svn repository with TortoiseHG to my desktop in Australia. It seemed to get stuck on some of the sql database files (*.mdf; * .trn) that were checked in, but it worked in the end. I did this prior to going on holiday, 2 weeks ago, so I haven't got back into the office to see how that history works within HG.
From memory I loaded the latest build of hg and use the command line to complete the task.
Now I've got the core changes in to a local HG repository, I'll be just doing local copy, as part of the testing I'm doing for a CI server (see http://www.finalbuilder.com/forums/ContinuaCI/).
Copyright (c) Marimer LLC