Jump to content

Hello! ūüĎč

Our forums have moved to: discourse.symless.com

These forums are now archived (read only).

Upgrade to 1.10.3 has broken my installation


Recommended Posts

People may want to be wary. This upgrade has broken my installation. Uninstalled & reinstalled, rebooted router, reset configuration, still no luck. I'll report back if downgrading is successful.

  • Server: Windows 10 (Wired LAN)
  • Client: Windows 10 (Wired LAN)

Working before the upgrade. Any troubleshooting suggestions? Tried a fresh install.

 

Client logs:

 

[2019-09-04T08:35:10] DEBUG1: logging to file (C:/Users/[removed]/synergy.log) enabled
[2019-09-04T08:35:10] DEBUG1: starting client
[2019-09-04T08:35:10] DEBUG1: thread 0x00003e68 entry
[2019-09-04T08:35:10] DEBUG: screen shape: 0,-479 4480x1559 (multi-monitor)
[2019-09-04T08:35:10] DEBUG: window is 0x0006091e
[2019-09-04T08:35:10] ERROR: failed to get desktop path, no drop target available, error=2
[2019-09-04T08:35:10] DEBUG: adopting new buffer
[2019-09-04T08:35:10] DEBUG: opened display
[2019-09-04T08:35:10] DEBUG1: registered event type IScreenEvents::error as 4
[2019-09-04T08:35:10] DEBUG1: registered event type IScreenEvents::suspend as 5
[2019-09-04T08:35:10] DEBUG1: registered event type IScreenEvents::resume as 6
[2019-09-04T08:35:10] DEBUG1: registered event type FileEvents::fileChunkSending as 7
[2019-09-04T08:35:10] DEBUG1: registered event type FileEvents::fileRecieveCompleted as 8
[2019-09-04T08:35:10] DEBUG1: registered event type ClientEvents::connected as 9
[2019-09-04T08:35:10] DEBUG1: registered event type ClientEvents::connectionFailed as 10
[2019-09-04T08:35:10] DEBUG1: registered event type ClientEvents::disconnected as 11
[2019-09-04T08:35:10] NOTE: started client
[2019-09-04T08:35:10] NOTE: connecting to '192.168.0.2': 192.168.0.2:24800
[2019-09-04T08:35:10] DEBUG: Opening new socket: 89647120
[2019-09-04T08:35:10] DEBUG: openssl version: OpenSSL 1.1.1c  28 May 2019
[2019-09-04T08:35:10] DEBUG1: openssl flags: compiler: cl /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM
[2019-09-04T08:35:10] DEBUG1: openssl built on: built on: Wed Jul  3 17:04:41 2019 UTC
[2019-09-04T08:35:10] DEBUG1: openssl platform: platform: VC-WIN64A
[2019-09-04T08:35:10] DEBUG1: openssl dir: OPENSSLDIR: "C:\Program Files\Common Files\SSL"
[2019-09-04T08:35:10] DEBUG1: connecting to server
[2019-09-04T08:35:10] DEBUG1: registered event type IDataSocketEvents::secureConnected as 12
[2019-09-04T08:35:10] DEBUG1: registered event type IDataSocketEvents::connectionFailed as 13
[2019-09-04T08:35:10] DEBUG1: registered event type IDataSocketEvents::connected as 14
[2019-09-04T08:35:10] DEBUG: Opening new socket: 8B6BA8B0
[2019-09-04T08:35:10] DEBUG1: registered event type IStreamEvents::inputReady as 15
[2019-09-04T08:35:10] DEBUG1: registered event type IpcServerProxyEvents::messageReceived as 16
[2019-09-04T08:35:10] DEBUG1: registered event type IpcClientEvents::messageReceived as 17
[2019-09-04T08:35:10] DEBUG: event queue is ready
[2019-09-04T08:35:10] DEBUG1: registered event type IpcClientEvents::connected as 18
[2019-09-04T08:35:10] DEBUG1: registered event type IStreamEvents::outputFlushed as 19
[2019-09-04T08:35:25] DEBUG1: registered event type IStreamEvents::outputError as 20
[2019-09-04T08:35:25] DEBUG1: registered event type IStreamEvents::inputShutdown as 21
[2019-09-04T08:35:25] DEBUG1: registered event type IStreamEvents::outputShutdown as 22
[2019-09-04T08:35:25] DEBUG1: registered event type ISocketEvents::disconnected as 23
[2019-09-04T08:35:25] DEBUG1: registered event type ISocketEvents::stopRetry as 24
[2019-09-04T08:35:25] DEBUG: Closing socket: 89647120
[2019-09-04T08:35:25] DEBUG1: connection timed out
[2019-09-04T08:35:25] WARNING: failed to connect to server: Timed out
[2019-09-04T08:35:25] DEBUG: retry in 1 seconds
[2019-09-04T08:35:26] NOTE: connecting to '192.168.0.2': 192.168.0.2:24800
[2019-09-04T08:35:26] DEBUG: Opening new socket: 8B6BA550
[2019-09-04T08:35:26] DEBUG: openssl version: OpenSSL 1.1.1c  28 May 2019
[2019-09-04T08:35:26] DEBUG1: openssl flags: compiler: cl /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM
[2019-09-04T08:35:26] DEBUG1: openssl built on: built on: Wed Jul  3 17:04:41 2019 UTC
[2019-09-04T08:35:26] DEBUG1: openssl platform: platform: VC-WIN64A
[2019-09-04T08:35:26] DEBUG1: openssl dir: OPENSSLDIR: "C:\Program Files\Common Files\SSL"
[2019-09-04T08:35:26] DEBUG1: connecting to server
[2019-09-04T08:35:41] DEBUG: Closing socket: 8B6BA550
[2019-09-04T08:35:41] DEBUG1: connection timed out
[2019-09-04T08:35:41] WARNING: failed to connect to server: Timed out
[2019-09-04T08:35:41] DEBUG: retry in 1 seconds
[2019-09-04T08:35:42] NOTE: connecting to '192.168.0.2': 192.168.0.2:24800
[2019-09-04T08:35:42] DEBUG: Opening new socket: 8B6B98F0
[2019-09-04T08:35:42] DEBUG: openssl version: OpenSSL 1.1.1c  28 May 2019
[2019-09-04T08:35:42] DEBUG1: openssl flags: compiler: cl /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM
[2019-09-04T08:35:42] DEBUG1: openssl built on: built on: Wed Jul  3 17:04:41 2019 UTC
[2019-09-04T08:35:42] DEBUG1: openssl platform: platform: VC-WIN64A
[2019-09-04T08:35:42] DEBUG1: openssl dir: OPENSSLDIR: "C:\Program Files\Common Files\SSL"
[2019-09-04T08:35:42] DEBUG1: connecting to server
[2019-09-04T08:35:57] DEBUG: Closing socket: 8B6B98F0
[2019-09-04T08:35:57] DEBUG1: connection timed out
[2019-09-04T08:35:57] WARNING: failed to connect to server: Timed out
[2019-09-04T08:35:57] DEBUG: retry in 1 seconds
[2019-09-04T08:35:58] NOTE: connecting to '192.168.0.2': 192.168.0.2:24800
[2019-09-04T08:35:58] DEBUG: Opening new socket: 8B6BB150
[2019-09-04T08:35:58] DEBUG: openssl version: OpenSSL 1.1.1c  28 May 2019
[2019-09-04T08:35:58] DEBUG1: openssl flags: compiler: cl /Zi /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM
[2019-09-04T08:35:58] DEBUG1: openssl built on: built on: Wed Jul  3 17:04:41 2019 UTC
[2019-09-04T08:35:58] DEBUG1: openssl platform: platform: VC-WIN64A
[2019-09-04T08:35:58] DEBUG1: openssl dir: OPENSSLDIR: "C:\Program Files\Common Files\SSL"
[2019-09-04T08:35:58] DEBUG1: connecting to server
[2019-09-04T08:35:59] DEBUG: start ipc handle data
[2019-09-04T08:35:59] DEBUG: ipc read: ISDN
[2019-09-04T08:35:59] DEBUG: finished ipc handle data
[2019-09-04T08:35:59] INFO: got ipc shutdown message
[2019-09-04T08:35:59] DEBUG1: stopping client
[2019-09-04T08:35:59] DEBUG: Closing socket: 8B6BB150
[2019-09-04T08:35:59] DEBUG: adopting new buffer
[2019-09-04T08:35:59] DEBUG: closed display
[2019-09-04T08:35:59] NOTE: stopped client
[2019-09-04T08:35:59] DEBUG: ipc disconnect, closing stream
[2019-09-04T08:35:59] DEBUG: Closing socket: 8B6BA8B0
[2019-09-04T08:35:59] DEBUG: Closing socket: 00000000
[2019-09-04T08:35:59] DEBUG1: caught cancel on thread 0x00003e68
Link to post
Share on other sites
Jamie Newbon

