jae

There was a problem connecting to the background service. Retry

20 posts in this topic

Hi there,

I have installed Synergy 2 on my both Mac/Windows computers at home and it worked great with some hiccups. (sometimes it didn't pickup host to share.)

However, next time I came to work and install different Mac/Windows computers which are not the same machine but the exact the same version of macos and windows and I never got them to work.

Since installing it on them at work, my both home mac/windows started to fail to connect.

I have tried to reinstall as the instruction I found here (remove completely and fresh install it again), did not help me to fix the issue.

It kept saying 'There was a problem connecting to the background service. Retry.'

On Windows, when I see and look at the service of Synergy, it kept failing to start the service so it just tries to restart over and over. (infinity loop)

It has been sitting like this for 5 days and I have also created a ticket but no one has been contacted me to resolve this issue.

I hope some one can help me to resolve this issue. I really want this working, but I feel like I totally wasted my money and time on this.

I have reinstalled it again to add the log as an attachment. (the service is still failing.)

Thanks,

Jae

Symless.log

Share this post


Link to post
Share on other sites

It sounds like you've done great troubleshooting. I'm not able to open the log on my end. Don't post the whole log here, but when you save it and view it, you should get a URL you can share.

You're using the 2.0.9 version, right? It has several re-connections fixes.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi GranPaSmurf,

I will re-attach the log in here below. Basically, this segment is just over and over in the log.

and also, it's Synergy 2.0.8.

I'm trying to update to 2.0.9 and I will post the result :)

Symless User ID: 55245
Operating System: osx 10.13
Synergy Version: 2.0.8-stable
System Name: jaes-work-mbp.ad.ypg.com

[ Service ] [2018-04-10T07:51:36] info: starting service...
[ Service ] [2018-04-10T07:51:36] debug: setting websocket headers, channel=55216 auth=DDFxEajxfjzsJ4k1BGk_hd_- version=2.0.8-stable check=true
[ Service ] [2018-04-10T07:51:36] debug: initial websocket connection
[ Service ] [2018-04-10T07:51:36] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Router  ] [2018-04-10T07:51:36] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-04-10T07:51:36] debug: Initialized
[ Router  ] [2018-04-10T07:51:36] debug: Starting...
[ Router  ] [2018-04-10T07:51:36] debug: ID = 140381, Name = 'jaes-work-mbp.ad.ypg.com'
[ Service ] [2018-04-10T07:51:36] debug: creating rpc endpoints
[ Service ] [2018-04-10T07:51:36] debug: rpc endpoints created
[ Service ] [2018-04-10T07:51:36] debug: cloud client connected
[ Service ] [2018-04-10T07:51:36] debug: websocket connected
[ Service ] [2018-04-10T07:51:36] debug: comparing profiles, id=-1 this=v-1 other=v44
[ Service ] [2018-04-10T07:51:36] debug: profile id changed, -1->55216
[ Service ] [2018-04-10T07:51:36] debug: profile name changed, ->default
[ Service ] [2018-04-10T07:51:36] debug: profile server changed, -1->139867
[ Service ] [2018-04-10T07:51:36] debug: profile screen set changed, added=3 removed=0
[ Service ] [2018-04-10T07:51:36] debug: Waiting for screen 139871 to become reachable
[ Service ] [2018-04-10T07:51:36] debug: profile changed, storing local copy
[ Service ] [2018-04-10T07:51:36] debug: handling cloud message: server claim, mode=unknown thisId=140381 serverId=139867 lastServerId=-1
[ Service ] [2018-04-10T07:51:36] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T07:51:36] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T07:51:36] debug: closing existing websocket connection
[ Service ] [2018-04-10T07:51:36] debug: cancelled websocket lowest layer
[ Service ] [2018-04-10T07:51:36] error: service failed: Invalid argument
[ Service ] [2018-04-10T07:51:46] debug: service log file path: /Users/jae/Library/Synergy/synergy-service.log
[ Service ] [2018-04-10T07:51:46] debug: install dir: /Applications/Synergy.app/Contents/MacOS
[ Service ] [2018-04-10T07:51:47] info: starting service...
[ Service ] [2018-04-10T07:51:47] debug: setting websocket headers, channel=55216 auth=DDFxEajxfjzsJ4k1BGk_hd_- version=2.0.8-stable check=true
[ Service ] [2018-04-10T07:51:47] debug: initial websocket connection
[ Service ] [2018-04-10T07:51:47] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Router  ] [2018-04-10T07:51:47] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-04-10T07:51:47] debug: Initialized
[ Router  ] [2018-04-10T07:51:47] debug: Starting...
[ Router  ] [2018-04-10T07:51:47] debug: ID = 140381, Name = 'jaes-work-mbp.ad.ypg.com'
[ Service ] [2018-04-10T07:51:47] debug: creating rpc endpoints
[ Service ] [2018-04-10T07:51:47] debug: rpc endpoints created
[ Service ] [2018-04-10T07:51:47] debug: cloud client connected
[ Service ] [2018-04-10T07:51:47] debug: websocket connected
[ Service ] [2018-04-10T07:51:47] debug: comparing profiles, id=-1 this=v-1 other=v44
[ Service ] [2018-04-10T07:51:47] debug: profile id changed, -1->55216
[ Service ] [2018-04-10T07:51:47] debug: profile name changed, ->default
[ Service ] [2018-04-10T07:51:47] debug: profile server changed, -1->139867
[ Service ] [2018-04-10T07:51:47] debug: profile screen set changed, added=3 removed=0
[ Service ] [2018-04-10T07:51:47] debug: Waiting for screen 139871 to become reachable
[ Service ] [2018-04-10T07:51:47] debug: profile changed, storing local copy
[ Service ] [2018-04-10T07:51:47] debug: handling cloud message: server claim, mode=unknown thisId=140381 serverId=139867 lastServerId=-1
[ Service ] [2018-04-10T07:51:47] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T07:51:47] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T07:51:47] debug: closing existing websocket connection
[ Service ] [2018-04-10T07:51:47] debug: cancelled websocket lowest layer
[ Service ] [2018-04-10T07:51:47] error: service failed: Invalid argument

 

