Aperture Library Repair fail

Hello,
I have Aperture 3, a 250GB Aperture Library and it faqiled to load this evening, just hung. I reapired permissions, tried to clean up the database and rebuild the database, none of which would run.I can find the library, look inside and see that the files are there in the folders. Aperture wont load it as the repair failed and was interrupted. Tried repair but the program bombs out.
Am scratching my head what to do?
Is there an external repair program that i can run over it? Aperture crashes out.
Bummed
martyn

I too am having difficulty with Aperture permissions.  This permission problem has plagued me for the last year.  Permissions will not verify using disk utility (Version 13) and disk utility fails to complete the repair after 7 minutes.  Now my Aperture drive with all my libraries will not mount.  The error message says to copy all files and reformat.  How do you do this if disk utility will not mount the drive?
Here is the error log (or part of it).
Checking file systemChecking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Overlapped extent allocation (id = 22557, /New Gourds.aplibrary/Database/apdb/Properties.apdb)
Overlapped extent allocation (id = 22559, /New Gourds.aplibrary/Database/apdb/History.apdb)
Overlapped extent allocation (id = 22561, /New Gourds.aplibrary/Database/apdb/ImageProxies.apdb)
Overlapped extent allocation (id = 97730, /New Gourds.aplibrary/Database/History/Changes/0000000007.plist)
Overlapped extent allocation (id = 205763, /New Glass.aplibrary/Database/History/Changes/0000000015.plist)
Overlapped extent allocation (id = 265087, /Animals.aplibrary/Database/Folders/2cA6IPVGRQWfleHtAEgKTA.apfolder)
Overlapped extent allocation (id = 265091, /Animals.aplibrary/Database/Folders/LibraryFolder.apfolder)
Overlapped extent allocation (id = 265111, /Animals.aplibrary/Database/Keywords.plist)
Overlapped extent allocation (id = 265112, /Animals.aplibrary/Database/KeywordSets.plist)
Overlapped extent allocation (id = 265407, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/+LVQTNHBRaCtWOv 95yR39w/Master.apmaster)
Overlapped extent allocation (id = 265411, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/14HtlPA+T1aImjS 7wtCUNg/Master.apmaster)
Overlapped extent allocation (id = 265415, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/2UWUfVXYSQ+0K+r shNjv3A/Master.apmaster)
Overlapped extent allocation (id = 265419, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/2YKGiQ7mR2GQ5BC +SOm89A/Master.apmaster)
Overlapped extent allocation (id = 265423, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/9UHl3mP5Ri+d2PJ cnTQRmg/Master.apmaster)
Overlapped extent allocation (id = 265427, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/Bhk9e7tsSxu+6l% V4zSD+A/Master.apmaster)
Overlapped extent allocation (id = 265431, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/bWOPURt%TpiCBVb nQhWU8Q/Master.apmaster)
Overlapped extent allocation (id = 265435, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/dm%PJaCIQQqjNyH nnyNM3g/Master.apmaster)
Overlapped extent allocation (id = 265439, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/DyXBQZDmR5+DQEE DOElFcA/Master.apmaster)
Overlapped extent allocation (id = 265443, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/EvzjT7ydSKOC5ST TYZP+uQ/Master.apmaster)
Overlapped extent allocation (id = 265447, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/FVPB8mRwTQGhAnD EkARVJA/Master.apmaster)
Overlapped extent allocation (id = 265451, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/gdcUiUH%TaucwaI DImghGA/Master.apmaster)
Overlapped extent allocation (id = 265455, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/iCkjZj7%TViUZNN XaYX0SA/Master.apmaster)
Overlapped extent allocation (id = 265459, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/iPM6IjyqTYaCCg5 CE7Kkkw/Master.apmaster)
Overlapped extent allocation (id = 265463, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/j3cQYZsGROqrMbd jCw5%9A/Master.apmaster)
Overlapped extent allocation (id = 265467, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/JeuoBg1gQaiV%fx eqPnecQ/Master.apmaster)
Overlapped extent allocation (id = 265471, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/OfZo08RDQ7G385% djcL8hA/Master.apmaster)
Overlapped extent allocation (id = 265475, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/PgGjSNauTIige5g 2xVjeyQ/Master.apmaster)
Overlapped extent allocation (id = 265479, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/QDcWGGqGS+6iLcZ 2O5DdHg/Master.apmaster)
Overlapped extent allocation (id = 265483, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/QfXjLbLPQba+01B 2AgRx0Q/Master.apmaster)
Overlapped extent allocation (id = 265487, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/qhTp5T+uSgGQ1Rt oleVzOQ/Master.apmaster)
Overlapped extent allocation (id = 265491, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/rBOq8LneQf2U%hq LsZnLRg/Master.apmaster)
Overlapped extent allocation (id = 265495, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/swTTA4JESlSqQnY dKNSskg/Master.apmaster)
Overlapped extent allocation (id = 265499, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/UJc5KU4bRE2YHZk pTPR%nw/Master.apmaster)
Overlapped extent allocation (id = 265503, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XA9m7ihER5eCibU glGskRg/Master.apmaster)
Overlapped extent allocation (id = 265507, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/xaM%4EGmQJqZqBn 1kEyL4g/Master.apmaster)
Overlapped extent allocation (id = 265511, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XaS35pzIQZOsDcx wp2GtYw/Master.apmaster)
Overlapped extent allocation (id = 265515, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/xl0svn8rRqGj8OR m3PxzCA/Master.apmaster)
Overlapped extent allocation (id = 265519, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XLqfC6DBT42E78d jsimuWg/Master.apmaster)
Overlapped extent allocation (id = 265523, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/XY8Iji95SVmYwHb vEaV5zg/Master.apmaster)
Overlapped extent allocation (id = 265527, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192826/ZYuDDLvxSuCUQM9 LqdVvXw/Master.apmaster)
Overlapped extent allocation (id = 265532, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/8oVOfqYkTb6C7pD q2oC+hg/Master.apmaster)
Overlapped extent allocation (id = 265536, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/bjiSlJKfTIC1lKn yVfw2fg/Master.apmaster)
Overlapped extent allocation (id = 265540, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/eNFQWAojS5WU2mH 5nCf3ZQ/Master.apmaster)
Overlapped extent allocation (id = 265544, /Animals.aplibrary/Database/Versions/2012/10/07/20121007-192924/HRfBGx5uTIOmCfC rshGvjA/Master.apmaster)
Overlapped extent allocation (id = 265824, /Animals.aplibrary/Info.plist)
Overlapped extent allocation (id = 1017926, /New Gourds.aplibrary/Thumbnails/Segments/Thumb64Segment_1.data)
Overlapped extent allocation (id = 1018813, /New Gourds.aplibrary/Database/Albums/Photostream-286385529.apalbum)
Overlapped extent allocation (id = 1019907, /New Gourds.aplibrary/Database/Versions/2013/05/29/20130529-183722/xyYiYDhwRfmAHoELa wk9wg/Version-1.apversion)
Overlapped extent allocation (id = 1019908, /New Gourds.aplibrary/Database/Versions/2013/05/29/20130529-183722/9NwRiNv5SB+rRA8kS Xq5pQ/Version-1.apversion)
Anyone have any ideas?
Mayte it is time to switch to Lightroom?

