I've just experienced the same symptoms, although I couldn't get beyond the installer trying to start the service even with the workarounds that Techno79 suggested.
If installing on Windows server 2003, is there a minimum service pack required? What does the output from the msiexec tell you (I can't get back down to our server to run that command again today)? On Jan 8, 2:36 pm, "VisualSVN Support" <[email protected]> wrote: > Hi! > > We're interesting to research this problem. Please could you provide > more detatils? > > What version of the VisualSVN Server do you use? > What version of the Windows do you use? > > >The user account I am running as has full access but I presume the service > >is running under > > local system which does not have full access. > > Yes, you should ensure that VisualSVN Server is running under a > network account with > sufficient privileges to connect to the file server before using the UNC path. > > >When installing VisualSVN Server upon installation I get the error > > "VisualSVN Server services cannot be started...". > > Could you please also execute the following command line "msiexec > /l*log.txt /i VisualSVN-1.6.2.msi" (in command prompt) and send us > the produced log.txt file from the current directory. > > Thank you! > > > > On Fri, Jan 2, 2009 at 5:27 AM, Techno79 <[email protected]> wrote: > > > When installing VisualSVN Server upon installation I get the error > > "VisualSVN Server services cannot be started...". This only happens > > when I set the repositories location to a network drive (both with a > > UNC path and with a mapped drive). Error does not happen if I use a > > local drive. I believe this is because it is not getting the necessary > > privileges for the network location. The network location is on a > > Windows Home Server so it has limited options. The user account I am > > running as has full access but I presume the service is running under > > local system which does not have full access. > > > Anyway, I found a work around: > > When the error message comes up, in the "VisualSVN Server" service is > > already in the services list. While the error message is up, change > > the service to run as the user account that has full access to the > > network share. Once this is done, click Retry on the error message box > > and this allows it to continue successfully. > > > Not sure if there is a better solution to this problem but thought I > > would let people know. > > -- > Olga Dolidze > VisualSVN Support