Edited by jae

Share this post


Link to post
Share on other sites

This is after updating to 2.0.9 :'( so it didn't resolve the issue.

I'm not too sure if I need to re-install (fresh install) this.

Symless User ID: 55245
Operating System: osx 10.13
Synergy Version: 2.0.9-stable
System Name: jaes-work-mbp.ad.ypg.com
[ Service ] [2018-04-10T08:30:47] info: starting service...
[ Service ] [2018-04-10T08:30:47] debug: setting websocket headers, channel=55216 auth=DDFxEajxfjzsJ4k1BGk_hd_- version=2.0.9-stable check=true
[ Service ] [2018-04-10T08:30:47] debug: initial websocket connection
[ Service ] [2018-04-10T08:30:47] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Router  ] [2018-04-10T08:30:47] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-04-10T08:30:47] debug: Initialized
[ Router  ] [2018-04-10T08:30:47] debug: Starting...
[ Router  ] [2018-04-10T08:30:47] debug: ID = 140381, Name = 'jaes-work-mbp.ad.ypg.com'
[ Service ] [2018-04-10T08:30:47] debug: creating rpc endpoints
[ Service ] [2018-04-10T08:30:47] debug: rpc endpoints created
[ Service ] [2018-04-10T08:30:47] debug: cloud client connected
[ Service ] [2018-04-10T08:30:47] debug: websocket connected
[ Service ] [2018-04-10T08:30:47] debug: comparing profiles, id=-1 this=v-1 other=v44
[ Service ] [2018-04-10T08:30:47] debug: profile id changed, -1->55216
[ Service ] [2018-04-10T08:30:47] debug: profile name changed, ->default
[ Service ] [2018-04-10T08:30:47] debug: profile server changed, -1->139867
[ Service ] [2018-04-10T08:30:47] debug: profile screen set changed, added=3 removed=0
[ Service ] [2018-04-10T08:30:47] debug: Waiting for screen 139871 to become reachable
[ Service ] [2018-04-10T08:30:47] debug: profile changed, storing local copy
[ Service ] [2018-04-10T08:30:47] debug: handling cloud message: server claim, mode=unknown thisId=140381 serverId=139867 lastServerId=-1
[ Service ] [2018-04-10T08:30:47] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:30:47] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:30:47] debug: closing existing websocket connection
[ Service ] [2018-04-10T08:30:47] debug: cancelled websocket lowest layer
[ Service ] [2018-04-10T08:30:48] error: service failed: Invalid argument

Share this post


Link to post
Share on other sites

Restarting the Synergy service on each machine sometimes helps.

also, on your GUI, if you mouse-grab a screen and move it so it is not attached (everything goes gray...) then replace it, that should restart the synergy-core on each computer

Share this post


Link to post
Share on other sites
Posted (edited)

So, I re-installed and also as you mentioned, I tried to restart Synergy service as the instruction below, however it didn't change anything. I still see the a problem connecting to the background service.

I also attached the log below.

 

