Automatic sync fails on mac, manual sync works
I have the latest mac client installed on 10.5.6
I can manually sync just fine (see log below at 10:55:46)
However automatic sync fails saying synchronisation is not enabled (see log below 10:54:03)
I can confirm I did not make any changes in isync between the two entries and that sychronisation is enabled in isync.
p.s. (I have busysync installed on this mac if that makes a difference)
21/01/2009 10:54:05 SoocialSyncTool[13202] Soocial Sync Client started
21/01/2009 10:54:35 SoocialSyncTool[13202] SyncServer is unavailable: timed out trying to connect
21/01/2009 10:54:35 SoocialSyncTool[13202] Soocial could not sync: Synchronisation is not enabled!
21/01/2009 10:54:35 SoocialSyncTool[13202] Soocial could not sync: Synchronisation is not enabled!
21/01/2009 10:55:46 SoocialSyncTool[13206] Soocial Sync Client started
21/01/2009 10:55:46 SoocialSyncTool[13206] Soocial Sync Client started
21/01/2009 10:55:46 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:46.285 SoocialSyncTool[13206:10b] Soocial Sync Client started
21/01/2009 10:55:48 SoocialSyncTool[13206] Doing Fast sync
21/01/2009 10:55:48 SoocialSyncTool[13206] Doing Fast sync
21/01/2009 10:55:48 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:48.246 SoocialSyncTool[13206:10b] Doing Fast sync
21/01/2009 10:55:48 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:48.246 SoocialSyncTool[13206:10b] Doing Fast sync
21/01/2009 10:55:50 SoocialSyncTool[13206] Soocial sync ended successfully
21/01/2009 10:55:50 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:50.150 SoocialSyncTool[13206:10b] Soocial sync ended successfully
I can manually sync just fine (see log below at 10:55:46)
However automatic sync fails saying synchronisation is not enabled (see log below 10:54:03)
I can confirm I did not make any changes in isync between the two entries and that sychronisation is enabled in isync.
p.s. (I have busysync installed on this mac if that makes a difference)
21/01/2009 10:54:05 SoocialSyncTool[13202] Soocial Sync Client started
21/01/2009 10:54:35 SoocialSyncTool[13202] SyncServer is unavailable: timed out trying to connect
21/01/2009 10:54:35 SoocialSyncTool[13202] Soocial could not sync: Synchronisation is not enabled!
21/01/2009 10:54:35 SoocialSyncTool[13202] Soocial could not sync: Synchronisation is not enabled!
21/01/2009 10:55:46 SoocialSyncTool[13206] Soocial Sync Client started
21/01/2009 10:55:46 SoocialSyncTool[13206] Soocial Sync Client started
21/01/2009 10:55:46 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:46.285 SoocialSyncTool[13206:10b] Soocial Sync Client started
21/01/2009 10:55:48 SoocialSyncTool[13206] Doing Fast sync
21/01/2009 10:55:48 SoocialSyncTool[13206] Doing Fast sync
21/01/2009 10:55:48 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:48.246 SoocialSyncTool[13206:10b] Doing Fast sync
21/01/2009 10:55:48 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:48.246 SoocialSyncTool[13206:10b] Doing Fast sync
21/01/2009 10:55:50 SoocialSyncTool[13206] Soocial sync ended successfully
21/01/2009 10:55:50 [0x0-0x63e63e].com.apple.systempreferences[13151] 2009-01-21 10:55:50.150 SoocialSyncTool[13206:10b] Soocial sync ended successfully
2
people have this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The company marked this question as answered.
The best answer from the company
-
Our OSX developer has looked in to this problem and stated:
"This seems to be an apple bug that once got fixed and then, well, unfixed again. The issue is SyncServices not being "daemon safe", e.g. not being available when started from a daemon."
We will have to change the behavior of our OSX client to stop this from happening. Will take some time though.....
The company says
this answers the question
-
Inappropriate?Hey John,
The feedback the client give you is not very acurate. But the reason why it didn't work is also in the logs: "timed out trying to connect " This could be because of our sync servers being busy or your network connection not being available. We should probably give better feedback in the clients PrefPane.
Thanks for reporting this. -
Inappropriate?But ut always fails when it is meant to automotically sync. Only syncs if I press 'sync now' (100% of the time)
/that goes against it being a your end server problem surely? -
Inappropriate?John,
I guess you are right. I am seeing the same behavior on my machine. I am going to look in to it. -
Inappropriate?Finding out this a issue happening to people running 10.5 We are not sure why. We will have our Mac guy looking in to this.
-
Inappropriate?cheers! thanks for your prompt replies to my (many!!) questions!
-
Inappropriate?Our OSX developer has looked in to this problem and stated:
"This seems to be an apple bug that once got fixed and then, well, unfixed again. The issue is SyncServices not being "daemon safe", e.g. not being available when started from a daemon."
We will have to change the behavior of our OSX client to stop this from happening. Will take some time though.....
The company says
this answers the question
-
Inappropriate?Any clarification on 'some time' as I dont know whether to switch to a different service in the meantime?
-
John, we hope to have a fix this week.
Loading Profile...




EMPLOYEE