Update Vault Error

I can no longer update my Apertue 2.1.4 vault. Since installing Snow Leopard, I first noticed my iPhone would no longer sync pictures via Aperture 2, but would via iPhoto. Now I find I also cannot update vault to an external drive. Have redone permissions, rebuilt Aperture library, tried to create new vaults on the original external drive and the internal drive. Always get same "Update Vault Error" response and images don't appear to go into the vault. I see similar posts with no solution. My Aperture Library has 14000 photos.
I wonder if these problems will carry over to an Aperture 3 library.
Hoping for some advice

No, I thought of that, I tried to make it simple:-
Lacie/backup/Vault
Or on the internal:-
Users/me/pictures/vault
It may be that one of the images or possibly a sidecar file in my project is corrupt, thus making the library itself corrupt.
Therefore, when Aperture tries to compare its internal library structure to the Vault, it finds an error and blames the Vault for being corrupt; even so it still finds errors trying to backup to a blank brand new vault. I have a problem with the fact that it is suggestng that the vault be deleted(!) and replaced, even though the problem is likely to be with the internal Library itself and not the vault. And replacing the vault with a new one is impossible (still has same error).
Unfortunately I have no way of finding out which one of the 2500 or so images in the library has the problem. I thought that the commandoptionrestart Aperture to rebuild the library would have worked, but unfortunately it doesn't.
L

Similar Messages

Update Vault error message

Aperture is not letting me update my vaults. I am receiving update vault error messages when trying to back up to Vaults. I have three backup Vaults on external firewire drives, formatted Mac HFS+ (not MS-DOS) and not partitioned. My Aperture library is also on a dedicated external drive. I get the same message for all three vaults, so this seems to be an Aperture problem, not a disk problem. The error messages refer to NEF (raw) image files that do not exist in my Library (or anywhere else, for that matter). Message reads:
update vault error:
The following error occured:
Couldn't create/Volumes/LaCie/ApertureV2.apvault/Library/....
Any insights would be appreciated.

James Bouret's problem is fixed -- or maybe not.
From my blog: +We traced the problem to "something bad" about the folder or its contents that was being reported. By opening the library and the vault with control-click Show Package Contents and navigating down, it was possible to trash the folder. Not only did the vault update complete once that was done, but it worked many, many times faster than before. The bad news is that I think this is due to a bad spot on the disk, indicating a drive that is on its way out. If you have vault problems: back up carefully and consider that you may have a bad disk.+
A bad spot on the disk may also be the reason that Johnny Cappuccino could fix his problem by modifying the image. That will have rewritten the sidecar files, a process that usually involves creating a new temporary file and then atomically deleting the old file and renaming the new one. So the new file is shiny and good and the bad spot is ready for use by another hapless program.

Update Vault Error: Errors creating a directory in vault "date".

I updated my Aperture vault in December.
When I tried to update it again this morning I get the message *Update Vault Error: Errors creating a directory in vault "date".* In one instance it says 15 errors occurred. In another it says 219 errors occurred.
Other than delete the current vault and re-create it, are there any suggestions as to a fix for this problem?
Jerry

I have noticed the following:
+ While I cannot update an existing vault, I can create a new vault on the same folder/disk. For my purposes, I will probably use this vault and delete my old vault that I can no longer update.
+ The last time that I successfully updated one of my existing vaults was 4 days ago. Since then, I accidentally blew-away my preferences and subsequently restored them from backup... but the restored preferences predated the current Aperture library.
Perhaps there is something in the Preferences ( <user>/Library/Preferences/com.apple.* ) that retains some state about the state of recent vaults. I haven't looked. Perhaps the status of my Aperture Library was out of sync with my restored preference files.
Anybody with this problem have a similar situation?

Update vault errors yet to be solved.

As suggested in the forums, I have dragged the aperture.app to the trash and installed the new v2.1 once again. I can create a vault in an external HDD (FAT32), but I still get the 'cannot create ... *.apfile' errors when I update it.
Did I missed any steps, say delete any preference files, in order to make it works?
I hope Apple could fix the error in the next update soon.

Ohhh...
You cannot have a vault on a FAT32 volume. It has to be an HFS+ volume.
FAT32 cannot handle the file naming that Aperture uses... Aperture uses characters that are illegal on FAT32.
So you have 2 options:
1) Reformat the drive as Mac OS X extended (Journaled) -- a.k.a. HFS+ Journaled
2) Create a sparse image on the drive using Disk Utility, open that image, and create the vault on that. This is more work, more complicated, and really not recommended (but will work in a pinch).

