|
I am trying to start Synergy as a service on my windows XP machine. I have got the sinergy service installed and it shows up in the services list in windows. However, when it starts, there is no connectivity with the client. The Synergy GUI works fine when I run as a server, so I suspect that the reason it won't work when I start the service is because it can't read a config file. I attempt to use the "Start parameters" field on the service properties dialog to specify the config file with the -c or --config command line options, but when I attempt to start the service, I get the error: "Windows could not start the synergy server on local computer...." (See image - does not appear, but if you copy the url you can view in browser...).
|
Can anyone help? I've tried all sorts variations of the string in the Start Parameters box - it seems that if I input any string in here, I get the error when trying to start the service.
****************** ***** NOTICE ***** ****************** *** *** This solution involves editing the registry. *** Don't try it unless you are comfortable doing so. *** Create a config file, either manually or using the GUI, and save it as C:\Program Files\Synergy\default.sgcOpen registry editor, and browse to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Synergy Server\Parameters Edit the CommandLine value Change --relaunch to --restart Replace the pathfilename that is after the -c parameter to C:\PROGRA~1\Synergy\default.sgcClose the registry editor, and restart your PC. If I have answered you question, please be sure to accept my answer.
(13 Jun '11, 17:31)
willichan ♦
Thanks Willichan, That got Synergy running as a service. However, when I attempt to run Synergy as a different user (an administrator user) the synergy service starts, but it does not allow me to control my client computer (another win XP machine running sinergy GUI). From services list, I opened the "Synergy Server" item, and in the "Log On" tab changed to user to a local administrator account - provided the right password and restarted. The client machine "sees" the server because when the service starts on the server machine, the client's Synergy tray icon changes to the symbol with the lightning bolt (indicating some sort of connection) however - the mouse is trapped on the server machine. When I stop the service on the server machine, the client's synergy tray icon changes to the one without the lightning bolt (no connection). The reason I'm trying to run service as administrator user instead of normal 'Local System' is because I read somewhere that synergy is given greater priority over other services if it's started as admin user - is this so? Cheers,
(14 Jun '11, 21:36)
Max_Power
You will probably want to set it to run as Local System account with Allow service to interact with desktop checked. If that does not resolve it, post a new question, and we can tackle that issue.
(15 Jun '11, 11:09)
willichan ♦
This Q&A was a godsend... Spent several hours this afternoon trying to figure out why the Synergy server would not start as a service on my WinXP machine when the same config file was working perfectly when started through the GUI. Looking at the Parameters item in the registry, it looks like the GUI, upon "install", is writing the pathname to the config file with forward slashes instead of backslashes ("/", rather than "") and so the config file was not being found when the server started up. Fixed the registry item, now everything is working fine. I am running 1.4.3, and am surprised that nobody has come across this problem before.
(06 Sep '11, 20:15)
rmw
Wow, RMW was right! This was a godsend. I am running 1.4.5 and it still has the same bug. The GUI tool is writing the service to the registry with forward slashes. Willchan was also right, I needed to also change the "D:Program Files" section of Parameters to say "D:Progra~1", AS WELL AS changing --relaunch to --restart. Now it connects immediately! I hope someone from the development team sees this and can fix it.
(09 Nov '11, 12:27)
Syclone0044
|
Check the log for errors.
The same bug still exists in 1.4.7