Aperture 3.3.1 update

I have installed aperture 3.3.1 update but aperture still freezes not responding and I have to force quit...anyone know what else i can do now?? i'm running mac os 10.7.4 this issue has just happened last week after a bunch of software updates

Has Aperture been running at all after the upgrade to 3.3.1?
Probably your library has some sort of corruption; use the Aperture Library First Aid Tools to rebuild the Aperture library, see this paragraph of the online manual how to do it:
Repairing and Rebuilding Your Aperture Library
Regards
Léonie

Similar Messages

HT4906 Both my iPhoto, Aperture and OX is update still having problem asking me to update my iPhoto.

Both my iPhoto, Aperture and OX is update still having problem asking me to update my iPhoto.

Make a temporary, backup copy (select the library and type Command+D) if you don't already have a currnet backup of the library and apply the two fixes below in order as needed:
Fix #1
Launch iPhoto with the Command+Option keys held down and rebuild the library.
Since only one option can be run at a time start with Option #1, followed by #3 and then #4 as needed.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
Download iPhoto Library Manager and launch.
Click on the Add Library button, navigate to your Home/Pictures folder and select your iPhoto Library folder.
Now that the library is listed in the left hand pane of iPLM, click on your library and go to the File ➙ Rebuild Library menu option
In the next window name the new library and select the location you want it to be placed.
Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments but not books, calendars or slideshows. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.
OT

Aperture 2.1.4 update will not load after Snow Leopard update

Has any one found the fix for aperture 2.1.4 update not loading after the installation of Snow Leopard. I to am also getting the alert "aperture 2.0 or later is required to install the update". I installed my copy of aperture 2.1 using the installer with no problems so the program is in the correct location. I've seen the posts related to this problem and it does not seem a fix has been found.

Just ran into this myself. I did check to see if there was a preference to delete under ~/Library/Preferences and one is not created since 2.1 is never actually launched. 2.1 is sitting in the root of Applications and hasn't been renamed, but the 2.1.4 update just doesn't detect that it is there and just gives the alert "Aperture 2.0 or later is required to install this update."

What's wrong with the Aperture 2.1.3 Update?

Hi,
I downloaded the Aperture 2.1.3 Update but am unable to update my existing Aperture 2.0.1 version. Whe I try to run the installer, I get the following message: "Aperture 2.0 or later is required to install this update."
Any suggestion or help is appreciated.

Hi,
I did, thanks for the link. I tried all that, nothing worked It's kind of frustrating to have the Aperture 2.0 version and not being able to update. The automatic Apple software update doesn't recognize the need for an update so I tried to do it manually. I never moved or renamed this application, it has been in the Applications folder from the beginning.
I don't have the time or energy to figure this out. It worked in the past with the 1.x.x version. I also tried with lower updates (2.1.x), same problem. Should I maybe de-install Aperture and try to install it again? Would that help?
Regards,
Igor

Unable to install Aperture 2.1.4 update on Snow Leopard

Hi Folks,
I have Aperture 2.1 installed on my Mac. When I try to install the 2.1.4 update, it quits by saying "Aperture 2.0 or later is required to install this update". And Snow Leopard wouldn't let me launch Aperture without this update. Has anyone else faced this issue? Any known workarounds?
This is a clean install of Snow Leopard and Aperture.
Also, Software Update doesn't show the Aperture 2.1.4 update either.
Thanks,
Deepak
p.s. As a workaround I am downloading the full 2.1.4 trial which I'll use with my retail serial.

I have been having the same difficulties since installing Snow Leopard. When I perform a "software update" Aperture updates are not listed. I manually downloaded the 2.1.4 update and was then unable to install it for the same reason as above; the original 2.1 version is not recognized as even existing on the computer.
Interestingly, I have the same issue with Safari. The program disappeared from my Mac Pro during the upgrade to Snow Leopard and when I downloaded the latest Safari program and tried to install it, the installer informed me that I had to have OS X v10.5.8 or newer in order to install this program; all partitions on the computer were indicated to be unsuitable for installation including the system (10.6.2) partition. This problem persists. So what gives?
Thanks for any help
Jon