Update vault errors connected to Spotlight rescan?

I haven't had a vault update error for a long time. Then I had spotlight rescan my external drives. Now I get ONLY errors, on external and internal vaults.
Anyone have any ideas?
Thanks,
Brent

Ohhh...
You cannot have a vault on a FAT32 volume. It has to be an HFS+ volume.
FAT32 cannot handle the file naming that Aperture uses... Aperture uses characters that are illegal on FAT32.
So you have 2 options:
1) Reformat the drive as Mac OS X extended (Journaled) -- a.k.a. HFS+ Journaled
2) Create a sparse image on the drive using Disk Utility, open that image, and create the vault on that. This is more work, more complicated, and really not recommended (but will work in a pinch).

Recurring vault errors

I'm having a recurring problem when updating vaults from Aperture 2. I fixed it first time around but its started to occur again. Any help?
*_First time_*
Back in November, our copy of Aperture 2 installed on a PowerMacG5 kept on quitting unexpectedly, and vault updates on a Lacie hdd brought back errors. I tried to rebuild the library on another Mac (a PowerBook) running Aperture 2 but this brought up errors too, saying certain items would not copy. Items causing these errors were deleted out of the G5 library but the vault would still not update.
Our next step was to copy the library off the G5 onto a smaller external hdd (successful), move library onto an iMac (successful) and try to import this into a copy of Aperture 2 running on the iMac. This last part failed, until we re-installed Aperture 2. However we could not create an vault from this new library (errors coming up again). Several different external hdd drives were tried, all bringing up problems.
We hit success when, on the iMac still using the 'good' library, we deleted all links to previous vaults, and reformatted external hdds so they were all in Mac OS X Extended (Journaled) format. We were then able to make two vaults successfully.
*_Second time_*
Update Vault Error has started up again (approx 700+ errors....). Has anyone got an idea why this could be happening, or give me any hints of new things to try?
I'm sorry I can't give exact details right now but I am not at the same location as the affected Apple Macs

hi, i'm not positive but i think i may have the same problem. furthermore, i've noticed a common theme to the problem.
first off, some background. i'm by no means a power user of the package, nor am i a mac expert and i've been 'satisfied' with aperture 2, that is until last november 2009, when for some reason, i lost all my aperture image files on my macbook, they had all been imported using the aperture wizard and saved to the vault. i was very diligent. so, no problem i thought, i'll just restore from my vault.
plugged in my portable hdd, commenced the restore routine, aperture restarts and on clicking confirm, i get a message stating that aperture has failed (or something similar) with 'close', 'try again' and 'report' buttons.
now i've been trying to get to the bottom of the problem for some time and Apple seem to have ignored this issue i thought i was defeated and all my images lost for ever. However, i've got round this issue and found most of my images.
there are two elements to the issues i've been experiencing:
_first accessing aperture:_
- i tried re-installing the application and much more. i just couldn't open aperture. however i finally tried opening aperture and at the welcome screen selecting - *import from a media card* (or something like that), rather than my standard option - *continue to aperture*. This worked for me and got me into aperture.
_the second issue - restoring the image files - well this is a more of a problem:_
- i noticed that most of the project folders worked perfectly well and that the images had been restored, however, those project folders with a light-table or a similar sub-set folder; well only the images in the light-table had been restored, the project folder images have been lost. i can't get these back. So before giving up completely, try reviewing the light-table or filter file within the project folder.
to summarise - i don;t know why aperture failed on me last november. additionally, i would recommend to any aperture user that you do not create a backup vault of your files if you have a subset of images selected within the project folder, such as a light-table or a filter, the vault doesn;t seem to be able to handle them.
i do hope this helps people if they have experienced a similar problem. for me, i've now given up on the mac platform, its just been to painful. Mac works great if there are no problems, but when a problem occurs, its generally a big one.
I've lost a considerable number of images, ones which i am extremely proud of and enjoyed looking at and sharing, and this experience and a few other gripes (i.e. a distinct lack of appreciation for an issue which has affected many people) has now driven me back to the pc platform. so long Apple, if you fancy buying my second hand, but well looked after macbook, you will find it on ebay soon.

Vault error

I've created a vault to backup my photo libraries and that went fine.
However, when I try to update it with new images I get an error message "Update Vault Error" along with the directory path.
I've tried creating a new vault, and then backing up, and get the same message.
DOes anyone have advice on what is wrong with the Vault routine?
Thanks.

