Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Upgrade to Lion - SyncServer Error messages in console - solution

Hi,


maybe someone will run into similar problems, so I want to share the solution I found for myself.


With the upgrade to Lion (or in my case, a new MBP with Lion installed and using the data migration assistant to get the data from my old MBP), a lot of SyncServer error messages appeared in console, like these here:


SyncServer: [0x107116cb0] |DataManager|Warning| Client com.apple.Palm:3265638981 image file path /System/Library/PrivateFrameworks/SyncLegacy.framework/Versions/A/Resources/Pal mBladeConduit.bundle/Contents/Resources/tungsten.tiff does not exist.

SyncServer: [0x107116cb0] |DataManager|Warning| Client com.apple.Palm:3265638981 sync alert tool path /System/Library/PrivateFrameworks/SyncLegacy.framework/Resources/Translator does not exist.

AM SyncServer: [0x107116cb0] |DataManager|Warning| Client com.apple.Palm:3265638981 formatter bundle path /System/Library/PrivateFrameworks/SyncLegacy.framework/Resources/Translator does not exist.


So, I tried to track it down.

It appears that Apple changed from 10.6 to 10.7 quite a bit regarding the Sync services, so that old plugins that used to give no errors in 10.6 show up on console.


The currently active Syncservices are all stored in your own

username/Library/Application Support/SyncServices/Local

package


One can either open this package content and try to delete obsolete SyncServices (directories) by hand.

Or one can use the program "Syncrospector" to do this.


In fact, there were LOTS of old iSync remains (Palm, mobile phones etc.) waiting to be cleared.

Some of them have not been used since 10.4 or 10.5 but still were carried over at every system upgrade or even data migration.


After clearing these old Sync services, all the error messages disappeared.

No problems after that, either.


I can really recommend Syncrospector, which seems to be part of the system 10.7

It seems to be able to do a wealth of other things for Syncing, as well.


Martin

MacBook Pro, Mac OS X (10.7.1)

Posted on Aug 29, 2011 2:11 AM

Reply
13 replies

Jul 27, 2012 12:04 PM in response to Richard E. Cooke

Since upgrading to Mountain Lion from Lion I see the following message repeated in the console:


DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.


I've opened the "local" file mentioned above in Text Wrangeler but find no reference to mailsync just a file called clientname.txt that has com.apple.mail in it. Is this what I should be deleting?

Sep 2, 2012 3:10 AM in response to duosx

Me too - but I have only just discovered that my symptoms were due to a sync error.


I had started a discussion on the problem I had:

"Mountain Lion tries to connect to another disc"

https://discussions.apple.com/thread/4248722?answerId=19417049022#19417049022


As for the original post by Martin (mampo), I have bought a new MBP. I did a full migration from an older MBP, then upgraded to Mountain Lion. Under certain circs (eg connecting an iPhone or iPod to iTunes, starting Mail, editing Contacts) the new MBP wanted to connect to the old MBP. Very irritating. I was stuck for a cause until I looked at the system log (why didn't I do that sooner?). I'm getting things like this whenever a spurious connection attempt is made:


Sep 2 10:14:39 <New MBP name>.local SyncServer[1521]: [0x7ff2f840bef0] |DataManager|Warning| Client com.apple.Mail sync alert tool path /Volumes/<Old MBP name>/System/Library/Frameworks/Message.framework/Versions/B/Resources/MailSync does not exist.


Like Matthew Wilson5, I can't see anything in the .../SyncServices/Local package that mentions the old MBP.


I'll be watching this discussion and hoping somebody's going to tell us how to fix this...

Sep 15, 2012 3:02 AM in response to RobertDHarding

Nearly two weeks after that last post and I've heard nothing further to get a full diagnosis of this issue.


I have eliminated the problem (I would not say 'solved') by making a full bootable backup of my system, erasing the MBP hard disc, reinstalling just the system, then followed up with a manual re-install of up to date applications, and copied in all user files that I wanted to keep. I excluded all Library files.


It is a long job but has ensured a clean system free of legacy issues.

Sep 16, 2012 1:59 AM in response to vrenna

Thanks - spot on. As you saw from my earlier post, I had got round the issue by completely rebuilding my system, with manual re-importing of data, settings etc, but I kept a full bootable backup on an external disc. I have just tried this, as follows:


a) restart from external disc, ensure wi-fi off and no network connections, open iTunes, connect iPhone. There's a 15 sec pause then the error is generated. So this was exactly the behaviour I reported.


b) Followed vrenna's link to the Apple document "Mac OS X: Resetting the SyncServices folder", followed instructions for ML.


c) re-tried a) - and the faulty behaviour has gone away. So vrenna's diagnosis confirmed.


Many thanks! That would have been a quick way to sort it out, but rebuilding the system had some benefits (lots of junk cleared) so my time was not entirely wasted.

Upgrade to Lion - SyncServer Error messages in console - solution

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.