Currently Being ModeratedJul 15, 2012 10:39 AM (in response to Localboy56)
Just an update on troubleshooting: I did copy the Aperture pref file and app support folder from my Macbook into my library on the iMac. Didn't fix the problem but Aperture now bounces twice in the dock before stopping so maybe that's progress.
Currently Being ModeratedJul 15, 2012 12:51 PM (in response to Localboy56)
I think your issue is because you migrated apps... Not good to do this. Never migrate apps. Always do a fresh install....
Here ( at the bottom of the page ) is detailed instructions on how to do a fresh install... This may resolve your issue....
BE SURE TO DO A BACK UP BEFORE COMMENCING WITH A FRESH INSTALL....
Kind regards... Gerry
Message was edited by: windhoveruk
Currently Being ModeratedJul 15, 2012 1:52 PM (in response to windhoveruk)
Thank you for your suggestions Gerry. I have already uninstalled Aperture and reinstalled a fresh copy from the MAS. That didn't get Aperture launched unfortuntely.
I tried to get to the Aperture Library First Aid screen via the Option-Command keys when launching Aperture and that hasn't worked either.
My aperture library on my Macbook opens up just fine so I'm thinking I might delete the Aperture file on the iMac and see if Aperture will open and create a new blank library. Then either import images from the file on the Macbook or just copy over the library file from the Macbook.
Please wish me luck on this, it has been a very scary, frustrating day so far!
Currently Being ModeratedJul 15, 2012 2:03 PM (in response to Localboy56)
Well I copied the Aperture Library onto an external hard disk, then deleted the library file from the iMac. When I tried to launch Aperture, the problem of failing to load continues. I'm kind at a loss for what to do next...
Currently Being ModeratedJul 15, 2012 2:17 PM (in response to léonie)
Here's the header data of the latest Aperture Crash Log (Kahawalu is the name of the iMac)
Process: Aperture 
Version: 3.3.1 (3.3.1)
Build Info: Aperture-251003000000000~6
App Item ID: 408981426
App External ID: 8854232
Code Type: X86-64 (Native)
Parent Process: launchd 
Date/Time: 2012-07-15 16:09:47.657 -0500
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /Library/Frameworks/NyxAudioAnalysis.framework/Versions/A/NyxAudioAnalysis
Referenced from: /Applications/Aperture.app/Contents/Frameworks/iLifeSlideshow.framework/Version s/A/Frameworks/iLifeSlideshowProducer.framework/Versions/A/iLifeSlideshowProduce r
Reason: image not found
Currently Being ModeratedJul 15, 2012 2:38 PM (in response to Localboy56)
Your crash report shows that your system library is corrupted and a framework is missing, the NyxAudioAnalysis framework. Did you install any new multimedia applications lately?
To fix your system library the best option would be to reinstall your operating system: I'd us the
Currently Being ModeratedJul 15, 2012 3:16 PM (in response to léonie)
OK Leonie, I found that only one item in the /Library/Frameworks folder: PluginManager.frameworks, nothing else!
Time Machine backup for 7/11/2012 Frameworks folder has 22 items in it including the NyxAudioAnalysis file. The Frameworks folder for 7/12/2012 has only the one item so something certainly happened on that date.
Shall I go ahead and trash the corrupted Library Frameworks folder currently in place and then restore it with the earler complete Frameworks folder using Time Machine?
Thanks very much for your help on this!
Currently Being ModeratedJul 15, 2012 3:19 PM (in response to Localboy56)
BTW - Earlier today I tried reinstalling OS 10.7.4 combo update and that did not correct the missing frameworks which apprently is causing the Aperture loading problem. Should the updater have done that?
Currently Being ModeratedJul 16, 2012 2:29 AM (in response to Localboy56)
Hmm. the Combo Update should restore the Libraries. If it did not do so, go ahead and restore from your Time Machine backup.
Maybe there is a problem with your system hard drive. It would not hurt to let Disk Utility check the file system.
Currently Being ModeratedJul 16, 2012 6:29 AM (in response to léonie)
Leonie - Sucess! Thank you, thank you , thank you!
It turns out the OS will not let you trash the Frameworks folder but you can restore the items within it so I had Time Machine replace everything including the PluginManager which was the only file there. Then rebooted and tried out Aperture and it opened my library quickly just the way it always used to. I don't think I lost any photos.
Still some mysteries to me how the frameworks were deleted back on 7/12/2012 and why the updater failed to reinstall them but at least I don't have to worry about accessing my photos any longer.
Thanks again for your help!
Currently Being ModeratedJul 16, 2012 6:38 AM (in response to Localboy56)
You are welcome.
Great, that you could get Aperture fixed and your pictures back.
Still some mysteries to me
I have never seen that particular framework missing. If you happen to remember something particular that happened at that day and might have changed the libraries - any installation, crash, please let us know. It is really peculiar, that the plug-in manager framework was the sole survivor. Usually this framework (and an installation of final cut) is the source of library trouble.
Currently Being ModeratedSep 3, 2012 2:02 AM (in response to Localboy56)
it sounds like this particular issue has been resolved but just in case others are looking for an answer and this does not work (like me until earlier today) See https://discussions.apple.com/thread/4147538
I found that by going to the System Preferences and logging out of MobileMe worked for me. Ive been using iCloud for a while but never thought I had to also log out of MobileMe on my non Mountain Lion Macs. I thought that as I was now using iCloud and MobileMe was finished there would be no need.
For some strange reason Aperture was affected by me being logged into MobileMe and once I logged out Aperture started normally.
Just a tip for anyone else still looking for an answer to Aperture not starting and you have already tried some of the other tips.
Currently Being ModeratedSep 14, 2012 8:28 AM (in response to Glenn Cogar)
Just wanted to say thanks for this. I have been struggling for weeks with a non-launching Aperture on my mid-2007Macbook which I cant update to Mountain Lion....
... signed out of MobileMe, and voila ... Aperture works!!!
So thank you very much for the post.