Yesterday I had the same problem in all three of my vaults. It happened after I'd made major changes in the organization of my Aperture library. I moved hundreds of masters from one project to another. When I tried to update the vaults, I got the same error messages or similar as the rest of you are reporting...something like "Can't create a directory on the Vault" and there'd be some 700 errors and the message was relaying the first five.
I rebuilt the library (press Command and Option while booting Aperture). Still the Vaults could not be updated. So I trashed all three vaults and re-created them all. Very frustrating!
The happy thing is that it seems that the Library itself was never compromised, and the Rebuild went very smoothly and quickly.
I also have two full bootable back-ups of my hard drive on external drives. And these bootable back-ups include full copies of the Aperture Library. I re-did the bootable back-ups after the major re-organization of the Library, and there was no problem.
In my view, there are major problems with the Vault software itself. It seems to stumble unnecessarily. Many users report that one corrupt file will cause the whole Vault procedure to crash. It would be much better if the Vault system carried on with the update and then simply reported the problem file, which could be corrected or deleted. But to have one corrupt file compromise the whole Vault update is ridiculous.
And the Vault message which was repeated some 700 times was not helpful at all. It gave me no idea how to correct the situation, other than trashing the whole Vault and starting all over again.
I use Synchronize Pro X (by Qdea) and Data Backup (by Prosoft Engineering) for my bootable back-ups and other backing up to external drives. Neither of these will handle a smart back-up of the Aperture Library package alone, covering only the incremental changes in the Library. But they do the incremental changes as part of the overall bootable back-up process.
I'd like Apple to make the Vault process as solid as the back-up process provided by Qdea and Prosoft.

Error when I "Update Vault Path..."

I have had some lingering problems with my Aperture library that I am just getting around to addressing. One is that I need to back up to my vault, but it is not letting me do so. When I hit the little (red) refresh button on the bottom of my window, I get the message:
"Update Connected Vaults?
Some vaults are not connected. Do you wish to replace the contents of all connected vaults with the current contents of your library?
This cannot be undone."
Because I'm an adventerous guy, I did this, but when I try to refresh my vault the next time I get the same error.
So I started poking around and found the "Update Vault Path" menu item. This sounds like it should solve my problem, but when I go through and select my vault and try to update the path I get the error message:
"Incorrect Vault Selected
The path could not be updated because the selected vault does not match the original vault."
This is definitely the right vault. It is on a partition of my Time Capsule. However I may have moved the file or changed the name of something a few months ago, which I suspect is why I'm having this problem now?
What do I do to get that vault path back in order?

Is this Aperture 3? Are you talking about one library or multiple libraries? How many vaults do you have connected to the library?
If you click the *show/hide Vaults* button what does Aperture show you? This is the name of your vault(s) and their locations. Does that match what you think it should be?
Sounds like you may be better off just creating a new vault and using that going forward.

Error when updating vault 3.3

Hi,
Just updated to 3.3
tried updating vault
it says "To open this Library in Aperture, you must quit (null)"
I click cancel and Aperture quits
if hold down option and open and the go to the vault it's greyed out
Any one know how to update from Aperture 3.2.3
Mark

"Using Aperture Library First Aid Utilities
Aperture 3 includes a new tool called Aperture Library First Aid that can correct the most common library and database issues Aperture 3 users are likely to encounter. To access the tool, do the following:
Quit Aperture 3 if it is currently open.
Press and hold the option and command keys while you launch Aperture 3.
The Aperture Library First Aid utility will launch, and provide three different repair processes you can perform.
Repair Permissions: Examines your library for permissions problems and repairs them. This requires Administrator access.
Repair Database: Checks for inconsistencies in your library and repairs them.
Rebuild Database: Examines and rebuilds your database. This option should be used only when repairs to the database or permissions do not address library problems."
>>> repairing permissions will most likely resolve your problem.

Aperture 2.1.1 and OS X 10.5.5. - Can't create nor update Vaults!

After updating to OS X 10.5.5 and installing the latest RAW file plug-ins update from Apple yesterday, I cannot update my existing Aperture vaults, I get the following error message:
The following error occurred:
Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one.
I deleted both vaults, created new vault, and when I press Update button, it compares empty vault to my library for some 4-5 minutes (why?! It's just empty vault!) and then Aperture shows the same message:
The following error occurred:
Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one.
I ran Disk Utility - Repair Disk Permissions - no problems. I installed 10.5.5. combo update over the existing system, restarted, and still I cannot create a new vault. The same error message. Any ideas why?
In Console I see two lines from Aperture:
08.9.17 19:28:52 Aperture[336] .sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.)
08.9.17 19:28:52 Aperture[336] line number: 2
I don't know is it related to this problem or not.

