Q: Library Will Not Connect to Images on Remote Drive Since Lion

Jakk,

jakk wrote:

 

It's with any library that resides on the external. And it affects both referenced files (on externals) and managed files (on externals). I don't think it matters whether the referenced files are on the same drive as the library, but in all of my cases, they are on the same drive. Libraries and images on my internal drive don't appear to be affected by this problem. 

 

I get a permissions error message (cannot access System Trash) when trying to delete externally-referenced images from an external library. I do not get this message when deleting managed files, but ... the managed files do not get moved to System Trash either. They physically remain in the library despite all efforts to remove them through regular Apeture commands. So,  effectively, there's no way to permanently delete images through Aperture with these permissions issues at play.

 

I tested it on all external drives and troubleshooted to the best of my ability with various fixes. Couldn't get it to work. The problem goes away entirely when I revert to Snow Leopard.

 

(I should clarify that I don't have a ton of libraries. I created several test libraries to see if I could replicate the problem.)

 

Message was edited by: jakk

OK your issue is different, and I do believe it's a new Lion problem. A similar problem exists with Final Cut Pro X, when you delete a project that's on an external drive, you get an error that you won't be able to undo because trash isn't supported, or something like that.

I've been told that this issue is because external drive simply don't support trash, but I have a hard time believing this. I haven't had the time to troubleshoot it myself. If you're so inclined, I'd say first to ensure that "ignore ownership on this volume" is enabled in the external drive (get info on drive icon and select there http://screencast.com/t/hYq8vhxWZUgo ), second repair permissions on the Aperture library (command-option on launch) AND on the drive itself with Disk Utility (probably do the drive first), and finally if that fails, try reformatting the drive under Lion.

These are merely suggestions, what I would try if I were so inclined to go down this path.

Feel free to post a question at www.ApertureExpert.com/forum as well—some of the folks there may have some ideas.

-Joseph @ApertureExpert

www.ApertureExpert.com

I can confirm that using an Apple server also has problems.  At least, Aperture running under Lion does not find the server where referenced files are stored.  I was using the Snow Leopard server and upgraded to the Lion server in trying to solve the problem, but that did not help.

    Although I see the comments from people who are more knowledgeable than I, explaining and confirming the problem with network servers, the Aperture 3 manual does support this use.  I purchased an Apple server specifically to house referenced files. 

   I plan to use the work around that I posted earlier, but I hope Apple will address this issue at some time.

Tom Cooper

Tom,

Although I see the comments from people who are more knowledgeable than I, explaining and confirming the problem with network servers, the Aperture 3 manual does support this use.  I purchased an Apple server specifically to house referenced files.

really… would you mind locating this in the manual and sharing it with me? Please email me directly at joseph at apertureexpert.com (I'm gonna unsub from this thread, I just don't have time to keep up on it). I just did a quick scan and couldn't find the reference. If it really says that, then I've got some hard questions to ask.

thanks!

-Joseph

A Read Only storage point would satisfy my questions and concerns of exposing the Masters, but how would you add new images to that file or originals?  So far I have seen nothing to limit the access to a server to only be Aperture, and not other apps that might alter the Masters?

From what I can google about LR, it could only do this after LR3, and then not everything looks easy.

Ernie

This is exactly what I was doing with Snow Leopard on my Windows Home Server. The admin account had write access to the "images" folder ! I used that account when importing files to the network.

For everyday use I was using another account with only read access to the "images" folder...

It was running fine until LION :-(

I'm trying to get around the issue with referenced files on a network drive under Lion, I copied the referenced RAW files (2TB) to an external firewire raid drive and connected the drive to my Mac with Aperture running.

Then I started the task reconnect referenced files for about 100.000 photos in the Aperture library.

The process is very slow and the CPU load Aperture is producing in the Activity Monitor is allways above 100%.

It looks like it will take about 20 hours to complete this task.

Was is that slow before Lion, too?

JO

I have the feeling that bad publicity might be the only language Apple understands.

My two star review of Aperture is now the top review in the German app store, telling each end every potential customer of the issues and of Apple's no-official-answer-no-matter-what policy.

I encourage all users concerned by these issues to do the same in the U.S. and other stores.

Cheers,

S.

Indeed, stephubik. 

I encourage all to submit feedback AND to contact the Mac App Store demanding for a full refund.

En masse, we will no doubt be heard and the issue will be addressed.  I have not received a refund, but at least my voice was heard and they escalated the issue to a "senior professional applications engineer".  The engineer I am in contact with is aware of this thread (and several others that I referenced) and is looking into the issue.

They admit to not having a fix but will get back to me with the ultimate resolution.

jlinaschke wrote:

 

Tom,

Although I see the comments from people who are more knowledgeable than I, explaining and confirming the problem with network servers, the Aperture 3 manual does support this use.  I purchased an Apple server specifically to house referenced files.

 

really… would you mind locating this in the manual and sharing it with me? Please email me directly at joseph at apertureexpert.com (I'm gonna unsub from this thread, I just don't have time to keep up on it). I just did a quick scan and couldn't find the reference. If it really says that, then I've got some hard questions to ask.

 

thanks!

-Joseph

Looks like you are right.

After searching the Aperture manual, I also couldn't find any information about referenced files on network drives.

Looks like Lightroom is doing a better job regarding photos on network drives.

JO

I DO have the very same problem here!

Running 10.7.0 with Aperture 3.1.3 and Synology DS409 and DS411+ II (runningy latest DSM 3.1) NAS server on 1Gbps LAN here. Almos every project in Aperture says that masters (that I store on NAS, library is on iMac's HDD) are offline.

My library has more that 77k photos. Cannot imagine to reconnect every single project.

It needs to be fix extremely fast. It is for me, as a professional photographer, painful complication!

The worst is yet to come: Even if you reconnect every single project, Aperture will have forgotten about it by the time you start it up again.

I've requested a refund. Regardless of all the talk about "do not put your library on network servers" (which we did *NOT* do) and how the use of referenced masters on network drives is not encouraged anywhere in the manual (but it's not discouraged either), there's no way we could have anticipated that Aperture would effectively cease to function correctly after the update to Lion.

There is a note about this issue on compatibility on roaringapps... http://roaringapps.com/app:239

A reply from my CSR regarding my tech support case...

"I did send up your case and there have been other reports of this issue, so the software engineers are aware of it.  It should be fixed in an update.  I'll let you know when I get a status update regarding this."

And like usual, they offer no timetable.  I like the word "should" since it doesn't imply that it will necessarily be fixed.  LOL

Oh these crazy tech support reps!