Unable to Start Subversion on windows 2003 server. StartService FAILED 1053

Question

good peeps of the world, I'm in the process of migrating from VSS to SVN (all these days of futile versioning ...)

anyway i've come to the point of creating the service, i used the following command:

sc create svn_hr binpath= "\"c:\program files\subversion\bin\svnserve.exe\" --service -rd:\SVN\SVN_HR" displayname= "Subversion Server" depend= Tcpip start= auto

This successfully creates the SVN service:

[SC] CreateService SUCCESS

I now try to run the service like so:

sc start SVN_HR

This returns an error for me:

sc start SVN_HR

[SC] StartService FAILED 1053:

The service did not respond to the start or control request in a timely fashion

I did some googling around and have arrived at the conclusion that there's something wrong with my rights permission or the service is not coming up because of some rights issue. Could anyone help me out with this? I'm presuming this is a basic problem faced... ?

I've installed Subversion 1.6.6 on Windows Server 2003 standard edition.

kindly enlighten the noob!

Cheers K

Answer 1

Good peeps...

many thanks for the support.

As Dani, Critical Skill & Yoopergeek have rightly suggested it's an issue with admin privileges. I searched for the svnserve.exe file, right clicked the file -> compatibility and checked the "Allow NonAdministrators to run this program". I deleted and re-created everything and now it's seems to be going through fine.

I doubt this is going to be a major security threat etc..

@Yoopergeek the -rD isn't actually a typo the service gets created correctly, while it's true the argument is -r only the D is from the location of the file i.e D:\SVN\SVN_HR. Apparently the space in between is not mandatory

Answer 2

Are you able to run the command line you're passing to sc?

ie: can you execute: "c:\program files\subversion\bin\svnserve.exe\" --service -rd:\SVN\SVN_HR

I think I'm a couple minor versions behind, but unless you have a typo, "-rd" isn't an option to svnserve. -r and --root are, however.

Answer 3

Check under what ID the service runs, and if that user have all the access it needs to the service files/ repositories.

You can make the service run under system permissions, which will make it maybe too strong but if you are not to deal with security issues, it might help solving the problem.

did you check the eventvwr for errors ?