I am having exact same problems. Software update says that I have all the latest updates for system and Aperture (including the latest RAW file plug-ins). I can't update vaults. Every time I try to update, I get the following error message:
The following error occurred:
Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one.
I have deleted all vaults and tried creating new vaults. Aperture will permit the creation of the vault, but when I attempt to update it for the first time, Aperture works away for a while comparing the 'library' to the empty vault and returns the exact same error message:
The following error occurred:
Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one.
I rebooted computer and restarted Aperture holding down the option key. I requested that Aperture perform a 'Consistency Check' and when completed, I restarted Aperture the same way so that I could request that Aperture 'Rebuild Now' all projects. Once both activities had finished, I tired again to create a vault and update it and was able to create the vault, but unable to update it. The same message was returned:
The following error occurred:
Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one.
I did notice a change in Aperture's behavior before and after performing the 'Consistency Check'. Before performing the consistency check, Aperture had stopped giving this message upon quitting:
'Updating information for sharing previews'
After the consistency check, Aperture upon quitting would update information for sharing previews.
Is there a fix for this?

I want to transfer my vault to a new HD. The new has been formatted for Mac. Update Vault path is grayed out, despite doing all the correct steps beforehand

I have followed directions to transfer my vault to a new HD. It is grayed out, despite doing all requisite steps beforehand. If I get 'info' on Aperture the lock icon shows and I cannot change it to unlock.

I think you may be getting confused by the 'Lock'.
The vault is locked in the files system to prevent accidental deletion.
The reason the 'Update Vault Path' is greyed out is because it is still detecting the original vault on your system.
Here's a simpler process.
Restart your system (Aperture may still have a reference to the vault and this will clear it).
Make sure you have copied the vault to the new location.
Move the vault to trash. It will warn you the file is locked. Continue to move it anyway.
Empty your system trash. It will warn you the trash has locked files. Continue to empty anyway.
Now the old vault is gone from your system, in Aperture, the vault will show as disconnected and you can update the vault path:
You can then Navigate to the new location:
And the vault will reconnect and show the available storage of the new drive:
I suspect you are following advice about trying to remove the lock. But this is not necessary, the lock means you'll simply get warnings when deleting (assuming you have permissions to delete), but you can jsut override these warnings. If at any stage you get an error saying the file is in use, just reboot and retry that stage.
Andy

Can't update vault - icon is pale red

For some reason I can't seem to be able to update my vault. The drive is connected and appears in the vault pane, but the update vaults icon is a pale red. Update All Vaults in the File menu is also grayed out. There is over 200GB available on the drive, I don't get any error messages, and I can create a new vault on the same drive. I just can't update any of them.
I searched here for answers, but couldn't find anything. So if any one has any advice please let me know.
Thanks,
Andrew

Hi,
had the same problem and fixed it like this:
In Preferences remove ..aperture.plist
Log out as the current user
Log in as a different user (maybe you´d have to create one)
Start Aperture
Close Aperture
Log out
Log in as "yourself"
Start Aperture
Use ShiftR to show Vaults
Now it should work again as usual, worked for me, that is
Greetings from Munich, Germany

Multiple Vault Errors

I have been struggling with this for a week now.
I shoot on a Nikon D70s and I shoot raw format. I maintain two separate vaults on two external hard disks. I back up to CD/DVD regularly. I also import all my images into iPhoto - just in case. (Can you say Paranoid?). My Aperture Library is on a native (internal) Serial-ATA Maxtor drive using the Journaled HFS+ File System (disk1s3). My OS is on a seperate native drive (disk0s3).
Changes to my system just prior to this last shoot, include the installation of new RAM and the Aperture upgrade.
I went on a shoot lastweekend and returned with 400+ images. They imported fine into Aperture and Vault 2 was upgraded without issue. When I attempted to import into iPhoto - that program crashed. I have not been able to successfully import into iPhoto.
I then returned to Aperture, and attempted to update Vault 1 - Aperture reported a number of errors (17) and listed the first 5.
I have run Disk Utility and all drives report no problems.
I have rebuilt the Aperture Library and the problem persists.
Using only Vault 1, I have completely deleted the most recent shoot and re-imported them in small groups, deleting back out of Aperture those reporting errors during the Update Vault process. Once this completed, and I successfully updated Vault 1, I attempted to update Vault 2 - it returned 40+ errors and listed the first 5.
I then attempted to create a completely new 3d vault on a 3d external drive. The creation of that vault runs for some time, then reports thousands of errors, starting with the first image in the library.
I have attempted to copy the Aperture Library to another disk using copy, but that fails. The library is 59.86GB in size.
So, three different Vaults reporting errors at three different locations in the Image Library at different times.
I have visually inspected the images which failed out of vault 1 and I cannot find a problem with them. They display fine. Even from within Aperture.
My external drives are on a mix of connections, USB and FireWire.
My limited troubleshooting skills tell me that:
1) It's not a disk problem because the probability of all three disks having issues at the same time is remote - especially when all other programs and data are working fine.
2) It's not a bus problem for the same reason - the problem exists on both the F/W and USB bus. Again - all other programs and data are functioning well.
3) It's not actualy an image problem - because the images display fine using other external programs (Finder, Viewer, Elements etc).
Any suggestions?