Aperture won't allow update vault

since update to 10.8 I've been having problems with aperture like vault wont update(will freez up), dodge&burn tools not working right, overall performance slow. I trashed the app and reloaded seems somewhat better but my computer still freezes when trying to update vault ?

Hi johnmyself, cor-el has covered Flash. For the other two:
* Adobe ReaderAdobe PDF Plug-In For Firefox and Netscape - because Adobe doesn't support Reader XI on Vista, you're stuck with the Reader X series and corresponding plugin 10. Mozilla's plugin check site only considered the current plugin 11 series to be up-to-date, so you'll have to rely on Adobe to keep you on the latest Reader X and plugin 10. You can use Help > Check for Updates in Adobe Reader X to watch for updates.
* Adobe Flash PlayerRealNetworks(tm) RealDownloader PepperFlashVideoShim Plug-In - this is something supplied by RealDownloader and most likely would be updated when you update that software.

Aperture has not been updated to support new higher-resolution Facebook images

In August facebook changed the maximum dimensions of a photo from 720x720 to 960x960 (http://blog.facebook.com/blog.php?post=10150262684247131). Much like the last time they upped the resolution of photos on Facebook, Aperture didn't get updated to accomodate this change for months. As I understand this isn't some long gradual rollout -- all FB users can now use 960x960 images, and seeing as this is probably like one line of code to change, I'm just wondering if we'll be waiting months and months again to take advantage of this. In the meantime there's little reason to create FB albums through Aperture since you're forced to use lower resolution images.
Anyone know how to perhaps modify Aperture to make this change while we wait for a proper update?

Totally understand your first point. Some photographers want to protect their work. Thing is, some don't. It's just a hobby for me and I know I won't be making any money on it. People like me just want to put up the best version of a picture FB will allow us to. Perhaps Aperture should allow the user to CHOOSE the resolution of the image that gets uploaded.
Facebook has, for the past while (long before the 960x960 change in August) allowed users to "download" the image, typically at a much higher resolution than what is displayed. The difference is that up until August, images viewed on facebook only displayed at 700x700. Now that's been upped to 960x960.
Upon some re-testing I do have to eat my own foot. I just created a new FB album through Aperture and they are showing up as 960's instead of 700's. However all my older albums still show the images at 700x700 (something FB said would change automatically, since they technically already have much larger versions of these photos to resample to 960x960). It seems you have to force an update by editing the image so it gets reuploaded.
So in conclusion, foot has been inserted into mouth.... though it'd be nice if I could simply "re-sync" my older albums to have them display at 960 without having to fool aperture into reuploading the whole thing....

Should I download Aperture 3.6 compatibility update before or after downloading Yosemite?

I'm running Mavericks OS on my late 2009 MacBook.
I would like to download Yosemite but I'm worried about my photos on Aperture 3. Should I download the Aperture 3.6 compatibility update before or after downloading Yosemite.? Thanks.

I bought Aperture 3 from the App Store some time ago but got it updated regularly
Does that mean, you are now running Aperture 3.5.1? Then you should be seeing Aperture on the Purchases tab of the App Store and your Aperture license has been associated with your Apple ID.

When will Apple bring the urgently needed Aperture 3.4-Repair-Update?

After installing the Aperture-Update to Version 3.4 the App crashes unexpectedly by start and cannot restart after Database-Repair.
When will Apple bring the urgently needed Aperture 3.4-Repair-Update?

I am having the same problem. Here is the crash log.
rocess:         Aperture [2285]
Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier:      com.apple.Aperture
Version:         3.4 (3.4)
Build Info:      Aperture-301036000000000~1
Code Type:       X86-64 (Native)
Parent Process: launchd [179]
User ID:         504
Date/Time:       2012-09-22 21:43:52.503 -0500
OS Version:      Mac OS X 10.8.2 (12C54)
Report Version: 10
Interval Since Last Report:          153586 sec
Crashes Since Last Report:           11
Per-App Interval Since Last Report: 194 sec
Per-App Crashes Since Last Report:   10
Anonymous UUID:                      E2C0D557-6915-DF12-D27D-22B6575C8BF3
Crashed Thread: 3 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initWithScheme:host:path:]: path 1282424674 is not absolute.'
terminate called throwing an exception
abort() called
Application Specific Backtrace 1:
0   CoreFoundation                      0x00007fff919c90a6 __exceptionPreprocess + 198
1   libobjc.A.dylib                     0x00007fff975fc3f0 objc_exception_throw + 43
2   CoreFoundation                      0x00007fff919c8e7c +[NSException raise:format:] + 204
3   Foundation                          0x00007fff8c05ede8 -[NSURL(NSURL) initWithScheme:host:path:] + 112
4   PrintServices                       0x0000000105463c6d +[NSURL(ISNSURLExtensions) URLWithScheme:host:path:] + 61
5   PrintServices                       0x0000000105463bef -[NSURL(ISNSURLExtensions) URLByAppendingPathComponent:] + 127
6   FacebookPublisher                   0x0000000112ff27f2 -[ILFacebookAPIRequest graphURLRequest] + 215
7   FacebookPublisher                   0x0000000112ff2fb5 -[ILFacebookAPIRequest send] + 33
8   FacebookPublisher                   0x0000000112fe44da -[IPHFacebookPlugin displayNameForUsername:] + 88
9   AccountConfigurationPlugin          0x0000000104974fa5 -[AccountConfigurationProfileInformationDownloadOperation main] + 174
10 Foundation                          0x00007fff8c0b5986 -[__NSOperationInternal start] + 684
11 Foundation                          0x00007fff8c0bd1a1 __block_global_6 + 129
12 libdispatch.dylib                   0x00007fff91361f01 _dispatch_call_block_and_release + 15
13 libdispatch.dylib                   0x00007fff9135e0b6 _dispatch_client_callout + 8
14 libdispatch.dylib                   0x00007fff9135f1fa _dispatch_worker_thread2 + 304
15 libsystem_c.dylib                   0x00007fff963bbcab _pthread_wqthread + 404
16 libsystem_c.dylib                   0x00007fff963a6171 start_wqthread + 13
Thread 0:: Dispatch queue: com.apple.main-thread
0   com.apple.Foundation                    0x00007fff8c0a9087 NSKeyValuePropertyForIsaAndKeyPath + 1
1   com.apple.Foundation                    0x00007fff8c0a8ede -[NSObject(NSKeyValueObserverRegistration) addObserver:forKeyPath:options:context:] + 80
2   com.apple.Aperture                      0x00000001038ebea4 0x103601000 + 3059364
3   com.apple.Aperture                      0x00000001038edd9c 0x103601000 + 3067292
4   com.apple.Aperture                      0x00000001038edd31 0x103601000 + 3067185
5   com.apple.Aperture                      0x000000010388ce6b 0x103601000 + 2670187
6   com.apple.Aperture                      0x000000010388874a 0x103601000 + 2651978
7   com.apple.Aperture                      0x0000000103888cd3 0x103601000 + 2653395
8   com.apple.Aperture                      0x00000001038ca4ad 0x103601000 + 2921645
9   com.apple.Aperture                      0x000000010365cda5 0x103601000 + 376229
10 com.apple.CoreFoundation                0x00007fff9197b47a _CFXNotificationPost + 2554
11 com.apple.Foundation                    0x00007fff8c06f846 -[NSNotificationCenter postNotificationName:object:userInfo:] + 64
12 com.apple.AppKit                        0x00007fff96a8d60d -[NSApplication _postDidFinishNotification] + 292
13 com.apple.AppKit                        0x00007fff96a8d346 -[NSApplication _sendFinishLaunchingNotification] + 216
14 com.apple.AppKit                        0x00007fff96a8a532 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 566
15 com.apple.AppKit                        0x00007fff96a8a12c -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 351
16 com.apple.Foundation                    0x00007fff8c08912b -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 308
17 com.apple.Foundation                    0x00007fff8c088f8d _NSAppleEventManagerGenericHandler + 106
18 com.apple.AE                            0x00007fff94c50b48 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 307
19 com.apple.AE                            0x00007fff94c509a9 dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 37
20 com.apple.AE                            0x00007fff94c50869 aeProcessAppleEvent + 318
21 com.apple.HIToolbox                     0x00007fff91cf68e9 AEProcessAppleEvent + 100
22 com.apple.AppKit                        0x00007fff96a86916 _DPSNextEvent + 1456
23 com.apple.AppKit                        0x00007fff96a85ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
24 com.apple.Aperture                      0x0000000103a7500d 0x103601000 + 4669453
25 com.apple.AppKit                        0x00007fff96a7d283 -[NSApplication run] + 517
26 com.apple.prokit                        0x0000000104b16324 NSProApplicationMain + 378
27 com.apple.Aperture                      0x00000001036109c2 0x103601000 + 63938
28 com.apple.Aperture                      0x0000000103610314 0x103601000 + 62228
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib                  0x00007fff90a23d16 kevent + 10
1   libdispatch.dylib                       0x00007fff91360dea _dispatch_mgr_invoke + 883
2   libdispatch.dylib                       0x00007fff913609ee _dispatch_mgr_thread + 54
Thread 2:
0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
Thread 3 Crashed:: Dispatch queue: com.apple.root.default-priority
0   libsystem_kernel.dylib                  0x00007fff90a23212 __pthread_kill + 10
1   libsystem_c.dylib                       0x00007fff963baaf4 pthread_kill + 90
2   libsystem_c.dylib                       0x00007fff963fedce abort + 143
3   libc++abi.dylib                         0x00007fff8e97ca17 abort_message + 257
4   libc++abi.dylib                         0x00007fff8e97a3c6 default_terminate() + 28
5   libobjc.A.dylib                         0x00007fff975fc873 _objc_terminate() + 91
6   libc++.1.dylib                          0x00007fff915aa8fe std::terminate() + 20
7   libobjc.A.dylib                         0x00007fff975fc5de objc_terminate + 9
8   libdispatch.dylib                       0x00007fff9135e0ca _dispatch_client_callout + 28
9   libdispatch.dylib                       0x00007fff9135f1fa _dispatch_worker_thread2 + 304
10 libsystem_c.dylib                       0x00007fff963bbcab _pthread_wqthread + 404
11 libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
Thread 4:
0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
Thread 5:
0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
Thread 6:
0   libsystem_kernel.dylib                  0x00007fff90a236d6 __workq_kernreturn + 10
1   libsystem_c.dylib                       0x00007fff963bbeec _pthread_workq_return + 25
2   libsystem_c.dylib                       0x00007fff963bbcb3 _pthread_wqthread + 412
3   libsystem_c.dylib                       0x00007fff963a6171 start_wqthread + 13
Thread 7:
0   libsystem_kernel.dylib                  0x00007fff90a230fa __psynch_cvwait + 10
1   libsystem_c.dylib                       0x00007fff963bdfc3 _pthread_cond_wait + 927
2   com.apple.Foundation                    0x00007fff8c0e7933 -[NSCondition waitUntilDate:] + 357
3   com.apple.Foundation                    0x00007fff8c0e7789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4   com.apple.proxtcore                     0x00000001057ea03a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore                     0x00000001057e9282 -[XTThread run:] + 329
6   com.apple.Foundation                    0x00007fff8c0bc612 __NSThread__main__ + 1345
7   libsystem_c.dylib                       0x00007fff963b9742 _pthread_start + 327
8   libsystem_c.dylib                       0x00007fff963a6181 thread_start + 13
Thread 8:
0   libsystem_kernel.dylib                  0x00007fff90a230fa __psynch_cvwait + 10
1   libsystem_c.dylib                       0x00007fff963bdfc3 _pthread_cond_wait + 927
2   com.apple.Foundation                    0x00007fff8c0e7933 -[NSCondition waitUntilDate:] + 357
3   com.apple.Foundation                    0x00007fff8c0e7789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4   com.apple.proxtcore                     0x00000001057ea03a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore                     0x00000001057e9282 -[XTThread run:] + 329
6   com.apple.Foundation                    0x00007fff8c0bc612 __NSThread__main__ + 1345
7   libsystem_c.dylib                       0x00007fff963b9742 _pthread_start + 327
8   libsystem_c.dylib                       0x00007fff963a6181 thread_start + 13