[ Service ] [2018-04-10T08:41:51] info: starting service...
[ Service ] [2018-04-10T08:41:51] debug: setting websocket headers, channel=55216 auth=G6JRL1cUTULdCmSDkfXqQ4tv version=2.0.9-stable check=true
[ Service ] [2018-04-10T08:41:51] debug: initial websocket connection
[ Service ] [2018-04-10T08:41:51] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Router  ] [2018-04-10T08:41:51] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-04-10T08:41:51] debug: Initialized
[ Router  ] [2018-04-10T08:41:51] debug: Starting...
[ Router  ] [2018-04-10T08:41:51] debug: ID = 140381, Name = 'jaes-work-mbp.ad.ypg.com'
[ Service ] [2018-04-10T08:41:51] debug: creating rpc endpoints
[ Service ] [2018-04-10T08:41:51] debug: rpc endpoints created
[ Service ] [2018-04-10T08:41:51] debug: cloud client connected
[ Service ] [2018-04-10T08:41:51] debug: websocket connected
[ Service ] [2018-04-10T08:41:51] debug: comparing profiles, id=-1 this=v-1 other=v44
[ Service ] [2018-04-10T08:41:51] debug: profile id changed, -1->55216
[ Service ] [2018-04-10T08:41:51] debug: profile name changed, ->default
[ Service ] [2018-04-10T08:41:51] debug: profile server changed, -1->139867
[ Service ] [2018-04-10T08:41:51] debug: profile screen set changed, added=3 removed=0
[ Service ] [2018-04-10T08:41:51] debug: Waiting for screen 139871 to become reachable
[ Service ] [2018-04-10T08:41:51] debug: profile changed, storing local copy
[ Service ] [2018-04-10T08:41:51] debug: handling cloud message: server claim, mode=unknown thisId=140381 serverId=139867 lastServerId=-1
[ Service ] [2018-04-10T08:41:51] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:41:51] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:41:51] debug: closing existing websocket connection
[ Service ] [2018-04-10T08:41:51] debug: cancelled websocket lowest layer
[ Service ] [2018-04-10T08:41:51] error: service failed: Invalid argument
[ Service ] [2018-04-10T08:42:01] debug: service log file path: /Users/jae/Library/Synergy/synergy-service.log
[ Service ] [2018-04-10T08:42:01] debug: install dir: /Applications/Synergy.app/Contents/MacOS
[ Service ] [2018-04-10T08:42:01] info: starting service...
[ Service ] [2018-04-10T08:42:01] debug: setting websocket headers, channel=55216 auth=G6JRL1cUTULdCmSDkfXqQ4tv version=2.0.9-stable check=true
[ Service ] [2018-04-10T08:42:01] debug: initial websocket connection
[ Service ] [2018-04-10T08:42:01] debug: connecting websocket: pubsub1.cloud.symless.com:443
[ Router  ] [2018-04-10T08:42:01] debug: binding to 0.0.0.0:24802
[ Router  ] [2018-04-10T08:42:01] debug: Initialized
[ Router  ] [2018-04-10T08:42:01] debug: Starting...
[ Router  ] [2018-04-10T08:42:01] debug: ID = 140381, Name = 'jaes-work-mbp.ad.ypg.com'
[ Service ] [2018-04-10T08:42:01] debug: creating rpc endpoints
[ Service ] [2018-04-10T08:42:01] debug: rpc endpoints created
[ Service ] [2018-04-10T08:42:02] debug: cloud client connected
[ Service ] [2018-04-10T08:42:02] debug: websocket connected
[ Service ] [2018-04-10T08:42:02] debug: comparing profiles, id=-1 this=v-1 other=v44
[ Service ] [2018-04-10T08:42:02] debug: profile id changed, -1->55216
[ Service ] [2018-04-10T08:42:02] debug: profile name changed, ->default
[ Service ] [2018-04-10T08:42:02] debug: profile server changed, -1->139867
[ Service ] [2018-04-10T08:42:02] debug: profile screen set changed, added=3 removed=0
[ Service ] [2018-04-10T08:42:02] debug: Waiting for screen 139871 to become reachable
[ Service ] [2018-04-10T08:42:02] debug: profile changed, storing local copy
[ Service ] [2018-04-10T08:42:02] debug: handling cloud message: server claim, mode=unknown thisId=140381 serverId=139867 lastServerId=-1
[ Service ] [2018-04-10T08:42:02] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:42:02] debug: ignoring core process shutdown request, core is not running
[ Service ] [2018-04-10T08:42:02] debug: closing existing websocket connection
[ Service ] [2018-04-10T08:42:02] debug: cancelled websocket lowest layer
[ Service ] [2018-04-10T08:42:02] error: service failed: Invalid argument

