Aperture 3.0.2 Opening Problem

When I try to open Aperture 3.0.2 I get a Warning window stating "There was an error opening the database for the library "/Volumes/Drive 3/Aperture Library.aplibrary" with the only option being to Quit. This is a new problem-Aperture 2 versions worked fine and Aperture 3 worked for the first few 'boots' and then this started. If I open Keynote and search the Aperture Library everything is there. I have reinstalled 3 and done the updates to 3.0.2 since this started and still no luck in getting into Aperture.

Gerry - have you tried to run any 'Aperture Library First Aid'?
If not, give the three steps listed in the [Troubleshooting Basics|http://support.apple.com/kb/HT3805|Aperture 3: Troubleshooting Basics] article a shot.
Regards,
Gary

Similar Messages

  • My aperture library will not open after restoring my whole computer after a kernal panic.  I can not get the Aperture troubleshooting menu to open...any help?

    My aperture library will not open after restoring my whole computer after a kernal panic.  I can not get the Aperture troubleshooting menu to open...any help?

    Leonie,
    Fisrt let me thank you for your reply and assistance!  So here is the problem with so more detail...I was not sure I was going to get any replies ; )
    I restored from a time machine back up.
    History of Failure:
    I was trying to launch Aperture when the kernal panic occured.  My computer had been closed, and asleep and the battery was dead.  I plugged in charger and it was restoring/waking up after being asleep/shutting down from dead battery.  I launched Aperture from the dock and as soon as it opened the kernal panic occured.  After that the computer would not turn on.  It would try to boot then it would shut off.  I even tried to safe boot to no avail.  I went to the Apple store and they told me that the only thing I could do was restore whole computer from back up.  So thats what I did.
    Since then my previous aperture library: "2011" will not open.  I have created a new aperture library "2012", and it runs fine.  I have added new photos for about the past month...no problems. 
    When I launch aperture with 2012 library then try to switch libraries, I get the following prompt: "The selected library is from an older version of Aperture and requires a relaunch to switch."  I choose "Relaunch" and I get the following warning prompt: "There was an error opening the database for the library “~/Pictures/Aperture Library 20111.aplibrary”."  The only option is "Quit"
    Both libraries are version 3.2.3
    Computer stats: 3.06 GHz Core 2 Duo, 8 GB 1067 MHz DDR3 RAM, OS X 10.6.8
    I have tried to launch aperture troubleshooting by holding option+command from both the aperture icon and from the library file, neither will launch the troubleshooting feature.
    I am ok with computers, but not a whiz (mechanical engineer)...to me it seems as though there is a corrupt path or file or some sort of "check" that is failing, becuase the failure occurs so fast after trying to launch aperture. Maybe that doesn't make any sense but just a thought.
    I hope that you may be able to provide some insight.  Thank you again for you time and I hope that you have a nice day!
    Mike

  • Aperture 3 won't open in two user accounts

    My new girlfriend and I are both photographers, and share one iMac with Aperture3.
    Both of use are Aperture3 power users and the bulk of our time on the iMac is using Aperture.
    Recently I decided to make her her own account on my iMac but she couldn't open Aperture if it were open on my account.
    I don't recall having this problem with Aperture 2...
    is there a way to override this? Most of our fast user switching will be from me working with Aperture in my account to her using Aperture on her account.

    The only good way to share an Aperture library between two accounts is to store the library file on a 2nd (non-boot) drive with "Ignore Ownership" turned on. Unless you have a Mac Pro with multiple internal drives, you'll need an external drive (preferably a Firewire drive but USB will also work). To turn on "Ignore Ownership", do a Get Info on the drive and check the box at the bottom of the Get Info window. It needs to be a non-boot drive because you cannot turn on Ignore Ownership on the boot drive.
    Even if you do as I suggest, only one account can have the library open at a time.
    I've been sharing a library with my wife (separate account) using a 2nd internal drive in my Mac Pro for about a year and it works well. Except when she deletes photos that I would have kept (of her) - but that's a different problem.

  • Aperture Trial Fails to Open

    I can't find an article about why Aperture would fail to open, so I apologize if this is a well known problem.
    I have a mac mini core solo with 2 gb of memory and 10.4.8. I installed the trial from the website and following that, the application fails to launch the first time. When opened, the icon appears for half a bounce and disappears again.
    I've run the compatibility checker which suggested no problems. I've also attempted to install the 1.5.1 update even though I know I'm not supposed to. The result was the same.
    I tried uninstalled and reinstalling and even app-zapping and reinstalling with no change.
    So, does anyone have any ideas? I'm not convinced the issue is that I have a mac mini. I'm thinking it may be an incompatibility with another software that's installed, but I have too many to list here.
    Mac Mini Intel Core Solo   Mac OS X (10.4.8)   2gb RAM

    I did actually try that. After I installed 1.5.1 the first time just to see what happened, then tried uninstalling and app-zapping - I went back to square one and got a new img and trial code. No luck there either.
    (but thanks for the help)

  • Image open problem in nokia 5230

    Dear All,
    I have nokia 5230 mobile & i am using from last 10 months but from past few days i am facing problem regarding image/songs open problem.  whenever i trying to open image my phone gets hang & it shows nothing in it but i have 100 pics in memory card, same problem is with songs whenever i put some songs in memry card but songs gallery after refreshing shows nothing.
    Please help me to resolve this issue.
    Vipul

    im not sure what to do about the images but the same happened with the songs. here is waht i did:
    1. make sure you have the latest firmware installed (fw. 50).
    2. when it is installed copy all tracks to pc and install nokia ovi music.
    3. delete the folder called 'music' on your memory card.
    4. open ovi music and add songs to playlists and copy to device. this will create a new folfre called 'music' and the error should be fixed
    if that fails you should try a program called lcg jukebox as this is a much better music player 

  • Desktop.open() Problem

    I recently put together an application that relied heavily on the Desktop.open( ) method and several other methods from the Desktop class. However, all of a sudden the Desktop.open() does not work. I believe I read some where that this was due to the ShellExecute function or dll or something like that.
    However, since my app is targetted at the Windows platform I resorted to using windows Explorer to launch the system default applications for files using a the code below
    public static void openFile(File file) {
      try {
        Runtime runtime = Runtime.getRuntime();
        runtime.exec( "explorer.exe \"" + file.getAbsolutePath() + "\"" );
      } catch(IOException) {
        ioe.printStackTrace();
        JOptionPane.showMessageDialog(null, "Could Not Open File Location: " + file.getAbsolutePath());
    }The code works as expected, but my problem is that I am loosing cross-platform functionality.
    Can any point my to solution to this Desktop.open( ) problem, or probably add the my list platform dependent launch procedures so at least the code works on Windows,Linux and Mac.
    ICE

    Thanks Andrew,
    I've do a more simple example of the problem. I create two files on "\\fiuu\proyectosShared", one called "test.txt" and the other one called "te st.txt". I execute your exact source for the who paths whith these results:
    File f = new File("//fiuu/proyectosShared/test.txt");
    System.out.println(f + "  exists: " + f.exists());
    dt.open(f);
    RESULT:
    \\fiuu\proyectosShared\test.txt  exists: true
    (notepads opens the file)The second test does'nt work:
    File f = new File("//fiuu/proyectosShared/te st.txt");
    System.out.println(f + "  exists: " + f.exists());
    dt.open(f);
    RESULT:
    \\fiuu\proyectosShared\te st.txt  exists: true
    Exception in thread "main" java.io.IOException: Failed to open file:////fiuu/proyectosShared/te%20st.txt. Error message: El sistema no puede hallar la ruta especificada.
         at sun.awt.windows.WDesktopPeer.ShellExecute(WDesktopPeer.java:59)
         at sun.awt.windows.WDesktopPeer.open(WDesktopPeer.java:36)
         at java.awt.Desktop.open(Desktop.java:254)
         at DesktopTest.main(DesktopTest.java:14)
    (translation of error message: System can't find specified path)I've also done some tests with Desktop.browse(file.toURI), and some others with no success.
    Something curious: try to execute Runtime.getRuntime().exec("explorer " + f.getAbsolutePath) for a file that has thow white spaces on his name....
    File f = new File("//fiuu/proyectosShared/te  st.txt");//with two white spaces
    System.out.println(f + "  exists: " + f.exists());
    Runtime.getRuntime().exec("explorer " + f.getAbsolutePath());
    \\fiuu\proyectosShared\te  st.txt  exists: trueSystem says:
    Explorador de Windows
    La ruta '\\fiuu\proyectosShared\te st.txt' no existe o no es un directorio.
    Aceptar  
    (spanish version of File not found alert message)Note that in alert message one white space of filename is lost!
    Thanks again
    Edited by: pakomail on Nov 24, 2008 6:12 AM

  • Oracle error - Open problem

    hi friends,
    on accessing the database i get this following error:
    Open Problem - ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Execution Problemnull
    How can i resove it...

    Here's a wild idea.... check the Oracle site/documentation for suggestions ?

  • Aperture library won't open after using new iphoto

    My Aperture library won't open after accidently using iphoto to view it. It says Aperture is outdated but I run 3.4.5 version which is the last.
    Now I CAN'T DO MY WORK thanks to this lunacy.
    Anyone any suggestions how to fix this ****?

    Also one more thing
    On the MacBook Air - Where aperture is working fine and loading the library, i tried to change the name of the library and then when I tried to open it it shouted with the error ""Error Opening Library--The library could not be imported because it is from an out of date version of Aperture 3. Please upgrade the library to the latest version of Aperture 3 and try again""
    But when I changed the name back it was working fine again on the MacBook AIr
    Should i be worried that when i look at the get info on my library it says it's an aperture library 3.5.1 ?
    Pandava

  • I've upgraded to Snow Leopard, Aperture 3 won't open.

    I've finally upgraded to snow leopard (hoping the bugs would all be worked out!)  Aperture 3 won't open.  I did the "fix" found under aperture support.  However, the advised,  3.1.1 update for aperture won't open either, saying it I need to install aperture 3 first (it is installed!)  help please....

    Please see this thread and do follow all the instructions.
    Just upgrade to Snow.  Now Aperture 3.1 will not start.
    I know you have Aperture 3 installed and feel its silly to reinstall it but just try it.

  • Aperture 2.1.3 Export Problems with Cropped Photos

    I ran into an odd problem after updating to 2.1.3. I was trying to upload to a Picasa album via "aperture-picasa-plugin", which I had used before without problems. The resulting export had problems with two photos I had cropped from landscape to portrait size. The resulting exports had the entire uncropped/original content "squeezed" into a photo matching the cropped size, so the exported pics were squished making everything look tall and skinny. (I found it especially odd that stuff I had cropped out was back in, but the size was cropped.)
    I assumed it was a problem with the plugin, so I exported to a file straight from Aperture and had the same problem. I had other crops that worked OK, but they appear to all be landscape to landscape with no change in aspect ratio.
    Is anyone else having this problem?

    YES!
    I have seen this show up as well. I'm also using Aperture 2.1.3. I too thought it was the fault of the picasa plugin... but when I, like you, started doing my exports directly to files I noticed that they still had the same problem.
    The horizontal 16x9 seems to be particularly vulnerable... And, yes, it almost looks as if the (pre-crop) master has been "squished" into the aspect ratio of the (post-crop) version. It is very strange, very annoying, and very intermittent. Although, I found that if I quit aperture, restart then re-export... I have better luck.
    Boy, am I relieved to find somebody else who is having this problem. For a while there I thought I was going nuts.
    -C.

  • Aperture 3 fails to open Leica D-Lux 6 RAW files

    Aperture 3 fails to open Leica D-Lux 6 RAW files. Any patch coming soon?

    Sorry, but we don't know. This is a "User to User" forum - you are not talking to Apple.
    You might consider to import "raw&jpeg" while you are waiting, so you will have the raw available, when the raw support will be released.
    Or use the software, that came with your camera, to develope the raw and import tiff to Aperture, while you are waiting.
    Regards
    Léonie

  • Having installed Aperture iPhoto won't open. When I try it fails with the message "You can't open the iPhoto.app because it may be damaged or incomplete. Any help please?

    Having installed Aperture, iPhoto won't open. When I try it fails with the message "You can't open the iPhoto.app because it may be damaged or incomplete. Any help please?

    OK, fixed it.  Found that iPhoto is now BACK in the App store.
    Found iPhoto app in Finder and dragged it to Trash.
    Downloaded iPhoto from App store and all now back working again.
    Didnt expect to find iPhoto in App store as last time I looked it wasn't available.
    Nige

  • Aperture 3.2.1 Import problems.

    Aperture 3.2.1 Import problems. I can not import. Complete system hang when I try. Have to force reboot. I made a new user and everything seems to work fine under that user. I must have something conflicting in my admin user but I have had no luck finding it. I have tried rebuilding the library (all three options) but to no avail. Aperture will run fine as long as I do not try to import. This is very frustrating, any help would be greatly appreciated.
    27" imac 3.06 intel core 2 duo 12 GB Ram

    Hello Tim,
    If a problem only occurs when working from one account, then very often faulty user preferences or presets are the cause. Try to remove your user preference file, and if that should not suffice, move your presets to the desktop, as described in the Aperture 3: Trouble Shooting Basics:
    (Caution: I see, you are running Lion: Because of Lion's non-preemptive Process Management you can never be sure if an application really has quit, even if it looks in the Dock as if the Application has finished. So it is very important to log off, before you launch Aperture again, after you changed something in the libraries like described below.)
    Delete the user preferences
    You can resolve many issues by restoring Aperture back to its original settings. This will not impact your image files or your library. To reset your Aperture user preference settings to their original state, do the following:
    Quit Aperture.
    In the Finder choose Go to folder from the Go menu.
    Type~/Library/Preferences in the "Go to the folder" field. Press the Go button.
    Remove the "com.apple.Aperture.plist" file from the Preferences folder. (and log off and log in again!)
    Move the user created presets, keyword lists, and so on...
    Quit Aperture.
    In the Finder choose Go to folder from the Go menu.
    Type~/Library/Application Support/Aperture in the "Go to the folder" field. Press the Go button.
    Move the contents of this folder to your Desktop (and log off and log in again!)
    Start Aperture and see if the issue is resolved. Note: Permanently removing these files will delete presets, metadata sets, keyword sets, and so on. If moving these files to the Desktop does not resolve the issue, move them back to their original location to restore the presets, adjustment chain presets, and metadata sets. In no case will removing these files affect metadata, keywords, or adjustments already applied to images.
    If none of this should help, try to boot into safe mode (hold down shift after the start up chime), to see if you have conflicting plugins or video drivers etc. installed in your admin library.
    HTH
    Léonie

  • Just Bought Aperture and won't open

    Hi
    HELP
    I just bought aperture and it won' open. Here's the message I see
    Process:         Aperture [651]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.3.2 (3.3.2)
    Build Info:      Aperture-265039000000000~4
    App Item ID:     408981426
    App External ID: 9411464
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [106]
    Date/Time:       2012-07-29 21:06:07.845 -0400
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Interval Since Last Report:          1566976 sec
    Crashes Since Last Report:           16
    Per-App Crashes Since Last Report:   9
    Anonymous UUID:                      AF579EE0-2B7B-4BB8-82CE-78EF40A89A7A
    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/PluginManager.framework/Versions/B/PluginManager
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: image not found
    Binary Images:
           0x100000000 -        0x1007cafef  com.apple.Aperture (3.3.2 - 3.3.2) <738E7070-D100-3296-8AA9-47BE3189DA95> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x1009c5000 -        0x100f50fe7  com.apple.RedRock (1.9.4 - 260.53) <1C2CBF83-E0BC-3A93-9807-02C5A42065BE> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
           0x10123c000 -        0x1012b6fe7  com.apple.iLifePageLayoutCore (1.0 - 170.28) <C3FE94E3-3F93-32BA-B9D8-BA63D56DFF40> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore
           0x101309000 -        0x10130cff7  com.apple.iLifePhotoStreamConfiguration (2.2 - 2.2) <A6E7CD7C-A826-395F-ABBC-E227071F726F> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
           0x101312000 -        0x101322ff7  com.apple.iLifeAssetManagement (2.6 - 25.16) <CF6842C3-01FE-3EEB-980C-04388E263D9A> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
           0x101335000 -        0x1013d8ff7  com.apple.MobileMe (13 - 1.0.4) <0705CAD2-E813-3657-B66B-C018753A9E7E> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
           0x200000000 -        0x20000cff7  com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <4B16E262-B842-3AA4-9252-E4EC0FE0BC1E> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
        0x7fff6acc4000 -     0x7fff6acf8baf  dyld (195.6 - ???) <0CD1B35B-A28F-32DA-B72E-452EAD609613> /usr/lib/dyld
        0x7fff89a36000 -     0x7fff89a82ff7  com.apple.SystemConfiguration (1.11.3 - 1.11) <0A7F1982-B4EA-3424-A0C7-FE46C6224F03> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff89a88000 -     0x7fff89a8efff  com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
        0x7fff8b297000 -     0x7fff8b2a7ff7  com.apple.opengl (1.7.7 - 1.7.7) <0CA11278-746C-353A-923B-BCC0047190C3> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
        0x7fff8c12f000 -     0x7fff8c2b9ff7  com.apple.WebKit (7534.56 - 7534.56.5) <BC22A17F-A32F-3D9B-926F-091A47C4B315> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
        0x7fff8c655000 -     0x7fff8c829ff7  com.apple.CoreFoundation (6.7.2 - 635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff8cddd000 -     0x7fff8cdddfff  com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
        0x7fff8ec0d000 -     0x7fff8ec0dfff  com.apple.ApplicationServices (41 - 41) <89B6AD5B-5C75-3E83-8C2B-AA7F4C55E400> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
        0x7fff8edae000 -     0x7fff8ef4dff7  com.apple.QuartzCore (1.7 - 270.4) <97E20A5F-652B-3E85-8C46-DCB777248ECD> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
        0x7fff900aa000 -     0x7fff902acfe7  com.apple.AOSKit (1.02 - 91) <78F90BCC-414B-38E0-908D-A17906CF31FF> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
        0x7fff90677000 -     0x7fff90677fff  com.apple.Carbon (153 - 153) <AF0F9910-E3C3-3922-AA92-A39000655E0F> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
        0x7fff92edb000 -     0x7fff92f6eff7  com.apple.PDFKit (2.6.3 - 2.6.3) <49BF9CDC-E902-3CAC-9C04-3302545907D5> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
        0x7fff92f9b000 -     0x7fff92f9bfff  com.apple.Cocoa (6.6 - ???) <7EC4D759-B2A6-3A99-AC75-809FED1500C6> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
        0x7fff93018000 -     0x7fff93083ff7  com.apple.framework.IOKit (2.0 - ???) <6C604894-7F61-3130-8499-20791D14577F> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
        0x7fff9320a000 -     0x7fff934f3ff7  com.apple.security (7.0 - 55148.1) <E9C46204-1336-3D90-BC67-5162FC7079D2> /System/Library/Frameworks/Security.framework/Versions/A/Security
        0x7fff94e84000 -     0x7fff94e84fff  com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    H

    If the Combo installer did not work (what is the exact error message?), try to download Lion again from the AppStore, or boot into the Lion Recovery Partition:
          OS X: About OS X Recovery 
    You can also try, to restore the missing framework from your backup.
    You need to restore this folder from the System Library:
         /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
    Regards
    Léonie

  • Since the recent upgrade all my photos have gone from Aperture and i cannot open any backed up Aperture files please help.

    Since the recent upgrade i have lost my Aperture libaray and cannot open the old one message reads you cannot use this version of the application Aperture original with this version of OS X you have Aperture original 3.2.4.
    How do i get my photos back please.

    Aperture 3.2.4 will not work on Mavericks.
    You can do as I did, either do a web search for Aperture updates to your current version of Aperture to update to Aperture 3.4.5 OR just simply upgrade to latest version of Aperure 3.5 ( from the Mac App Store) that is fully 64 bit compliant for OS X Mavericks. As long as you have registered your previous version of Aperture, the new 64 bit version will be a free upgrade.
    Be advised that if you just upgrade to the latest version of Aperture, it will update your Photos  Library, as well.
    When this happens, your old version of Aperture on older versions of OS X will no longer work with the new, updated Photos Library.
    If you still want to be able to access your Photos Library with an older version of Aperture and older OS X version, you need to make a copy of your current Photos library.
    Make a copy of your current Photos Library and put it into a folder called something like old Photos Library so you still have an older version you can still access if you need to.

Maybe you are looking for