Aperture 3.4 cannot repair/update library
See also link from previous discussion:
https://discussions.apple.com/message/19731719?ac_cid=tw123456#19731719
Aperture is repeatedly repairing its library
Upon the recent "update" from Apple concerning Aperture 3.4:
I installed the update on 9/20.
When I open my massive 1.16 TB Aperture library, I get this message:
Aperture has detected inconsistencies in your library. Please click Repair to avoid any potential problems.
Click Repair.
Then this message:
Repairing Library: Examining Library
Then this message:
Repairing Library, 1% Complete
Since then, Aperture has been repairing my massive 1.16 TB library for ~ 5 hours until it gets to 77% and then "Aperture Not Responding".
I have to Force Quit.
Open Aperture again and then this message:
Restore Windows. The application "Aperture" was forced to quit while trying to restore its windows. Do you want to try to restore its windows again.
Click Restore Windows
Then this message:
Aperture has detected inconsistencies in your library. Please click Repair to avoid any potential problems.
Click Repair.
Then this message:
Repairing Library: Examining Library
Then this message:
Repairing Library, 1% Complete
Then, the cycle begins again until it gets to 77% in about ~5 hours
Then "Aperture Not Responding".
I have to Force Quit.
And so on.
So, I deleted Aperture from hard drive
Install Aperture 3.0 from cd/dvd
Open Aperture...with new library. Fine.
Close Aperture.
Open Massive Aperture Library
Get this message:
Warning: The library in "Volumes/Libraries/ApertureLibrary.aplibrary" cannot be loaded because it is from a newer version of Aperture.
Select Quit
Close Aperture
Update Aperture to 3.4
Open Aperture with massive library
This message:
Aperture has detected inconsistencies in your library. Please click Repair to avoid any potential problems.
Click Repair.
Then this message:
Repairing Library: Examining Library
Then this message:
Repairing Library, 1% Complete
Since then, Aperture has been repairing my massive 1.16 TB library for ~ 5 hours until it gets to 77% and then "Aperture Not Responding".
I have to Force Quit.
Of course I send the Report to Apple. Every time.
And so on and on and on and on. For FOUR DAYS already.
My Mac Pro has been a brick and unusable since it is hogging the cpu with this Aperture update.
Check back to the Apple Discussion Forums
Get this message:
We'll be back soon. We are busy updating Apple Support communities for you and will be back shortly.
Repeat all the steps above for 2-3 times per day for 4 days.
This morning, ran the Repair Library from 8:00 a.m. until 11:56 a.m., when I force quit.
Rebooted computer.
Option + Command Click while opening Aperture.
Repair permissions.
Repairing Library, Database. That ran until 3:00 p.m. when it got to 77% again and we start the ground hog day all over.
Quit Aperture.
Option + Command Click while opening Aperture.
REBUILD Database, 3rd option.
3:11 p.m. 9720 versions restored.
4:19 p.m. 93000 versions restored
5:46 p.m. 169936 versions restored.
6:30 p.m., at time of this writing, it is still at 169936 versions restored.
When Force Quit, Aperture is NOT showing up as Not Responding. But...we aren't done yet either.
So, I have repaired permissions on my computer.
Re-installed Aperture from CD
Tried Time Machine
and rebuild library up the wa-zoo. To no avail.
I have removed the plist items from permissions.
Nothing so far has worked.
I'm sick and tired of spending the last 4 days rebuilding and not being able to use Aperture.
I am extremely disappointed.
And this nonsense happened in April as well.
I am an Aperture Certified Pro. Aperture 2, Level 1.
So sad...
John, if you already reinstalled and tried all repair options, we need more clues to what might be wrong in your case. Please post a crash report (the first 60 lines + the crashed thread) and any diagnostic messages relating to Aperture that you can see in the console window.
Regards
Léonie
Similar Messages
-
Aperture 3.3.1 frequently "Updating Library" when I quit Aperture
Since I've upgraded to Aperture 3.3 (now 3.3.1), Aperture frequently (almost 100%) spends time "Updating Library" when I quit Aperture. This takes like 40 mins to do. I've fixed permissions and repaired the library but no difference.
Does anyone else have this problem? I was hoping 3.3.1 would fix this problem but it doesn't. Next plan would be to rebuild the library but that will take a long time!
JasonSadly, you are on the cutting edge of the deployment of Aperture 3.3.x (along with many other posters here). The answer to your unasked questions -- "What is going on, and how can I fix it?" -- is "We don't know yet". Since you have upgraded to 3.3.1, and have let Aperture more than once run through whatever it is doing when it says "Updating Library" and it continues to update the Library for 40 minutes every time you close the Library, I advise you to go ahead with rebuilding the database. IME, this rarely takes longer than 10 hours, and can be run overnight.
I have rebuilt Libraries many times and have never seen a Library damaged by the rebuild. Nevertheless, you should have a complete and verified back-up before doing any maintenance on any Library.
Let us know what you do, and what the result is. Thanks. -
Aperture 3.01 Crashing on updating library
This all stems from my G4 MacBook 17" being stolen. My Aperture programme was on the laptop but luckily my library was on my office hard disc. This has a mixture of imbedded files and referenced files on a variety of media - CDR', DVD's and hard drives.
Laptop has been replaced with a new MacBook Pro 17" this week and loaded with an upgrade for Aperture 3 and Final Cut Express 4.
Aperture has been updated to 3.01 via software updater.
Aperture will run with the sample library but after upgrading my main library which went fine everything was OK until i quit and restarted the next day. It then crashes 30 sec's after starting and restarting continuously the same repeats itself.
I have created a new empty library and imported the updated library into it and again all is ok until I quit and restart, then back to crashing after 30 sec's.
The sample library after all this opens and works OK.
This is very frustrating as all my work is in the library and I am at a standstill.
Help!!It seems that the problem is something inside that library itself. Make sure you have a back up. Then launch Aperture while holding the command and option keys. In the resulting dialog box read what each option does and choose Repair Database. ( I doubt its permissions, but you could try that too.) This will take a while perhaps hours depending on the size of your library.
DLS
Oh, and welcome to the forum -
Aperture 3.4 can't update library
I updated Aperture on my iMac and on my MacBook Pro (Both 10.8.2) to 3.4. After the update Aperture opens and says it needs to update my Library. While performing the lib update the process stops with the message: WARNING: There was an error opening the database for the library “/Volumes/ApertureLib/Aperture Library.aplibrary”. The only option provided is "Quit" The same thing happened on both computers. I've tried launching with Cmd/Opt to rebuild and/or repair the libraries without any success. The repair/rebuild always crashes the app. When I launch with Opt key and try to create a new library, it fails to create one. I've tried reinstalling Aperture only to end up with the same results. I've done a permission repair and, of course, a reboot. Something is terribly wrong with Aperture 3.4.
John, if you already reinstalled and tried all repair options, we need more clues to what might be wrong in your case. Please post a crash report (the first 60 lines + the crashed thread) and any diagnostic messages relating to Aperture that you can see in the console window.
Regards
Léonie -
Aperture 3.2 won't update library, won't load
Upgraded from Aperture ver. 2.1.8. When I try to open the upgraded version, I get the message regarding the need to upgrade the library. Whether I check the box in the dialog or not, I get the message "The library in "/Users/sharedlAperture Library.aplibrary" cannot be upgraded." and it quits, so I can't even open Aperture. I have tried:
1) the instruction to start Aperture with Option and command pressed, and nothing changes (same sequence of dialog boxes)
2) reinstalled Aperture after deleting the software
3) repaired permissions etc using DiskWarrior
Still no luck...What if you move that library out of the shared folder and into the Pictures folder in your user account?
And what version of the OS are you running?
I'm assuming you meant 2.1.4 for the version of Aperture... -
At the opening aperture often tell me that the library has to be repaired
at the opening aperture often tell me that the library has to be repaired
my external hard drive which are directly connected to my imac 27 inches with 16 gig of ram dissapear. Which cause a problem if aperture was running.
O.k., if your external hard drive is suddenly offline, while Aperture is still using it, and could not complete all database transactions, the Aperture will insist on repairing the library, just like after Force-quitting; this is necessary, for the Aperture library may be inconsistent, if Aperture could not finish writing its data.
This is not an Aperture problem, it is a problem of your external drive. It should not dismount while a program is using it. If it happens, while Aperture is running and the computer is going to sleep, change the energy saver settiings and don't let your mac go to sleep, while you need Aperture running. Ask in one of the technology forums, why your disk continuously will dismount.
I have recuperate my library with a vault on a 6 tb brand new in september and i can't get access to this new library i am now recuperate all the images by making copies of the master files . What a mess
Is that the same harddrive, or a second library? Can't you get access to your library after letting the repair go through?
Léonie -
Just updated and: aperture can't update library
just updated from Ap 2 to 3 and got the following error message: The library in “/Users/name/Pictures/Aperture Library.aplibrary” cannot be upgraded.
Any ideas?The library in “/Users/name/Pictures/Aperture Library.aplibrary” cannot be upgraded
Is that the full error message you get? Are there any additional messages in the Console window? Any crash logs?
Backup your Aperture 2 library, if you have not done so and rename it from the default name, so that Aperture 3 will not overwrite it, by accidentally creating a new library.
Your Aperture 2 library may have a corruption. To repair this, try to repair the permissions and rebuild the library with the "Aperture library First Aid Tools". This would best be done with Aperture 2, if you have saved your Aperture 2 application, see the "Release Notes" (at the bottom of the page, additional information).
If you no longer have Aperture 2, try the repair with Aperture 3:
Hold down the option-command-key combination⌥⌘, while you double click your Aperture library.
Then select "repair permissions" from the First Aid panel, followed by a "Rebuild Library".
Regards
Léonie -
I launched Aperture with Option Command on opening so that I could repair the unified database. After I select repair from the menu, I keep getting a strange error message that says "This library has been opened with a newer version of Aperture. Repairing the library using this version of Aperture may remove data supported only in newer versions of Aperture." I selected cancel and checked that I am running Aperture 3.5.1 and there are no updates showing up when I select Software Update. So how could I have opened it with a newer version of Aperture before? And what is it going to remove?
Aperture is telling me that my unified library needs to be repaired. I figured that out myself when photos started disappearing in events and albums in iPhoto, even though the event or album showed several photos were there in the number of photos in the top right, no images appeared. But I have never received this error message in Aperture before and I do not know where it is coming from or what it is going to do.Here is the Open Library View #1:
Even though my unified library is the default library, just in case this problem was being caused because of the Aperture 3 Trial Library version (even though that is not the library that Aperture was opening), I upgraded that library too. Here is the Open Library Info after that library upgrade:
I retried the Aperture repair on my unified library and got the same error message on launch:
But I am running the repair anyway because I do not know what else to do. I will let you know how that goes when it is finished.
Anna -
first time I contact Apple Support Communities
I have re-installed Snow Leopard on a MacBook Pro(permissions = ok) and each Software update proposed by Apple.
After each software update installation, I have checked the permissions being ok.
But after install update 14 Java for Mac OS X 10.6.8 (proposed by Apple), I found 27 permissions errors. Disk Utility as well as Onyx cannot repair. (in fact they repair and if you check again you still have those 27 permissions errors)
It concern mainly System/library/Java/Java Virtual Machine + System/Library/Framewoks/JavaVM.Framework and System/Library/Java/Support/Deploy.Bundle
Do you have an idea how to get rid of those 27 permissions errors.
Thanks in advance
claude533As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.
Poster rccharles has provided this description of what it all means:
drwxrwxrwx
d = directory
r = read
w = write
x = executeable program
drwxrwxrwx
| | |
| | all other users not in first two types
| |
| group
|
owner
a little more info
Before the user had read & write. A member of the group had read.
After, only the user had read & write. -
Aperture Updating Library... 126,637 of 6,959,575
Hello all,
I upgraded to Aperture 3.2.3 and got an unexpected "Recovering Library" when it first started. Well, it seemed to have worked, and I did some importing in Aperture. It also started doing facial recognition in the background. I let all the background stuff finish, and then yesterday I quit Aperture.
At that time, it popped up a panel/sheet saying Updating library... 1 of 6,959,575 (commas added by me). It had done Updating Library in the past so I didn't think much of it.
However, now, a day and a half later, it is only up to 126,767 of those nearly 7 million. It seems to be going at a rate of one per second. At this rate, it will take around 80 days to finish. Given that my computer is a MacBook connected to an external DroboPro, that means I'm stuck with a non-portable computer that I have to hope has absolutely no crashes nor power failures nor any other hiccoughs for three months. Clearly, this is unacceptable.
Does anyone have any ideas what's going on here and what I could do, please?
Thanks,
DougIf you have not read and undertstood this, you should: http://photo.rwboyer.com/wp-content/uploads/2010/08/Aperture3Organization.pdf
This will tell you how to open the Library Package and determine how large your Masters, Thumbs, and Previews are.
Some other thoughts:
How full is your system drive on your MacBookPro? If it does not have between 25 and 30% free space, then that is the first thing you have to fix. Similarly, I assume that you have run Disk First Aid or Diskwarrior against your system drive, just be be sure that it is not, for any reason, hosed. From your comments about Lion, I would guess that:
-- Your OSX installation has real problems; problems that probably rate a visit to the Genius Bar; there should be one near you in New York.
-- Your Aperture rebuild may be having problems with latency - possibly because the catalog of your system disk is damaged or your Lion install is damaged. Couple that with the slow speed of the Drobo and things may be timing out. I will admit that this is a complete shot in the dark.
Assuming that your 2 TB Library is Managed, that is that the 2 TB includes your masters, and that you do not have 2 TB of free space in your MacBookPro, then:
-- First relocate your Masters out of the Managed Library and put them somewhere on the Drobo. There re many, many threads on this Forum discussing strategies for doing this.
-- Move the Library (now without Masters) onto your fastest, emptiest internal drive.
-- Resync everything. A quick pass with iDefrag wouldn't hurt after this much file movement.
Why lecture about backups?
-- Well, first of all you said that you had no backups.
-- Secondly, we are trying to diagnose a problem at a distance, on hardware that we cannot see. We can't really tell if your problem is with your Mac, Lion, the Drobo, or Aperture. Under those circumstances we could easily give really bad advice. The cyber version of the Hippocratic Oath (First, do no harm.) is to assure that backups are available.
Good luck and best wishes.
DiploStrat -
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 -
Hi,
I am completely confused. I use aperture everyday and today when I tried to open it I got the following message " aperture cannot access this library" then it said to use this library , make sure its file permissions are set correctly"
So i read a bunch of posts and opened aperture while holding down option and command and repaired the file permissions. it did nothing, when I tried to open aperture I received the same message. So then i tried opening it while holding down just the option key. This brought up all of my libraries but when I chose the library i use daily the same message came up.
Does anyone know how to fix this and/ or why it is happening?
Thank youNo idea how to check the format, not familiar with Drobo products. Does the drive show up in Disk Utility? If so you should be able to see how it is formatted there.
How long has this setup been in use?
Aperture libraries have to be on locally connected drives formatted as OS Extended as per Apple (see Format external drives to Mac OS Extended before using with Aperture for example). While Aperture may work with other setups there is always the possibility that the library will become unusable at any point in time with no warning.
Try to find out the format of the drive and post back. Maybe something can be done but from the error messages you are getting I'm thinking the best course of action will be to restore from backups onto a correctly formatted drive.
regards -
Tried to update my itunes and it says "iTunes installed incorrectly" now i cannot access my library
tried to update itunes and it says after download "iTunes installed incorrectly" now I cannot access my library.....HELP!!
Go to Control Panel > Add or Remove Programs (Win XP) or Programs and Features (later)
Remove all of these items in the following order:
iTunes
Apple Software Update
Apple Mobile Device Support (if this won't uninstall move on to the next item)
Bonjour
Apple Application Support
Reboot, download iTunes, then reinstall, either using an account with administrative rights, or right-clicking the downloaded installer and selecting Run as Administrator.
The uninstall and reinstall process will preserve your iTunes library and settings, but ideally you would back up the library and your other important personal documents and data on a regular basis. See this user tip for a suggested technique.
Please note:
Some users may need to follow all the steps in whichever of the following support documents applies to their system. These include some additional manual file and folder deletions not mentioned above.
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
tt2 -
my itunes cannot be update on my windows xp. so i delete my itunes and install new, but now i got new problems, it says "The file itune.library.itl cannot be read because it was created by newer version of itunes." so how can it be solved?
Hello Bebyida,
Thanks for using Apple Support Communities.
For more information on this, take a look at:
http://www.apple.com/itunes/download/
Best of luck,
Mario -
Error Message - "Aperture cannot access this library"
I'm using OS 10.5.7 and Aperture 2.1.3. I recently had an error message pop-up when I try to start Aperture that says, "Aperture cannot access this library. To use this library, make sure its file permissions are set correctly." Unfortunately, I can't seem to open up my library. Any ideas how to fix this or what is wrong? Thanks
Hello,
attached I would like to report how the problem solved.
1. I had 63 Minute Call to Apple Support and we are tring some things. Finally I Spend spend 1 day for testing.
2. Testing procedure:
A) I exported each project step by step
B) Than I deleted all appr. 50 projects in Aperture Library.
C) After that I Imported each project to Aperture back.
Result: 2 Project was corrupted, one of it was going well after export/import procedure how ever but the second ones error was constant appearing if I try to import it. The project consisting of 512 jpg files in total appr. 500MB.
The solution for this project:
I moved this jpg´s to waste bin und imported it from waste bin to Aperture again into a new project. Than I tested it again(Export/import) and it was fine.
For final check I delete my Aperture backup und start a new one.
Than start a compleate restoring from that last backup.
Every thing was fine, all project include albums or books are ok.
The pictures in the corrupted project was not imported by Aperture, they was created on a PC system(XP). Maybe that was the reason for the problem.
A friend sad, that windows use not the agreed standard for jpg´s.
I don´t know. So I´m happy all my books are back that is imported for a wedding photographer.
Have fun
bernhard66
Maybe you are looking for
-
I need help!! My I-tunes won't let me buy any more songs until I confirm that my account..is well..MY ACCOUNT! I can't remeber my security question answers, how do I reset them!? I also need to make a rescue email, i didn't make one when i first made
-
Hi I have created a form with fields. All the fields are in global namespace as i need to pass the values to all the resources. The problem is that the values are populated in my resources, but in Identity manager's user view, the values as well the
-
EncoreDVD CS3 crashes without an error message - perhaps not enough RAM?
Hi, my Encore DVD CS3 crashes without any error message! I made a DVD with a main menu and two submenus, one submenu for the chapters of my movie and the other submenu for a bonus part of my DVD. I'd linked all content to the buttons, except the vide
-
File being erased during input output stream
I am trying to send a .txt to an ftp server. The application will send the file but it is empty on the server end AND my original! The file is still there but is 0 kb with all data deleted. I cant seem to figure out what I'm doing wrong. Any ideas? t
-
PRINTING DELIVERY CHALLEN - MATERIAL DOC OF 541
We have a requirement of printing Delivery challen which is Material document of 541 movement type. Now I have to link the Material document line item to P.O line item. for this I was referring MSEG table where I have P.O No but not the line item no.