Win10 absolutely nothing

[XavierBacon]

this is in my log, same as on the connected m/c.

[ Config ] [2017-09-14T14:54:17] INFO: log filename: C:/Users/ME/AppData/Local/Symless/Synergy/synergy.log

[ Config ] [2017-09-14T14:54:17] DEBUG: connecting to service

[ Config ] [2017-09-14T14:54:18] DEBUG: new added screen pos: 257 161

[ Config ] [2017-09-14T14:54:19] DEBUG: Profile ID: 17 name: default

[ Config ] [2017-09-14T14:54:19] DEBUG: current version is update to date

[ Config ] [2017-09-14T14:54:19] DEBUG: requesting profile snapshot

 

cheers

Alan

[Nick Bolton]

Could you use the "Send log" feature? I need to see the whole log.

[XavierBacon]

Is this it?

Upload path: https://synergy-logs.symless.com/2017-09-15/26-2017-09-15T10-22-21.log

[Mad3813]

Got my Windows 7 Pro (x64) PC talking to my Windows 10 (x64) Surface Pro with zero issues here, setup and config (or lack of) was instant.

[Nick Bolton]

1 hour ago, XavierBacon said:

Is this it?

Upload path: https://synergy-logs.symless.com/2017-09-15/26-2017-09-15T10-22-21.log

Ah, here we go...

[ Config  ] [2017-09-13T23:21:16] ERROR: Network request error: 499
[ Config  ] [2017-09-13T23:21:16] ERROR: Reply status code: 502

Could you please follow this guide?

https://symless.com/synergy-2-beta4-troubleshooting

[XavierBacon]

Yea that log entry is from a couple of days ago, my firewall has been off ever since.

I have followed the troubleshooting guide just in case. But this is still all I get in the log.

[ Config  ] [2017-09-15T11:51:13] INFO: log filename: C:/Users/DAD/AppData/Local/Symless/Synergy/synergy.log
[ Config  ] [2017-09-15T11:51:13] DEBUG: connecting to service
[ Config  ] [2017-09-15T11:51:14] DEBUG: new added screen pos: 257 161
[ Config  ] [2017-09-15T11:51:16] DEBUG: Profile ID: 17 name: default
[ Config  ] [2017-09-15T11:51:16] DEBUG: current version is update to date
[ Config  ] [2017-09-15T11:51:16] DEBUG: requesting profile snapshot
[ Config  ] [2017-09-15T11:51:23] DEBUG: forcing current computer to be server
[ Config  ] [2017-09-15T11:51:38] INFO: Sending log file...

Cheers

 

Alan

[Nick Bolton]

Did you restart the Synergy window after restarting the service?

[XavierBacon]

Yes I did Nick, and F12'd it.

[Nick Bolton]

4 hours ago, XavierBacon said:

Yes I did Nick, and F12'd it.

Could you check your process list and make sure "synergyd" is in there?

[XavierBacon]

Hi Nick, It's there along with service controller.

[Nick Bolton]

15 minutes ago, XavierBacon said:

Hi Nick, It's there along with service controller.

Could you send your latest log?

[XavierBacon]

Nick all I get is the same 8 lines as previously posted.

[Nick Bolton]

2 hours ago, XavierBacon said:

Nick all I get is the same 8 lines as previously posted.

I need to see the whole log to make sense of it.

[XavierBacon]

Here you go

 

https://synergy-logs.symless.com/2017-09-16/26-2017-09-16T16-23-10.log

[Nick Bolton]

On 9/16/2017 at 4:23 PM, XavierBacon said:

Here you go

 

https://synergy-logs.symless.com/2017-09-16/26-2017-09-16T16-23-10.log

Try restarting the services and the main Synergy program.

[XavierBacon]

right this is weird!

I knew that restarting the services and restating Synergy program wouldn't make any difference (and it didn't).

So I thought rather than send you another log with old data in it, I would clear the log down.

Now when I restart everything comes to life and starts working!! How's that?

Now I just can't get my second m/c to start properly but at least I am getting somewhere now.

I will post the log from the second m/c at some point but I'd like to hear your views on the log anomaly.

cheers 

Alan

[Nick Bolton]

2 hours ago, XavierBacon said:

Now when I restart everything comes to life and starts working!! How's that?

 

The connect test randomly fails. Restarting the services is the only known workaround right now. This'll be fixed in beta5.