Could you also send the server log as well, the client log on shows a time out which is either a firewall issue or the server is not listening for connections

Link to post
Share on other sites

Just an FYI, 1.10.3 is working fine in my environment, Windows 10 Mac OS both most recent versions. The only oddity was after the install / reboot (on Windows as my server) I had to stop the service and restart it once before my Mac client would connect. If that continues to happen (I reboot every night) I'll save some logs and post them.

Link to post
Share on other sites
11 minutes ago, Jamie Newbon said:

Could you also send the server log as well, the client log on shows a time out which is either a firewall issue or the server is not listening for connections

What debug level?

Link to post
Share on other sites
2 minutes ago, Jamie Newbon said:

Debug1 for now, please.

Narrowed it down to the Windows firewall on the server computer. Disabling the private networks firewall resumes functionality and the timeouts stop. When I turn it back on they quit. I've added Synergy to the allowed list, here are those entries below. Any additional changes I need to make?

etnlyUG.png

 

 

d9wWHun.png

Link to post
Share on other sites
Jamie Newbon

That should be all thats needed if it still doesn't work try allowing port 24800 through the firewall on the server computer.

  • Like 1
Link to post
Share on other sites
48 minutes ago, Jamie Newbon said:

That should be all thats needed if it still doesn't work try allowing port 24800 through the firewall on the server computer.