Similar Messages

  • Error when upgrading Aperture library on an external drive

    I have a MacBook Pro and am in the process of upgrading to Aperture 3. When Aperture wants to upgrade the existing Aperture library, it fails saying that there is insufficient memory. (My hard drive is very full). I have copied the Aperture library across to a WD external drive and have held down "Option" key when launching Aperture 3 so that I could select the library on the external drive as the preferred library. That went ok. Then when Aperture 3 was some way through upgrading the library on the external drive, it suddenly stopped and gave me this message.
    "There was an error creating a library at the path “/Volumes/External Drive/Aperture Library.aplibrary”. The library could not be created because the file system of the destination volume is unsupported."
    The library also seems to have disappeared off the external drive.
    Any ideas on what I did wrong?

    Hi Paul DT;
    In addition to the suggestions that Allen gave you I would also suggest that once you increase the free space on your internal disk drive that you reboot with install DVD and repair the disk using Disk Utility.
    When you run the free space down that can greatly increase the chances of corrupting the directory on that disk. If you have any corruption in the directory that cause all kinds of strange problems for you until you repair it.
    Allan

  • Problem syncing photos to iPad from Aperture with a merged iPhoto/Aperture library

    I recently 'upgraded' to us Aperture instead of iPhoto. One of the features of this was that I could continue to use the old iPhoto library in Aperture, and it automatically configures to Aperture settings - and it works great in Aperture.
    The problem is that when I come to sync photos to my ipad, I have the drop down options for iPhoto and Aperture. The Aperture option shows zero photos, and the iPhoto option shows all the complete list of all my photo event/projects (from both my iPhoto days, and the more recent stuff in Aperture); but anything that I have created since moving to Aperture is greyed out and not accessible.
    Any clues as to how I can sync the new photos as well as the old ones?
    Thanks

    Have you enabled the sharing and creation of previews in Aperture? That is one big difference between Aperture and iPhoto - in iPhoto it is impossible to disable previews, but in Aperture you can create previews selectively, see: Working with Preview Images
    Check Aperture's Preferences > Previews settings for "New Projects automatically create Previews".
    Then select the images with missing previews in Aperture in the Browser and use the command "Photos > Update previews".
    If that is not the problem, the iPod Photo Cache or the Aperture library may need repairing or rebuilding, see these documents on how to repair the Aperture Library:
    Repairing and Rebuilding Your Aperture Library
    iTunes: Understanding the iPod Photo Cache folder
    First try, if a simple repair of the Aperture library will suffice, then delete the iPod photo cache folder. Make sure, that the backup of your Aperture library is current, before try any of this.
    -- Léonie

  • My Aperture library is 300GB!!!!

    My Aperture library is 300GB but I have referenced all 27,000 of my images on another hard drive which is 300GB.  Why is this?  I went in and found 2,000 images that are not referenced using smart album, but that should not be why.  I also went in and adjusted the previews to be just the pixels of my screen. What do I do?
    Brandon

    There is about 70GB accountable and still wondering what is the other 100GB that makes up the rest of my library!
    Display the contents of the library sorted by size - best in list view. Then you should be able to spot the largest items. Like this:
    Or check with Omni Disk Sweeper, as Kirby recommended.
    Thanks Kirby for your suggestion: moving my entire library. This might be the best option but that sounds even more daunting...
    How do I do this when all my masters are already on an external drive?
    Moving the entire library is just an drag-and-drop.
    Get yourself an external drive.
    Conect it to your mac and check the formatting of the drive - it should be formatted for MacOS X Extentended (Journaled).
    Reformat the drive with Disk Utility if necessary.
    Repair your Aperture library (Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual)
    Then drag it to the external drive and test.
    If you want to include the referenced original again, use the command "File >Consolidate).
    Can I easily create a backup on another disk of an entire library?
    If you consolidate the library, so that it includes all referenced files, you can drag a copy to your backup drive.
    Or include the drive with the library in your regular Time Machine backup.

  • Copying aperture library from one external disk to another fails with error -36

    I am trying to duplicate my aperture library (449 GB) from one external hard disk to another. I get an -36 error and the copying fails before 1 GB is copied. I have repaired permissions and repaired my aperture library and have repaired both the source and destination disks. I am using a MB Air with a 256 GB HD (155 GB free) to perform the copy operation. Any help will be appreciated.
    Thanks!

    Rahul,
    I have also used the Aperture First Aid to repair the perminssions and the library (just the first two options out of three provided).
    What else can I do?
    Sorry, I overlooked that you already had done the repair options.
    To prevent permission issues, I'd enable the "Ignore Ownership" flag on both drives, if you have not already done so.
    Your copy-problem may be caused by a bad media file in your library.
    You could try to copy in small installments.
    Open the Aperture library package in the Finder by ctrl-clicking (right clicking) the Aperture library.
    You will see a Finder window with folders like Masters, Previews, etc.
    Create an empty folder on your new drive, name it something like ApertureLibraryBackup and drag the items from your current Aperture library on by one to this new folder.
    When the copy fails, e.g. for the Masters folder, check, how much could be copied. The first file, that not could be transferred, is probably the bad image or video.
    Delete this file from your Aperture LIbrary (using Aperture) and then try to copy the rest.
    Post back, when you discover what cannot be copied.
    Regards
    Léonie
    P.S.
    You enable the "Ignore Ownership" flag from the "File > Get Info" panel of the drive.

  • Time Machine Suddenly Failing Caused By Aperture Library

    Starting about 3 days ago - my ever-faithful Time Machine backups started failing. The error was concerning running out of disk space. Ilet it try several more times and it failed every time. I started doing some research at this great resource http://pondini.org/TM/Troubleshooting.html and tried several things from the suggestions:
    1. Disk Utility repair
    2. Spotlight Re-index
    3. Manually deleting the "inprogress"
    4. Manually deleting a few older backups.
    None of them worked. Looking at the logs I could see it was choking on the Aperture library. I fired up Aperture and let it do it's thing - hoping it would repair whatever issue it had. Tried backing up again. Still  the same error.
    Next up - I excluded the Aperture Library from the Time Machine backups - and BOOM.... successful backup.
    My only problem now though is I REALLY want that Aperture library backed up  to Time Machine,
    Does anyone have any suggestions for fixing this issue?
    - thx

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Cannot repair Aperture Library, "which library do you want to use"

    When I open Aperture and hold down the option key I keep getting prompted for "which library do you want to use"
    and it lists my current library and two backup with a , .BAK extension on two different disks.
    So I cannot get to the repair options, I only get  "which library do you want to use".
    How can I get to the repair options?
    much appreciated.

    You need to press the key combination options-command to launch into the Library First Aid Tools:
    Hold down the options key ⌥ and the command key  ⌘ at the same time, while launching Aperture. And keep the keys held down firmly, until you are seeing the Library First Aid panel. Then select "Repair Library" from the panel.
    If you only hold  down the options key  ⌥, you will launch into the Library chooser panel to switch between libraries.
    What is the reason, that you need to repair the Aperture library?

  • Failed to obtain image version information from Aperture library

    Mac OS X 10.10.1 (yes, Yosemite...)
    Aperture 3.6
    Lightroom 5.7,1 (CC version)
    When trying to import some libraries from aperture I get this immediate response "Failed to obtain image version information from Aperture library".
    In the plug-in import window, Number of image/video files is "undetermined", as well as Disk space required.
    Tried with different Aperture libraries, but with the same negative result.
    The plug-in worked in previous Lightroom version or when it was a stand alone plug-in.
    Thnak you
    Stefano

    OK, here is the workaround I did to migrate all my images.
    1. I broke down my Aperture library into separate libraries based on year (highlight all the 2014 projects, for example, right click, and "export to library")
    2. Import each separate library into Lightroom, one at a time.
    3. Delete the year-based libraries - and leave your original library on the drive (in case you need it in the future).
    I found I had one project in my 2013 photos which was causing Lightroom's scan of my database to fail. So I ended up creating metadata riders for that one project and imported it after I got the rest of my images imported.

  • Hi, I have an issue with my Aperture, I recently had a Samsung HD with 225 gb Aperture library fail. As per the instructions I moved the library to a new hard drive, in this case a 2tb Time Capsule. Now Aperture opens but no pictures

    Hi, I had a Samsung 1tb hard drive fail with a 225gb Aperture library on it, as per onscreen instructions I transferred the library to another hard drive in this case a 2tb Time Capsule. Now when I open the Aperture library I see the file structure and the white outline of the photos but no photos. When I try to export photo I get a pop up saying, 'selected master version offline'. The metadata is showing the photo details and size but no pic, and the aperture library is still showing it as 225gb
    If anyone has any suggestions or a way of finding the master files I would deeply appreciate it.
    Many thanks

    When a drive reports failed the data on that drive should be suspected to be corrupt. Initially one should assume any copies made of data after the drive starts reporting failing will also be corrupt.
    After a drive reports failure:
    When a drive reports to be failing our first concern should be the integrity of the existing backup of the data on that drive. It is easy to manage to corrupt the backup data during efforts to retrieve the failing-drive data.
    Step one should be to back up the back up of the failed drive. The known-good backups should be carefully quarantined from the likely-corrupt data.
    Step two (which should only happen after step one is complete and verified) is to make post-drive-failure copies of data from the failing HDD and make efforts to verify the accuracy of the data copied from the failed drive.
    Before a drive reports failure:
    Originals from the camera card should be separately backed up prior to import into Aperture or any other images management application. Always.
    HTH
    -Allen

  • Repair aperture library

    In trying to use aperture, I get repeated  "inconsistencies in library, repair". How do I correct this problem?

    Back up your Aperture Library and try the "Aperture Library First Aid Tools" as described here:
    Aperture 3: Troubleshooting Basics: http://support.apple.com/kb/HT3805
    Press and hold the Option and Command keys as you start Aperture. The Aperture Library First Aid dialog will appear and offer the three troubleshooting options - "Repair Permissions", "Repair Database", "Rebuild Database".
    Try all three options in turn, starting with the "Repair Permissions". Post back, if this does not solve the problem.
    If you cannot get to the "Aperture Library First Aid Tools" while launching Aperture with " Option and Command keys", select the Aperture Library in the Finder, and firmly hold down the Option and Command keys, while double clicking the Library.
    Regards
    Léonie

  • Two user accounts sharing aperture library constantly repairing permissions

    My girlfriend and I each have a user account on our iMac.  We have our Photo Library in a shared folder so we can both access it when using Aperture.  However, every time I want to use Aperture, I have to first repair permissions.  After doing this, everything runs fine. 
    Then, when my girlfriend tries to access Aperture, SHE has got to repair permissions first or Aperture gets hung up. 
    Basically, it appears that when I repair permissions in my user account, it messes up the permissions in her user account and vice versa.  Has anyone ever experienced this behavior before and have they found a solution?
    Thanks,
    Rick

    It is not sufficient to have the library in a shared folder. That will not help with the permissions inside the Aperture library package.
    The safest way to use an Aperture library from two differnet accounts is to move it to a disk or disk partition that has the "Ignore Ownership on this volume" flag enabled. Then you can take turns  using the Aperture library from your accounts.
    The procedure is explained in this document for an iPhoto library, but it work also for an Aperture library.
    iPhoto: Sharing libraries among multiple users http://support.apple.com/kb/HT1198
    Just remember, that any disk you are using for an Aperture library will have to be formatted for Mac:
    MacOS Extented (Journaled).
    My media drive with the Aperture library looks like this in "File > Get Info":

  • Restoring Aperture Library from Vault

    Hi all,
    I hope someone can help.  I recently had my 'Drobo' die on me as two discs failed at the same time.  I also have a copy of my Aperture Library backed up in a Vault.  I have carried out a 'Restore from Vault' and my new  external HD shows 1.5TB of data (same as my original library).  When I open Aperture, I can see all my folders and projects, but each project has no photos in it.  I have tried repairing the database and rebuilding the database using the option key on start up, but I repeatedly get to approx 83-89% complete and my system hangs and I get a message that I have run out of applications memory.  I then get the Spinning wheel and eventually have to reboot the iMac.
    1. How can I recover my data?
    2. Is there anything else I can/should do? Am I doing anything wrong?
    3. Is there anyway of recvering the files seperately of the external hard drive with other data recovery software?
    I am running Aperture the most uptodate version of Aperture 3.4.x, on OS X Mavericks, on a 3.4GHz i7 iMac with 12GB ram.
    One point I may need to add, I was backing up to Vault when my 'Drobo' unit failed, although based on the size of the vault, I think it had finished backing up, although can not be certain.
    Any help/assistance or advice would be greatfully received as I have lost my library, its parity due to two failed drives simultaneously and possibly a corrupt vault(?).
    Thank you in advance for your help.
    Paul W

    Will rebuilding the library place the images into their correct projects/folders?
    Will rebuilding return the images to their edited version state?
    This library is the restored library from your vault, correct? 
    What seems to be missing are all of the 'version' images processed in Aperture.
    In what way "missing"? Are all your projects empty or are you seeing broken thumbnails of the missing images in the projects?
    I am afraid, rebuilding will not be able to reconnect the "recovered" originals to the versions. The images are in the "Recovered" project, because Aperture does not know the link to the version.
    If your missing versions are still showing thumbnails, however correpted, you could use the lift&stamp tool to transfer the adjustments from the unusuable versions to the recovered versions.
    But that would be a bit daunting for 14000 recovered originals.
    I'd try something different - quick and dirty emergency measure: Try to open your vault directly on the drive where it is now without restoring it.
    Keep the restored library you are now having save and don't delete it.
    Change the filename extension of your vault to ".aplibrary", this will turn the vault into an Aperture library and try to open it directly in Aperture by double clicking it. This needs to be done in-place, on the Drobo-attached drive where you originally created the vault. Do not move it.
    Aperture will now try to open the vault as the current Aperture library and upgrade it. There is a slim chance, that the links between originals and versions will remain intact, if the vault is not restored to a different volume but repaired in-place on the original volume.
    Frank, what do you think? Should Snurge first try to repair the permissions on the drive?
    -- Léonie

  • There was an error opening the database for the library "/Volumes/Aperture Master/Unknown/Aperture Pictures/Aperture Library.aplibrary".    what do I do now?

    There was an error opening the database for the library “/Volumes/Aperture Master/Unknown/Aperture Pictures/Aperture Library.aplibrary”.
    What do I do now.  I cant access the photos on the drive.  The only option is Quit?  what ??????????
    Please help ready to throw computer and drive out the window.  I have a deadline of next Tuesdaythe 11th.

    Start Aperture while holding down the option and command keys. You'll get a Photo Library First Aid dialog as below.
    Try Repair Database first. If that doesn't work, then redo the startup with option-command and try Rebuild Database. These repair processes can take a long time with a larger library.
    If all that fails, you can try creating a new library from scratch and then try importing the old library into the new. This sometimes can fix problems that can't be repaired the First Aid way.
    Also make sure the drive where the Aperture library is located is working properly. You can check it with Disk Utility app.

  • Trying to open Aperture, but I get the message, "There was an error opening the database for the library "/Users/davewasson/Pictures/Aperture Library.aplibrary". - and it forces me to quit. What do I do?

    Trying to open Aperture, but I get the message, "There was an error opening the database for the library “/Users/davewasson/Pictures/Aperture Library.aplibrary”. - and it forces me to quit. What do I do?

    Dave-
    You can try opening the old (problem) library by launching Aperture into Library First Aid mode and choosing to Repair (first option) or Rebuild the library. Before doing this, make a backup copy of the old library, since both Repair or Rebuild will write changes to the library database.
    Repair is the faster and less drastic option, so try that first: After backing up your library, hold down both the Option and Command keys while dragging and dropping the problem library on the Aperture icon. The Photo Library First Aid window appears. Select Repair Database, then click Repair. After some time Aperture should open the library, if possible.
    If that fails launch Aperture back into Library First Aid and select Rebuild Database. Depending on the size of your library this operation could take some time, up to several hours for a very large library. When the main window appears you may have some extra Recovered folders/projects. This operation rebuilds the library from scratch and is usually successful at reviving problem libraries.

  • Aperture library suddenly won't open

    OK, I've been putting off updating to the latest version of Aperture (3.4.3) because I had a sort of premonition about something bad happening to my library. But I finally got around to doing the upgrade, having felt this version had been around long enough to be stable. Big mistake. It worked OK initially, but suddenly today won't open my library, no matter what I do.
    When I launch Aperture, it opens a little window with a spinning marker in it and the message "Opening Aperture Library". This is normal prior to the main window opening, but usually I see it for no more than a second or so. Now, it's all I see; the main window never appears.
    Oddly, Apertur's menu structure seems to work OK while this 'loading' window is open. I can, for example, open the Activity window. However, it contains no useful information to say what's going on; the entries are just blank in this window. Also, I can quit Aperture normally (whereupon it says 'updating previews' as usual).
    I've tried all three of the database-reparing options that Aperture offers if you hold down Option-Command when starting: repair permissions, repair database, rebuild database. In all three cases, it goes through the repair process and then just reverts to showing the little 'opening library' window and nothing has improved.
    The upgrade to version 3.4.3 apparently went OK the other day, and I've opened and quit the software a few times since I upgraded it, and I thought everything was fine. The one thing that wasn't quite right (and I wonder if this has somethnig to do with my problem now) was Photo Stream. It didn't seem to be working properly. If I clicked the Photo Stream entry in the list at the left of the window, what I saw was just the 'welcome' message with buttons below it to sign in or turn off the service ("No, thanks" button). I didn't see any actual Photo Stream content. In this window, however, it *did* say that I was signed in with my usual Apple ID, so it wasn't very clear to me whether it was OK or not.
    There's a photo I took on my iPhone which I was expecting Aperture 3.4.3 to download from Photo Stream, but it never did. I.e. just one shot that failed to download; all the previous ones had been downloaded by my previous version of Aperture. I couldn't see why the missing picture was failing to download, so I tried turning Photo Stream off and on again from within Aperture. I'm really not sure whether this worked or not; there didn't seem to be any meaningful feedback from the software.
    Anyway, after having tried to launch Aperture today (and failed), I checked System Preferences and found that Photo Stream was turned off. So I turned it on again. Unfortunately it makes no difference: Aperture still won't load its library at all now.
    I have tried all of following:
    1. Rebooting my Mac
    2. Verifying the disk contaning my Aperture library (it was fine)
    3. All three of Aperture's database-repair options
    4. Turning Photo Stream on in System Preferences
    ...and nothing makes any difference. Aperture simply will not open my library but just sits there, twiddling its spinner.
    NB My library still appears to be OK, in that I can access its contents from other software successfully using the media browser.
    What I haven't yet attempted is to create a blank new library and import my existing library into it. Failing any better ideas I'll try that next, but it's going to be a big operation that will take a lot of time and disk space, so I'd like to see if there are any better things to try first.
    I must say I'm very disappointed that Aperture can apparently break so easily. I haven't lost any actual pictures because I'm paranoid and keep a separate copy of all my shots just in the Finder, external to any management software. But I've lost access to lots of photo books I've created over the years and various other resources, not to mention all the editing work I've done on thousands of shots within Aperture (which I haven't retained separately).
    This is supposed to be professional level software. How can it seriously (a) break this easily and (b) not be able to retrieve itself via its database repair options?I'm very disappointed.

    Thanks for that very helpful reply. I've followed your instructions and done some further digging too.
    To answer your three points, first of all:
    1. No, I haven't imported any images since upgrading my Aperture library for version 4.3.4; I did move photos between projects a couple of times, but mostly I just checked that everything appeared OK after the upgrade and tried to work out why PhotoStream didn't seem to be working properly.
    2. I've attempted to create a new Aperture library. This didn't work! A library gets created on disk, but attempting to open it produces the same endless spinner as the main library.
    3. I switched to a spare user account (a blank one called 'test', just as the system created it) and tried to launch Aperture and create a new library there. Same result: library is created but won't load in.
    This is very strange, because I'm not aware of having changed anything substantial on my system recently. No new software that installed anything as a login item, system service or background process etc. that I'm aware of. (I'm actually quite wary of such software, and don't have much of it on my system.) The only substantial thing that I know has changed since I last successfully launched Aperture is the year, to 2013! And I hardly think that's the cause...!
    I'm wondering if Aperture itself has become corrupted somehow, and whether I should trash it and reinstall it. But that's rather a pain because I've got the DVD version, not the one from the Mac App Store. Besides, I'm not sure what remnants it leaves on the system (sandbox files etc.).
    I've verified my startup disk, on which Aperture resides, and repaired permissions, and no error was reported (nor did many permissions need to be fixed).
    Now, the only other possible explanation I can come up with is that startup is being prevented by a misbehaving PhotoStream process, as I've just discovered that I'm having endless crashes from PhotoStreamAgent, as reported in Console. I'm getting the same series of messages popping up every few seconds:
    01/01/2013 21:58:51.649 xpcd[4676]: PhotoStreamAgent[5540]: registration request failed: (0x11, 0x0) The file “com.apple.iLifeAssetManagement.agent.plist” couldn’t be saved in the folder “Preferences” because a file with the same name already exists.
    01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent[5540]) Job appears to have crashed: Illegal instruction: 4
    01/01/2013 21:58:52.431 com.apple.launchd.peruser.501[473]: (com.apple.photostream-agent) Throttling respawn: Will start in 10 seconds
    01/01/2013 21:58:52.615 ReportCrash[5531]: Saved crash report for PhotoStreamAgent[5540] version 2.7 (40.34) to /Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent_2013-01-01-2158 52_Richard-Hallass-Mac-Pro.crash
    01/01/2013 21:58:52.620 ReportCrash[5531]: Removing excessive log: file://localhost/Users/rghallas/Library/Logs/DiagnosticReports/PhotoStreamAgent _2013-01-01-215516_Richard-Hallass-Mac-Pro.crash
    This is just repeating every 10 seconds, as suggested by the 'Will start in 10 seconds' message. Starts; crashes; loop.
    Now, I've searched for a file called "com.apple.iLifeAssetManagement.agent.plist" and have found three instances: one each in the following places:
    Aperture:
    /Users/rghallas/Library/Containers/com.apple.Aperture/Data/Library/Preferences/c om.apple.iLifeAssetManagement.agent.plist
    PhotoStream Agent:
    /Users/rghallas/Library/Containers/com.apple.photostream-agent/Data/Library/Pref erences/com.apple.iLifeAssetManagement.agent.plist
    iPhoto:
    /Users/rghallas/Library/Containers/com.apple.iPhoto/Data/Library/Preferences/com .apple.iLifeAssetManagement.agent.plist
    In all three cases, the file appears to be an alias that points to itself (i.e. original path is the same as the alias's path in each case). That seems weird but I hope it's right, given that it applies to all three (and the files alongside these plists in the folders in which they reside).
    Anyway, the logs unfortunately don't make it clear exactly *which* Preferences folder is being referred to, and hence which com.apple.iLifeAssetManagement.agent.plist file is causing a problem. I imagine it's the one associated with PhotoStream Agent, since it's the Agent that's producing the ongoing crash reports. But either way I don't know what to do about it. I suppose I could try trashing this particular plist file, but I'm reluctant to do so as I don't want to break anything further.
    NB Aperture itself doesn't appear to output any log messages to say what's happening while it's failing to load its library.

Maybe you are looking for