Screen Shot 2018-04-10 at 8.45.25 AM.jpg

Edited by jae

Share this post


Link to post
Share on other sites

I think I've run out of troubleshooting level ideas.

Support has been pretty fast recently.

SUPPORT  
Report your experience to support. Send logs from each machine. Trouble tickets drive development 
[email protected]

 

Share this post


Link to post
Share on other sites

Thanks for the help!

Yes, I have contacted them and been asked to install 2.0.9, but it didn't help.

I am still waiting for their response so I guess I will see.

If I can use Synergy 2 at home at least, I wouldn't worry too much about it but I cannot use Synergy at all. (home nor office).

Hope I have other choices.

Thanks for helping anyways.

Share this post


Link to post
Share on other sites

Issue could be you have a proxy server between you and the internet at work.  Synergy 2 doesn't support this configuration, and despite Nick promising months ago that it would be added to the "next release", such support no longer appears on the roadmap at all.

Share this post


Link to post
Share on other sites
56 minutes ago, JeffDG said:

Issue could be you have a proxy server between you and the internet at work.  Synergy 2 doesn't support this configuration, and despite Nick promising months ago that it would be added to the "next release", such support no longer appears on the roadmap at all.

Sorry for the delay, proxy support is imminent. However, background service issues (OP) aren’t caused by lack of proxy support (that’s actually a bug). So that’s a separate issue to the OP.

Share this post


Link to post
Share on other sites

If I added extra, this issue is not only affecting in my office computers. It is not happening to my home computers as well.

So basically, I am not be able to use Synergy 2 completely. None of my mac/windows computers are working with Synergy 2.

I have installed Synergy in new computer at home and it still gets the same error and I only can think, it some how referencing my previous network settings? or profile??

Anyways, if this is a bug, can it be fixed soon? so I am going to be able to use it soon? :)

Share this post


Link to post
Share on other sites
12 hours ago, jae said:

So basically, I am not be able to use Synergy 2 completely. None of my mac/windows computers are working with Synergy 2.

1

Sorry about that, have you opened a support ticket? https://symless.com/contact/customer-support

Share this post


Link to post
Share on other sites
Posted (edited)

Hi Nick,

yes, I have contacted the support, but other than installing newer version (2.0.9) nothing was given.

Interesting is they didn't give me any ticket number or anything to reference other than replying email back. (I think this link is to view my request in zendesk, but have no account so can't see) ttps://symless.zendesk.com/hc/requests/68792

Please let me know what I need to do regarding to resolve this asap unless I will need to ask to refund which will be completely wasting my time for all of this.

Is there a way to try Synergy 1 instead 2? if version 1 works at least on my machine which I don't even know. (but my colleague's computers work fine with version 1 at work)

Edited by jae

Share this post


Link to post
Share on other sites
Posted (edited)

Hi everyone,

I've got a response from the support and I was able to install Synergy 1 finally.

It actually didn't work at first and I need to switching server/client back and forth a couple of times between Mac and Windows.

In short, I got it working!! :) Thanks for the help.

I guess I will stay away from version 2 for a while, however, I am not too sure if I should be able to install this on my work computers and use it.. :S

FYI, in Synergy 2, can you guys add a switch that can change server/client manually? I see in the beginning of the log, client kept being refused to connect and after I was switching them a couple of times, it got me working somehow.. hmm weird..

Anyways, thank you so much for all the help!

Edited by jae

Share this post


Link to post
Share on other sites

Hello Nick/Members, 

I bought Synergy some months ago and it worked the first day but its not worked since then. 

I have shared multiple emails with support and its still not working.

I have also installed 2.0.9 and its still showing There was a Problem Connecting to the background service - Retry.

Basically, I am not able to use it. 

Can you help out or should I just ask for refund. 

 

Share this post


Link to post
Share on other sites

What OSs are you using?

Re-submit the support ticket. That gets your. Issue in front of the developers.

Basically, the DYI troubleshooting is stop/start Synergy service and retry... next step is a though uninstall from all machines then reinstall. Reboot all.

In my system, I think the key to good operation has been the thorough uninstall. I'm lazy, I use a 3rd party uninstaller, Revo. They have a free version.

But, full circle, keep on support's list. If you have a really unusual situation, they want to learn from your issue.

 

Share this post


Link to post
Share on other sites

Hi jibs,

I would suggest to install Synergy 1.

None of the restart services on both Macos/Windows and re-installing solution didn't work at all.

Even Synergy 1, I need to switch mater/client back and forth finally helped me to use properly.

I think you will need to create a ticket/reply the current ticket for Synergy 1 to try.

I would say give a try Synergy 1.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now