We were using 1.5.5 which we installed on our Windows Server 2003 system back in September. The 1.6.2 install failed because it could not start the Apache server. A power outage (which I hadn't thought was related at the time) had abnormally terminated Apache, and it could not be returned to a normal state via restart nor could the VisualSVN service restart the Apache server. Restarting the VisualSVN service would return an error message which said that the service could not be started because the name was not the same as the one listed and an Event Log message indicating that Apache failed to start because it was already running (when the VisualSVN/Apache service was listed as "Stopped").
Uninstalling VisualSVN, restarting, and then installing VisualSVN 1.6.2 resolved the problem. Pointing 1.6.2 to the previous repositories worked without any trouble so we did not lose any code. I hope this helps if someone else has this problem. On Nov 28 2008, 12:18 pm, "VisualSVN Support" <[email protected]> wrote: > Hello! > Thank you for using VisualSVN Server! > > Please upgrade to VisualSVN Server 1.6.2 > fromhttp://www.visualsvn.com/server/download/. > > Upgrading from older versions of VisualSVN Server is easy as usual. > Run the installation of the new version and just click "Next" several > times. Uninstalling of the older version is not recommended - the > server parameters customization (such as port number etc.) will be > lost in that case. > > You could also read Release Notes at VisualSVN Server > ChangeList:http://www.visualsvn.com/server/changes/#v1.6.2. > > Please could you provide more details on the problem? > > We need to know additional information about your configuration: > - what version of the Windows do you use? > - what particular kinds of projects do you use? > - what Windows Service Pack do you have? > > Could you please send us VisualSVN Server logs? > VisualSVN Server writes log to the Windows Event Log. You could find > VisualSVN Server logs in the Application category in the Event Viewer. > Please pay attention that earlier versions of VisualSVN Server (before > 1.6) write log to file C:\Repositories\server.log. > > Thank you! > > > > On Tue, Nov 25, 2008 at 6:26 PM, <[email protected]> wrote: > > > We've been running Visual SVN Server 1.5.3 for a while now without any > > troubles, but this morning the service failed to start. Attempts to > > start the service have resulted in an error message. The accompanying > > application event says: > > > "A service process other than the one launched by the Service Control > > Manager connected when starting the Visual SVN Server service. The > > Service Control Manager launched process #### and process #### > > connected instead. > > > Note that if this service is configured to start under a debugger, the > > behavior is expected." > > > The process numbers are different each time, so I have opted to use #. > > > I saw in this group this issue was fixed long ago by updating 1.0.1 to > > 1.0.3. Is there a similar solution here? > > > Also, this server has no connection to the internet. Does running the > > downloaded install update, or will it try to uninstall the current > > version? > > > Thanks. > > -- > Olga Dolidze > VisualSVN Support