Aperture Not Working After Updating to OS 10.10.3

I have updated to the latest version of the OS and my legitimate copy of Aperture has been inoperable since the update. Apple has sent an email to everyone with a registered copy of Aperture stating that it still will work after the update but that is not the case. I feel lied to and I have about 200,000 photos across 7 Aperture libraries and this new "Photos" app lacks the professional tools that I need. I was going to transition to other options but I didn't feel the need to right away since they said it would be fine.
Is there some update patch I am missing? I would like to think they didn't abandon the few of us that use it and love the program for what it was. (See images below.)

What is your current Aperture version?
Shortly before the Mac OS X 10.10.3 update, Apple released the compatibility update to Aperture 3.6., that you need to install.
If your current Aperture version is Aperture 3.5.1,Aperture should be showing at the AppStore on your Purchases tab. If you are seeing Aperture there, move your crossed out Aperture application from the Applications folder to the Trash (but do not empty the Trash).
Then try to download and install Aperture from the Purchases tab of the AppStore.

Aperture 3.4.5 - update from previous version not working

Hi, I have updated Aperture to 3.4.5 via the App Store update and now it won't startup correctly. I get this...
I started with Aperture 2 via disk install and then upgrade to V3 via the App store, all other updates have worked fine.
Any ideas guys?
I can use Time Macjine to go back a version and get things working again but this is preventing any further updates and enhancements from being applied.
Thanks.

