0

I setup the basic Win32 CollabNet SVN Server 1.6.5-6 with all the default settings and Apache running on port 9999 . Also, I installed TortoiseSVN . Everything works fine with Tortoise and also with Eclipse as long as I use a FILE url such as: file:///C:/SVNRepository/ .

If I point Internet Exploder at http://localhost:9999 it gives me a http text message that says "It works!". When I try to connect with the url http://localhost:9999/svn the browser shows me the 4 root directories of C:\SVNRepository but they are not browseable directories. Pointing the browser to svn://localhost:9999/svn causes the browser to open Tortoise, which in turn locks up explorer.exe for 5 minutes until it times out.

What is wrong?

After deliberations, the answer turned out to be:

<Location /svn>
  DAV svn
  #SVNParentPath C:/NotUsed
  SVNPath "C:/SVNRepository"
  SVNListParentPath On
  #Require valid-user
  #AuthType Digest
  AuthName "SVNRepository"
  #AuthUserFile "C:/Subversion Server/httpd/conf/svnauthfile"
</Location>
Improve this question
6
  • Hi Did you get the svnserve.exe running as in an answer below? It will be nice if you can record what you did to resolve this issue - thanks a bunch. :-) Commented Oct 19, 2009 at 3:34
  • I haven't yet resolved this. The local SVN stuff works great. When I try to connect to my SVN from a remote machine using Tortoise and the url svn://mymachine:9999/CodeRoot it just times out and locks up my explorer.exe for about 2 minutes. If I get the url slightly wrong, such as with the wrong port number, it instantly says "cant connect". So, this proves that Tortoise sees "something" that it recognizes but cant negotiate with. Commented Oct 19, 2009 at 15:04
  • Which windows version are you using? Commented Oct 19, 2009 at 16:37
  • this was windows XP SP3. Commented Oct 30, 2009 at 1:19
  • @djanjofan: You asked a moderator question about the "-50" on this; this was the cost of the bounty (50) that you placed. The system adds a free 50, making the total bounty 100, at cost of 50 to yourself. Commented Oct 31, 2009 at 8:33

5 Answers 5

Reset to default
1
+100

That you get a not found error when trying to open the repository in a web browser suggests that the url is wrong. From reading the readme for opencollab svn server it seems that the recommended url-prefix for repositories is /svn, so if you followed those recommendations your "CodeRoot" would be http://localhost:9999/svn/CodeRoot.

You should be able to confirm if that is the case by looking at the httpd.conf of apache, at the bottom of the file you should find something like

<Location /_url prefix here_>
   DAV svn
   #SVNParentPath C:\repositories
   SVNPath C:\repositories
</Location>

If you have only one repository and want to be able to access it through localhost/svn you should use SVNPath instead of SVNParentPath and point it to the full path of the repository. If you instead want multiple repositories to be available under /svn use SVNParentPath instead and point it at the directory containing all the svn repositories.

Improve this answer
Sign up to request clarification or add additional context in comments.

4 Comments

Ok, you were right about one thing. I had the SVNParentPath configured incorrectly and also without quotes around it. I updated my original bug description. Thanks for the help but I am still not getting it to work.
It sounds like you should be using SVNPath instead of SVNParentPath in your configuration.
For a guy who had only 21 points before this answer, you kicked ass helping me out. Thanks. :-)
you should edit your answer to reflect the correct answer. that means changing SVNParentPath to SVNPath and also comment out AuthUserFile, AuthType, and Require .
1

If you're trying to access your SVN repository via an Apache server, you should be using the URL specifying the http protocol: http://localhost:9999/something. The svn protocol is for use with the standalone svn server. The something part will depend on how Apache is configured (whatever Apache is expecting to map to the directory C:\SVNRepository).

Improve this answer

1 Comment

i tried that. that was the obvious thing to try, which is why i started thinking svn:// was the correct way to go.
1

subversion URLs starting with svn:// use subversions own protocol that is handled by svnserve. If you are using apache you're using the mod_dav_svn module for apache if configured correctly. When using apache for serving an svn repository you can also access the repository via any browser -- just type the URL in the browser and you'll see a rather simple representation of the file list. This is a really useful way to see if the repository is actually served. All URLs served via apache use the http protocol or its SSL variant https. As with any webserver, if you're using a non-standard port you need to specify it with the URL.

Improve this answer

Comments

0

I've never used SVN with apache but shouldn't it be

http://localhost:9999

If accessing it through apache? I could see specifying the svn protocol might confuse tortoise when it tries to connect.

Also trying "telnet localhost 9999" to test the port is listening.

HTH.

Improve this answer

2 Comments

yes, netstat shows the port is listening. also, the url localhost:9999 shows the message "it's working" in the web browser.
the svn:// url didn't confuse explorer.exe . what happens is that it uses the file association in the system to open TortoiseSVN with that same url. Tortoise locks up though and cant open the url anyway (see my original description).
0

Thats hard to tell, but most obviously there is something wrong with the apache configuration. For more precise answers you should post your concrete setup steps.

But besides installing all on your own, you should take a look on VisulaSVN Server. This is quite handy in a Windows environment (which you seem to work with). Its a complete SVN server and easy to configure via a simple GUI.

Improve this answer

1 Comment

i did the standard apache install that comes with the installer and i accepted all defaults except i used port 9999 instead of 80.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.