Problem with iSync in Tiger

[artemio]

There seems to be a (relatively) harmless problem with the new iSync app in Tiger. In fact, every hour I get the following error message in my console and system logs:

Apr 30 14:21:25 imac-g5 crashdump[14969]: Scheduler crashed
Apr 30 14:21:25 imac-g5 crashdump[14969]: crash report written to: /Users/artemio/Library/Logs/CrashReporter/Scheduler.crash.log
*** loading the extensions datasource
dyld: Library not loaded: /System/Library/PrivateFrameworks/SyncEngine.framework/Versions/A/SyncEngine
Referenced from: /Applications/iSync.app/Contents/Resources/Scheduler.app/Contents/MacOS/Scheduler
Reason: image not found

The SyncEngine framework was indeed present in Panther, but it's missing in Tiger (at least on my computer). Has anybody experienced this? Any ideas on how to fix it?

Cheers,

Artemio Gonzalez
artemio@eresmas.net

[thetrent@mac.com]

I have the exact same error as you - check out your scheduler.crash.log

To me it looks like the panther isync 1.5 is crashing, and the new Tiger 2.0 sync is working -

How do we get rid of the 1.5 scheduler entry??

Look in your console - there is a schedulercrash log - something like that -

Here is my entry -

**********

Host Name: Trent-Computer
Date/Time: 2005-04-30 18:52:52.419 -0400
OS Version: 10.4 (Build 8A428)
Report Version: 3

Command: Scheduler
Path: /Applications/iSync.app/Contents/Resources/Scheduler.app/Contents/MacOS/Scheduler
Parent: WindowServer [61]

Version: 1.5 (139)

PID: 347
Thread: Unknown

Link (dyld) error:

Library not loaded: /System/Library/PrivateFrameworks/SyncEngine.framework/Versions/A/SyncEngine
Referenced from: /Applications/iSync.app/Contents/Resources/Scheduler.app/Contents/MacOS/Scheduler
Reason: image not found

[thetrent@mac.com]

Posted this in the mac forums - and someone there actually figured it out -

Install xcode2 from the tiger dvd -

And David on the forums on apple.com - gave these directions:

"You need to have the Developer kit installed to edit plist files, first off. (It's on the kit and provides useful features; everyone should install it except, perhaps, if you're really tight on disk space.) If you don't, you'll have to do this with a text editor and be careful of the XML structure. Or just trash the entire plist file and reset your other timed entries. This file controls your .Mac sync updates, Apple Backup, SoftwareUpdate checks, CHUD development tool update checks if you've ever enabled that, and probably other things that I don't have enabled. So before you delete it you should probably at least look through to see what you need to re-set later. (Unless you don't have the plist editor, it's easiest to delete the one entry!)

OK, so go to your home directory->Library->Preferences (or ~/Library/Preferences in UNIX filespec terminology). Scroll down the long, long list to find com.apple.scheduler.plist. It's always a good idea to make a backup; just select the file and duplicate it. (There's no reason you'd need the old copy, and no reason to expect you'll accidentally damage the copy you edit... but I always prefer to be safe because it's the times I know I don't need to that I get myself in trouble!) Now double-click to edit the original plist file in the Property List Editor.

Click on on the "Root" disclosure triangle to open it. You'll probably see a single entry called "AbsoluteSchedule"; in any case, open that one, too. You'll see a list of entries, and one of them should be "com.apple.isync.scheduler". It has a disclosure triangle, too; and you can open that to see the details, but you don't need to. Just select the line and delete it by clicking the "Delete" button up at the top. Now Save the file, and Quit.

Note that the plist is read at login, and so you still have a scheduled job running at this point. If it runs again while you're still logged in, it will RECREATE the scheduler entry and you'll need to edit the plist file again. So LOG OUT, and then log in again -- or if you want to be conservative, just restart. (I restarted; restarting is pretty fast in Tiger.)"

[artemio]

That solved the problem, indeed. Thanks a lot!

Artemio