aperture library not showing in mail, iweb or iphoto

Got it ! I change the iLife sharing setting in the preference from "when leaving Aperture" to "always" and now it works.
Anyway, the iLifeShared folder is always recreated on my iMac while on my MBP 15", with the same library (a copy of it), this folder doesn't exist nor is created... still a mystery.
Thanks again for the help.

u.c.h. wrote:
Well, I fixed my problem now. I deleted the file "ApertureDatabaseTimestamp" in the folder "iLifeShared" and tried it again - and don't ask me why, but it worked perfectly (without even creating a new file with the same name)...

I also had this problem and deleting the ApertureDatabaseTimestamp file did indeed solve the problem. I don't know how you managed to figure that one out, but I'm glad you did!

Later, the problem recurred and I realised that, in my case, it is to do with using the new Adobe Photoshop Elements 9 software and using the media browser within this software to open an Aperture 3.1 library. I guess this might be a compatibility problem ...

It would be interesting to know if anyone with this issue sees messages in the Console during the timeframe where the Aperture library doesn't display in one of the iApps. Launch Applications>Utilities>Console and in the filter field at the top of the window, search for Aperture or the iApp you were trying to view the Aperture library with. Post any messages you find.

I already had the sharing setting set to "Always" and that didn't help, the file would reappear as soon as I would do any edit to any photo. I finally changed the permissions on that annoying iLifeShared so that I don't have permission to write into it and now it seems to work. I'm just not sure when I'll be adding pictures if they're going to show up in other apps, though...

I too did all you described include deleting the timestamp file, repair the database and permissions but still no luck. At repair of database some errors were found and repaired. Before I had some continue syncing of my mobileme galleries. That disappears after repair. But iLife support still not working.

Any ideas?

Beside of that, my library resides on a separate volume and this volume has disabled access settings – all owners of files are ignored, so I can not change the owner or write permissions.

Message was edited by: Adrian Wackernah

Setting the sharing option to "always" solve the problem... yesterday.
Today it is not working 😟

I tested a bit more and created a _new empty_ library in my home/photos directory and after quitting of Aperture and Mail, restarting Mail I can see in the photos preview window of Mail now the previews from the just created new Aperture library.
Then I created a new library on my second hard drive from scratch and well, it worked too. All fine.

Then I went back to my original library, selected some projects and exported them as a new library were all projects are collected into one library. Thats worked too. After a while, as all previews were made in Aperture for that new library, whole library could be seen in iLife Apps like Mail or iWeb.

Now I am on my way in exporting all other projects from my original library to a new one. This will take some time, so I will report later if it works.

Further to my forum post from last night, I have done some more of my own research and the following is now highly replicable:

1. Firstly, I'm not now so convinced that my installation of Photoshop Elements 9.0 had anything to do with it (although the fact that I had updated Elements and Aperture within a day of each other left me wondering ...)
2. Like forum contributor NemesysSoft, I also then found that it wasn't good enough to just delete the file ApertureDatabaseTimestamp. I actually had to take away Read/Write permissions to the iLifeShared directory. Basically, everything works fine until Aperture writes again the ApertureDatabaseTimestamp file to that directory and then, upon reload, media browsers in any application 'hang' upon trying to read my Aperture library.
3. The problem appears to be only replicable on my main Aperture library. If I switch to a very much smaller library (created just for test purposes) and do some work in that, although the ApertureDatabaseTimestamp file is created, it doesn't appear to have an adverse effect on the media browser which does then display the files in the smaller library. I'm not so sure that I want to consider exporting the whole of my existing 80GB main library to a new library just to see if this is going to work!

I have not (thus far) come across any adverse problems with the work-around solution of denying write access to iLifeShared yet.

Well, now I created a new library and imported my old one into the new. That took me over 6 hours as the library was about 300 GB in size. The new library is ok, all runs fine but only iLife support doesn't still not work.

Another new library with only few projects imported from original library with about 30 GB in size works fine - the iLife support does work.

Any ideas? Do we need iLife 11 for using Aperture Library in iLife apps?

Message was edited by: Adrian Wackernah

@Adrian
No, iLIfe '11 shouldn't make a difference in this (though its a good idea to update _often used_ apps to be of the same generation). Its not the iLife apps where the problem resides tho.

Its more likely somewhere between a piece of software all the apps share, called the iLifeMediaBrowser framework and how its interacting with your original upgraded Aperture library. Something used to work fine with the way Aperture 3.0.3 shared but not with the way Aperture 3.1 is.

I think you are on to the solution to the problem in your experiments. If you were to add a few projects at a time from the larger failing library to the smaller newer working library, I think you would hit a point where your sharing would start to fail. That would point you towards the trigger of the problem.

Or if you continued to parcel out parts from the failing large lib into smaller 30-50 GB chunks you would eventually make one that failed like the larger one. Something then in that last batch will probably be the culprit (ie, written something not right in the database that is now incompatible), something that Rebuild is not correcting. If you can narrow it down enough, you could be able to ultimately remove it, and unclog the sharing.

Thank you for this thread, I also found I couldn't access the Aperture Library from the media viewer in iLife apps. Deleting the timestamp file did the trick, but I also had to apply a read only setting to the folder.

Cheers

Andy.

I have the same problem after the upgrade, tried delete "ApertureDatabaseTimestamp"
but after a while, the folder was somehow recreate by the system, and again it wasn't shown in anywhere. Delete it again and it seem to work for the moment.

I had the same thing, you need to change the permissions on the folder to 'Read Only' (use Command-I, and unlock the padlock at the bottom of the info screen, change permissions on each user).

Check out this thread and see if it helps—

http://discussions.apple.com/message.jspa?messageID=12480932#12480932

I've changed the permissions and still haven't had any luck in getting Mail, the Web, or anything that can use iLife sharing to see my whole Aperture library. This is happening on two computers for me. I'm surprised this isn't a bigger issue for Aperture owners. The only workaround that I could come up with is export the photos you want to email/upload and then go from there. It is a shame I can't do it through the sharing browser though.

Has anyone found a bulletproof solution yet?