Comments on: OS X 10.5, SyncServer takes 100% of CPU

By: JackC NYC

JackC NYC — Fri, 19 Feb 2010 04:27:09 +0000

What worked for me was launching iSync
Preferences
uncheck Enable Syncing (removed from Activity Monitor)
check Enable Syncing

now SyncServer is not taking 90% CPU

good luck

By: Julio Alonso

Julio Alonso — Thu, 24 Dec 2009 09:21:41 +0000

I’ve had this problem for weeks now. All I was doing was killing the syncserver on activity task every time it started running. My machine was becoming almos unusable.

Thank you so much.

By: tyagain

tyagain — Sun, 19 Jul 2009 02:48:42 +0000

thank you – also saved me a lot of trouble!

By: Oliver Völckers

Oliver Völckers — Wed, 17 Jun 2009 08:04:04 +0000

Thanks alot, this fixed my problem with Apple’s sync. The first time I tried it I got the following response in the Terminal:

2009-06-17 07:57:21.895 perl[365:807] SyncServer is unavailable: exception when connecting: connection timeout: did not receive reply
PerlObjCBridge: NSException raised while sending reallyResetSyncData to NSObject object
name: “ISyncServerUnavailableException”
reason: “Can’t connect to the sync server: NSPortTimeoutException: connection timeout: did not receive reply ((null))”

After a few minutes, I tried again and everything worked as it should. I had to restore my data from MobileMe, of course, but I also had backups on other computers and with TimeMachine, so I felt safe.

P.S. My system is Mac OS X 10.5.7

By: leddunK » Meine Menüleiste

leddunK » Meine Menüleiste — Tue, 17 Feb 2009 21:26:40 +0000

[...] MobileMe-Sync: Diese Systemfunktion erfüllt gleich zwei Aufgaben. Zum einen hält sie via MobileMe Adressbuch- und Terminkalender zwischen Computer und iPhone synchron, zum anderen sorgt sie dafür, dass der Prozessorlüfter nicht einrostet (im Viertelstundentakt von 1800 auf 6200 Umdrehungen behoben). [...]

By: Ditlesen

Ditlesen — Fri, 23 Jan 2009 22:15:38 +0000

Andy T, you are the man…
I have had problem, with my MobileMe, for soooo long time, but I think you just fixed it!!!

By: Paul

Paul — Wed, 07 Jan 2009 20:47:11 +0000

At first it didn’t work for me either at first. Ugly error messages appeared along the lines of “NS exception was thrown”. I then restarted, and before the syncserver could start its evil work, started Terminal and executed the command. The error message did not appear, and all is well. Thanks.

By: Scott

Scott — Wed, 07 Jan 2009 20:31:13 +0000

I used Andy T’s procedure and it also resolved my issue (Thanks for posting Andy). I was initially confused about the location of the SyncServices folder, it’s in the user’s library directory, not the system’s library folder. This issue was user-specific for me (you can test this by creating a separate user account and then logging in to that one to see if the SyncServer goes crazy on that other account–which it didn’t in my case). I hope this helps.

By: Andy T

Andy T — Tue, 06 Jan 2009 20:28:28 +0000

This didn’t work for me, I got a time out message from python (even in safe mode). Single user mode didn’t help either. However, it did set me on the right path. Apple “STRONGLY DISCOURAGES” messing with the ~/Library/Application Support/SyncServices folder as it may lead to “unexpected data loss”. My machine was unusable, so I bit the bullet. I copied the SyncServices folder to the desktop and compressed it as a back-up. Then logged out and back in again. Then I went strait to the MobileMe Preferance Pane. In the sync tab, in advanced I “Reset Sync Data” on my machine. I was then presnted with a dialog box asking whether to replace all on MobileMe or replace all on my computer. As this is my msater machine I replaced all on MoblieMe and all is now hunky dory (thats a good thing by the way). Thanks alot

By: sata

sata — Thu, 13 Nov 2008 11:55:04 +0000

Thanks! Seems like this work for me too ^^