In previous versions of Aperture it helped to trash it and to install it again from the App Store (don't empty the Trash), when Aperture was asking for the serial number.
I don't know, however, if it will still help with the new AP 3.5.

Aperture not working after update.

Hello,
I just updated to OS 10.7.5 and also updated to Aperture ver. 3.4 (auto-updater) and now Aperture won't open, it just crashes. I tried reinstalling, but it didn't help. Another app. Canon EOS Utility also stopped working, I also reinstalled this to no avail. I was using both of these programs yesturday with no problems.
Can Anyone help with this?
Thanks in advance.

Deleting the .plist file will not cause you to delete the program or any images.
Make sure you are looking for the .plist in your user library folder and not the system library folder...by default, the OS hides your user library folder from view...there are lots of ways to "unhide" it, but my preference is to do this: http://osxdaily.com/2011/07/04/show-library-directory-in-mac-os-x-lion/
This will unhide it permanently so that the next time there is some kind of problem you will be able to easily delete the offending preferences file.
Once you have done this, you can now go to ~/Library/Preferences/ and locate the com.apple.Aperture.plist file and delete it (where ~ represents your home folder, whatever you call it).
If this does not solve your problem, you can reinstall the application, which takes a lot more time.

Photo edits in aperture are not being updated in Photostream

I want to edit photos in iPhoto on an iPad mini and also in Aperture and have the changes synchronised either using photostream or a direct connection. Try as I may I can't get this to happen. If I move a photo in Aperture to the photostream then it appears on the iPad and vice versa. If I subsequently edit a photo on either device the changes are not propagated to the other device and the photostream image is not updated. Can anyone tell me what I am doing wrong, or is this feature simply not supported.

Photo Stream can be used to automatically share photos to other devices, but it will not sync the photos. If you edit photos and want to share the edited version as well, you will have to add this edited version again to the Photo Stream. Also the photos will not be stored in the Photo Stream for more than a month.
You might consider to use iTunes Photo sync instead:
iOS and iPod: Syncing photos using iTunes
With iTunes Photo Sync you can update the albums synced to your iPad, when you change the albums and edit the photos on your mac, but changes done on your iPad will also not sync back. You have to reimport the edited photos from your iPad.
There is simply no simple way yet to sync iPad and Mac, if you are looking for a solution to do some editing on your iPad and keep iPad and Mac in perfect sync.
Maybe some third party software can do that, but neither the Photos app nor iPhoto on iPad has means to do that.
Regards
Léonie

Aperture library does not update in iLife media browser

I had the following problem for over a YEAR now. The *photo browser* does not have current Aperture information available. I looked everywhere for a solution, including this forum and the support database. The proposed solutions were as follows:
1. Turn on iLife sharing and auto-preview creation in Preferences - DUH!
2. Turn off iLife sharing, restart Aperture, then turn it back on - DOES NOT WORK
3. Hold down Command-Option when starting Aperture and rebuild library - DOES NOT WORK
4. Trash ApertureData.xml file - DOES NOT WORK
5. Trash ApertureData.xml as well as Aperture.aplib folder - DOES NOT WORK
I'm sure there were a few more things I tried. I thought I'd ask a "genius" at the Apple store. I realized then (again) that that moniker is gravely misplaced.
The crux of the problem is that the ApertureData.xml is not kept up-to-date by Aperture. That XML file is used throughout the Mac to provide photo browser access and insertion of preview files into Mail, iLife, iWork and other supported programs. Why that file stopped updating is a mystery to me. Some people suggest it has to do with the upgrade from 1.5 to 2.
For all those super-frustrated Aperture users who have had the same issue and cannot fix it using any of the above methods, here's ultimately what I had to do to fix this.
1. Export every one of your projects
2. Create a new Aperture library
3. Import all projects into the new library
The only items that do not transfer are the ones situated at the root level of the library. Those will have to be recreated manually. Since I only had a few smart folders there, it did not affect me gravely. The keyword list should also be created when you create the new library. If not, look for Keywords.plist in the old Aperture.aplib folder.
I spent literally WEEKS looking for this solution, it is nowhere to be found. I cannot be the only one running into that problem. I'd be curious to know if there are others out there with the same problem.
Thanks!

Wow, this is not encouraging. I have a slightly different version of this problem. I had my Aperture library showing up (and updating as I expanded it) in the Media Browser, and all was well until I bought a new Mac and transferred everything over from the old one. For whatever reason, not everything makes it over. Now, on the new Mac, my Media Browser only shows images from Photo Booth--not even iPhoto! I feel your pain and share your ire.
Someone mentioned September (not coming soon enough). Is there speculation that Aperture will be updated (finally!) when Snow Leopard releases?

Aperture 3 failing to update your Aperture 2 library? Please read!

Hello all,
This is for those who are not running the trial version - the trial version CANNOT upgrade an existing library.
Like many others here I ran into a snag when upgrading my Aperture 2 library with Aperture 3. I kept getting "Warning: Update Failed" box immediately after choosing to upgrade the library for the new features in A3 (I tried with the box checked and unchecked). I rebuilt and did a permissions fix using A2 (holding down Option + Command while launching A2) but still no avail. I checked the library file itself to see if I (username for my OS X account) had read & write privileges - I did. I even tried to re-install A3 to see if that would fix anything - it didn't.
I keep my library on an external hard drive in a folder called "pictures". Within this folder are both my Aperture and iPhoto libraries. I then thought to check to see if I (username for my OS X account) had read & write privileges for the "pictures" folder and was partially relieved to see that I didn't. I changed that and A3 started the update/upgrading procedures.
So, if anyone else out there is experiencing this same problem check to make sure you have read & write privileges along the entire path to your Aperture library.
Please note, me not having these privileges on my "pictures" folder did not affect A2 in any way (I could launch my library without any issues), just A3.
Cheers.

Quit Aperture and double-click the library you want upgraded. Aperture will open and upgrade it. Once you've upgraded it you can import it into your other library.

Aperture 3.3.1 update

Similar Messages

Maybe you are looking for