Further information:
Every time I open Aperture, Vault 1 (the only vault to sucessfully upgrade) indicates yellow. Even though I have not modified my database.
Following another attempt to update Vault 2 this morning returned the error that Aperture could not create the preview for an image (P0314845).
A check of the Console Log shows the following:
Aperture(882,0x18af800) malloc: * vm_allocate(size=417996800) failed (error code=3)
Aperture(882,0x18af800) malloc: * error: can't allocate region
Aperture(882,0x18af800) malloc: * set a breakpoint in szone_error to debug
Aperture(882,0x18af800) malloc: * vm_allocate(size=484024320) failed (error code=3)
Aperture(882,0x18af800) malloc: * error: can't allocate region
Aperture(882,0x18af800) malloc: * set a breakpoint in szone_error to debug
Aperture(2509,0x18b3600) malloc: * vm_allocate(size=417996800) failed (error code=3)
Aperture(2509,0x18b3600) malloc: * error: can't allocate region
Aperture(2509,0x18b3600) malloc: * set a breakpoint in szone_error to debug
Aperture(2509,0x18b3600) malloc: * vm_allocate(size=484024320) failed (error code=3)
Aperture(2509,0x18b3600) malloc: * error: can't allocate region
Aperture(2509,0x18b3600) malloc: * set a breakpoint in szone_error to debug

Cannot Update Vault in Aperture 2

Today I started getting an error (actually 6 of them, all the same) when I try to update my vault. I am told "Aperture has detected a problem with the vault “Aperture Vault”. You need to remove this vault and create a new one." When I try to update the vault I get the "Comparing Library to Vault" barberpole for a while and then the error. Prior to today this vault file has been on the same drive for over a year and has worked flawlessly. I have done the following: 1) Deleted the old vault ad created a new one, 2) Deleted the Aperture plist file, 3) Repaired permissions on my boot drive and run Disk First Aid on the Western Digital MyBook (the drive is only 1/2 full) 4) Rebuilt the Library and run a Consistency Check 5) Trued putting the vault on any of my other drives.
None of this has worked, I still get the same error message. Any suggestions as to what to try next?

I had the same problem and tried about everything I found on this forum. None of it worked. Then I found the following two blog posts:
http://rickcogley.blogspot.com/2010/01/fixing-aperture-vault-errors-from.html
As I am not familiar with Terminal I did dare changing the settings. Trying via CMD-I didn't change anything.
Then I found the following solution
http://www.onlinenerd24.de/2009/04/17/aperture-you-need-to-remove-this-vault-and -create-a-new-one-error-message/
Hooray! Removed the Flickr and Facebook plugins and everything is solved!
Guess, I'll need to upgrade to Aperture 3 since this functionality is now standard available. Was that done intentionally, dear Apple?

RMMR1MRS-When run in background cause update failure errors looking

hi,
RMMR1MRS report when run in background cause update failure errors .
There are few below reason for the error log.
1. for the PO invoice already generated - (its right if already invoice generated. should not happen again)
2. In MIGO, entire quantity has been reversed and also invoice generated with zero value - ( its right , should not happen invoice again )
3. Particular PO line item deleted - (its right if the PO line item deleted. ERS settlement not require)
For the all above reason, the update error occurs. But the mean time the program "RMMR1MRS" should not through the update error log.
Note: The job was not terminated due to this update error and also no harm because of the error log
can you please help on this update failure why it occurs.

Have you found a solution already? If so, please, share it with the community and close this thread.

Update Vault Error

Similar Messages

Maybe you are looking for