Upgradedb error after Leopard u/g

[Dabow]

Hi all,

I'm hoping someone may be able to shed some light on why I am receiving continuous "The application upgradedb quit unexpectedly" messages after my recent upgrade to Leopard. If I try and 'Relaunch' the message pops up again. If I 'Ignore' it disappears for a while then later reappears. This is perhaps a general message, but if someone can point me in the right direction as to what may be causing it and how I can fix/remove it that would be most helpful. Thanks in advance.

Dave

[Giaguara]

Did you install 10.5 client on 10.4 Server?

I've only seen upgradedb error messages on server. Are you trying to upgrade mail databases? (p. 42)
This is for 10.4 upgrade but unless they changed the location of the Server's core services, it should still be valid.

If it's on normal Mac OS X 10.5 client, which application launches this upgradedb message? Some database is trying to upgrade itself, and it would be good to know what it was.

Open Console (Applications/Utilities) when it starts to give this error again, and then look at Console to see what it says (post the code it will generate then, it will contain what asked for what in your system).

[Dabow]

Giaguara,

Many thanks for the advice. This was a straight forward upgrade from Tiger client to Leopard client. When it reappears (so far it hasn't appeared tonight) I'll follow your suggestion

[Giaguara]

Ok. I'm very curious which application would have this database ...

[jernst]

Blogged about it here: http://netmesh.info/jernst/Personal/...edb-crash.html

I have never touched OSX server in my life so that can't really be it.

[Giaguara]

/System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb is where it's calling it from.. so SyncServer.app. Core services in the Mac.

Would you have Missinc Sync app installed?

Let's see if it's something with permissions..
In Terminal (Applications/Utilities), type

ls -lias /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb

For comparison, on a healthy 10.4 the output would be something like
462336 2008 -rwxr-xr-x 1 root wheel 1026116 Apr 25 2007 /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb
At least the owner and permissions should be the same.
What do you get with that command as output?

[jernst]

What I have what installed, exactly?

Here's some output. Note my file seems to be larger than your's.

% ls -lias /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb
1762993 3216 -rwxr-xr-x 1 root wheel 1643440 Oct 4 23:16 /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb
% file /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb
/System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb: Mach-O universal binary with 2 architectures
/System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb (for architecture ppc7400): Mach-O executable ppc
/System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb (for architecture i386): Mach-O executable i386
% /System/Library/Frameworks/SyncServices.framework/Versions/Current/Resources/SyncServer.app/Contents/Resources/upgradedb
Bus error

[Giaguara]

Hm, permissions for it are ok, it should be able to execute it. So next probability is .mac sync database or other corruption error.

Do you have .Mac sync enabled? If so, in System Preferences, .Mac, try if any of these or these tips work, if not ...
"Reset Sync Data..." (make a backup of everything that you sync there first, just in case). That should reset the database.

Apple recommends staying away form the sync folder, but if it doesn't go away with any of those other options, may need to try as the next resort.

If any of those steps will fix it, I'm curious to see which one did it as I've never seen this exact error on Client as said