MadCap Software Forums

I love when this happens. An error message where the description is "there was no error".

I've been struggling with getting SVN to work, partially because I'm using VisualSVN server on a virtual machine. It kinda worked for one project, then the other one just doesn't want to go on there.

The message I get after entering the server (https://servername/svn/RepositoryName/) is the following:

Could not connect to server:
https://servername/svn/RepositoryName/
'https://servername/svn/RepositoryName/': 200 OK (http://servername)

I say "servername" but this is actually local: it's on the same machine as Flare. when I did it from another machine, it actually just created the folder and Flare just froze there and never uploaded a single file to the SVN server.

Ooops! Hahaha that was my fault! I had a second Apache server running on the same machine and it started before the SVN one. My bad!

Same issue here, same error. Just updated to v7.01 on Tuesday morning, but hadn't tried this feature until then so I don't know if it's a result of the .01 update or not.

Have contacted Dev here (they manage the SVN server) but they don't know what the problem could be. I was able to successfully create a folder based on my project structure on my local drive but cannot upload anything. I'm sure it's just a settings issue in Flare, but don't know how to fix it. Have followed steps in your online help.

Any thoughts? Thanks.

P.S. Attended Flare RoadShow in Toronto on Monday, it was terrific. Recommend to everyone!

Andrew,

As my first reply mentions, I had another web server running on that same machine at the time which was using the port instead of the real SVN server.

Just make sure you're not running Apache, IIS or anything else. Also, try to access https://subversion/ with your browser and see what page it is, that may clue you in (if you see "Welcome to IIS7" for example, that's a clue!)

Cheers!

Eric Lachance wrote:As my first reply mentions, I had another web server running on that same machine at the time which was using the port instead of the real SVN server.

Just make sure you're not running Apache, IIS or anything else. Also, try to access https://subversion/ with your browser and see what page it is, that may clue you in (if you see "Welcome to IIS7" for example, that's a clue!)

Thanks Eric. Negative on the first question and I get a 403: Access forbidden error on the second suggestion. The actual URL is https://subversion/svn/[i]<Name_of_Repository>[/i]/Projects/Help. I can access that URL in the browser and create a new folder but cannot upload through Flare.

In that case, I'm out of ideas. I'm not a subversion professional so beyond plug & play, I'm lost. I would open a support ticket if I were you.

Eric Lachance wrote:In that case, I'm out of ideas. I'm not a subversion professional so beyond plug & play, I'm lost. I would open a support ticket if I were you.

Thanks for trying, much appreciated. Have already opened a ticket via the web. I'll post back here if I find out what the story is so others can benefit as well. Cheers.

I've got exact the same problem. I'm using apache svnserver 1.6.12 When I try to connect to http://svnserver/reposname, the following error occured in flare 7.0.1:
Could not connect to server:
http://svnserver/
'http://svnserver': 200 OK (http://svnserver)

With a browser I can connect to the server with login credentials. Anyone a idea to fix this?

Eric Lachance wrote:Andrew,

As my first reply mentions, I had another web server running on that same machine at the time which was using the port instead of the real SVN server.

Just make sure you're not running Apache, IIS or anything else. Also, try to access https://subversion/ with your browser and see what page it is, that may clue you in (if you see "Welcome to IIS7" for example, that's a clue!)

Cheers!

The page that is displayed when entering https://subversion/ into my browser states: "Welcome to Visual SVN Server!". Just checked with Dev and they are running Apache only but this whole thing is becoming moot, apparently, since we're soon switching to GIT very soon, and SVN will become read-only. Oh well.