Aperture 2.0 Upgrade WARNING - Network Libraries No Longer Accessible

Question

I just upgraded Aperture 1.5.6 to Aperture 2.0 and can no longer access any of my Aperture libraries.
I'm using Aperture on a MacPro workstation running 10.5.2 connected to an Xserve AFP fileserver running 10.5.2 connected to an Xserve RAID via Fibre Channel. I've been using this same exact configuration with Aperture 1.5.6 and earlier for about a year with no problems.
Upon upgrading to 2.0, I went to launch one of my libraries. Aperture notified me that the library needed to be upgraded to 2.0 and I selected "Upgrade". Here's where it went bad. Aperture 2.0 returns an error message saying "Aperture cannot access this library. To use this library, make sure it is on local disk and file permissions are set correctly."
I checked my file permissions and everything is good. I called Apple support and told them the situation, asking in somewhat disbelief if Apple was actually saying that only locally attached drives will work with Aperture thus requiring users to drop another 15-20K for another RAID to be just attached directly to the workstation. The support person told me that it appears to be the case with Aperture and they weren't sure why my configuration had worked without problems before.
If this is in fact true, how Apple could create a product which uses TBs of storage for high volume photographers shooting in RAW and does not allow the use of network storage strikes me as a bit ridiculous and in complete ignorance of some of the demands of how high-end pro users work.
The case is being escalated through Apple support but the cautionary tale here is do not upgrade to 2.0 if you use network storage and make sure to make product requests to Apple to support this essential feature.
For the moment I'm left with uninstalling 2.0 and going back to 1.5.6.
If anyone has any nuggets of wisdom or workarounds on this issue, they'd be greatly appreciated as I'm not to hear back from Apple for at least a few days.

Answer 1

So are you saying that you have a library file with the images imported into it (not referenced) sitting on a fileserver on your LAN that you can access from Aperture on your desktop machine?
With the problem I'm running into I can't even create a brand new library file on the fileserver from Aperture but it works fine on a local disk. This rules out the possibility of it being isolated to a damaged or unrecognizable library, I would think.
I'm going to try some of the other ideas listed here over the next couple days and will post the results but what I'm afraid of is that there is something in 2.0 that actually recognizes it as being on a fileserver as opposed to a local drive and cuts it off. While this may not have been supported in 1.5.6 and before, it did work and reliably from my experience.
If this doesn't work or get fixed by Apple soon, having to manage an ever growing collection of multiple TBs of photos spread across more than 15 Aperture libraries and needing server grade HDs with RAID 5 for data protection and uptime, simply becomes untenable in terms of hardware costs and having to buy an entire other RAID just for a single workstation, which seems to be the only solution at the moment.
The only local drives I use are for scratch disks for when working with Final Cut Studio and even then all the other video files are managed on the RAID through the fileserver and it works fine with Apple's Final Cut Pro and DVD Studio Pro. I'm going to deploy Xsan later this year and possibly increase our Fibre Channel deployment to select video workstations but I have a feeling even this would run into Aperture 2.0's apparent limitations and the expense that requires only makes sense because of the bandwidth demands we have for video, this should not be an issue for still photography.
Has anyone worked with Aperture libraries over Xsan?