Adding inbound rules for the port on the firewall worked! Thanks for your help! 

Edited by adunker
Link to post
Share on other sites

I had a failure to install this version which I then fixed.

The computer is a Windows 10 Pro, not joined to a domain. The error was the classic, "Service "Synergy" (synergy) failed to start. Verify that you have sufficient privileges to start system services."

In order to fix this, I did the following:

  1. Updated Windows to the very latest version
  2. Uninstalled Synergy, then cleaned it via these Instructions: https://members.symless.com/help/s1-troubleshooting/s1-reinstall
  3. Installed the latest C++ redistributable from here: https://support.microsoft.com/en-ph/help/2977003/the-latest-supported-visual-c-downloads

I rebooted, and blammo, was able to install the software. Back in business! :)

  • Like 1
Link to post
Share on other sites
Mark Vitale

I got a "Service "Synergy" (synergy) failed to start. Verify that you have sufficient privileges to start system services." on 2 clients (upgraded fine on the server) - had to rollback to 1.10.2 all Windows 10 x64 - don't have the time to go through what Stonesand did. I will just wait to see if others are having the same issue and if there is a release to address the issue.

Thanks

Link to post
Share on other sites
  • 2 weeks later...

I had a Windows 7 boot drive go bad on me (I believe the MBR got damaged/deleted and I am moving on to a new drive with WIN 10 PRO). I have tried to install both the x64 version (x64 processor) and the x86 version when that received these same errors. Regardless, during the installation process(es) when it tries to start the service, I get the following error: "Service Synergy failed to start. Verify that you have sufficient privileges to start system services."

If I go to Services.msc and try to manually start Synergy, I get "Windows could not start the Synergy service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion."

I would REALLY like to get Synergy installed and move on to the rest of my rebuilding so that I can finally do some work. I am trying to install Synergy_1.10.3-stable_b126-ca35737a_windows-x (I won't try v. 2 because I have tried it several times in the past and it just hasn't worked for me and I have had to reinstall v. 1).

What can I do to get this installed properly? I've never had this problem in the past.

One thing that is weird is that I went to the instructions under "Fresh Install" and there are none of the entries for "Synergy" nor "Symless" in the Registry OR the "ProgramData" directory nor the User folders. Yet the Synergy service is listed in Services.msc. It's like it was never installed (probably because none of them ever completed) but the Service is "there."

Also just tried hacking the registry and removing Synergy from the list of Services. Rebooted and tried reinstalling and still get the errors. I cannot figure out why I am having all of this trouble on a brand new Windows install.

After spending ALL DAY trying to get this installed and running, I was finally able to go to the Sourceforge page, download v. 1.8.8 and it installed successfully. But now, I have the "out of date" message. I am a little afraid to try and update it. Maybe I'll just stick with a working albeit "out of date" installation.

Because I'm a glutton for punishment, I decided to try to update to "1.10 STABLE" and it gave me the same error as in the first post. I had to stop that installation and reinstall 1.8.8 which is now working. With the "out of date" message. (I've tried re-downloading 1.10 just in case the original download was corrupted and no difference). I guess I'll just stay "out of date" because "1.10 STABLE" apparently is NOT "stable.

Link to post
Share on other sites
  • Nick Bolton locked and locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...