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).

Similar Messages

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

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).

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.

Attempt To Update Vault Generates Arcane Error

I have an Aperture 3 library with about 25k photos. The library sits on a Firewire 800 drive. I've created a vault on a second external drive. When I try to update the vault, it churns for a while, then asks if I really want to update the vault. When I hit okay, it churns away for a bit longer. Eventually I dialog box pops up with the message "You may put a maximum of 1000 photos in this published album".
I have no idea what this message means, or what it's in regard to. When I hit okay, there's no further "update" activity, and the little circular update icon next to the vault is not *black*, but remains *red*.
Anyone ever had this happen, or ever seen this error message? It doesn't appear in reponse to a google search either.
Thanks,
--Ian

I've never seen that message either, seems out of place in reference to a vault update procedure. Do you have any Facebook albums in this library?
Also how are the two drives (the one with the library and the one you are trying to create the vault on) formatted. You mention how the library drive is connected (firewire) but not how the second drive is connected. How is the drive you are putting the vault on connected to the system?
If, for troubleshooting purposes, try to create a vault on the same drive the library is on does it work?
Finally have you done the Aperture library first aid procedures? Specifically try the library repair to start.

Software Update can't connect to server -- error

I have Tiger 10.4.7 on a 600mH white G3 dual USB iBook. When I try to use the SoftwareUpdate function off the Apple Menu to check for any updates to Tiger, the "checking for new software" window starts up all right but immediately the error message window appears with "Software Update can't connect to the update server."
I'm otherwise connected to the internet all right and everything is working. I tried trashing the com.apple.softwareupdate.plist file from the Library/Preferences and the user/Library/Preference/ and restarting, but this didn't do it either.
I've had this problem before and it has "become" fixed, but I don't know exactly what sequence does it. Any help, please?
PM9600/233 (OS 8.6); G3 white iBook (10.4.7) Mac OS X (10.4.7)

No, I didn't try creating a new user, in part because once before doing that only made things more complicated and didn't solve any problems.
Software Update simply started working again. No idea why.
However, even after several days, Safari is still reporting that it cannot connect to the server for any URL put in. I've restarted Safari, reset Safari, manually emptied all caches, removed cookies. All very odd!
Firefox is working just fine.

My iphone 5c says connect to itunes. It won't update/restore; error message (27) comes up. I also haven't backed the phone up since last year. Help

My iphone 5c says connect to itunes. It won't update/restore; error message (27) comes up. I also haven't backed the phone up since last year. HELP.

Hi there owain11,
It looks like that particular error may be realted to a hardware issue. Take a look at the article below for more information.
Resolve iOS update and restore errors
Check for hardware issues
Related errors: 1, 3, 10, 11, 12, 13, 14, 16, 20, 21, 23, 26, 27, 28, 29, 34, 35, 36, 37, 40, 1000, 1002, 1004, 1011, 1012, 1014, 1667, or 1669.
These errors mean that your device or computer may have a hardware issue that's preventing the update or restore from completing.
Check that your security software and settings aren't preventing your device from communicating with the Apple update server.
Then try to restore your iOS device two more times while connected with a cable, computer, and network you know are good.
Confirm that your security software and settings are allowing communication between your device and update servers.
If you still see the error message when you update or restore, contact Apple support.
-Griff W.

I am trying to download the update IOS 5 version for mi ipad 2 and at the end when it finishes downloading it shows an error "connection has been interrupted and that the task could not be completed", my internet service is fine, what can it be?

I am trying to download the update IOS 5 version for mi ipad 2 and at the end when it finishes downloading it shows an error "connection has been interrupted and that the task could not be completed", my internet service is fine, what can it be?

The 2nd generation can not be upgraded beyond 4.2.1.

There was an error connecting to the update server.

There was an error connecting to the update server. Check your network settings and try again.
am i along with this?
airport utility 5.4.2 can`t get a new update 7.4.2

Ok. Got it fixed.
For a real fix:
Try trashing the ~/Library/Application Support/Apple/AirPort folder. This should solve the problem this time and next time.
If you are reluctant to do that, log into your 'test' account. (You do have a test account, don't you?)
Do the update from there.
Apparently we have something corrupted in our support directories for the AirPort device.
I first fixed my problem by doing the alternate log in method and found that all 3 of my devices were needing a firmware update but only the Capsule was reporting an update within my own account.

HT201263 An error has occured while updating software. Connecting to the server is slow and games etc only run for 60 seconds

An error has occured while updating software. Connecting to the server is slow and games etc only run for 60 seconds

Have you tried resetting your iPad? You may have to restore again if there was a problem.
Try the reset first.
Reset the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider - let go of the buttons.

Hello.I wanted to upgrade my iPad 1 to iOS 5.1 Over the Air.I was running iOS 5.0.1.It said it had an error connecting to server.It is already 5 hours i cant install this update.I also have an iPhone 4 with iOS 5.0.1 with the same issues.Help please!

Hello.I wanted to upgrade my iPad 1 to iOS 5.1 Over the Air.I was running iOS 5.0.1.It said it had an error connecting to server.It is already 5 hours i cant install this update.I also have an iPhone 4 with iOS 5.0.1 with the same issues.Help please!

You're probably running into the servers simply being swamped. Thousands of people are all going for the software update at the same time. Give it a try again and if that doesn't work, then try plugging it into your computer and trying it that way.
I didn't get a notion of the size, it doesn't seem to be as big as the 700 meg 5.0 update, but it did take me 20+ minutes to download via cable internet so it's a large file. That in and of itself takes a while.
If you're trying to download it directly to your iPhone, you'll need to be on wifi since I'm sure it's well over the 20 meg file size limit for 3G.

Update vault errors connected to Spotlight rescan?

Similar Messages

Maybe you are looking for