Aperture 3 doesn't see Network Drive that holds masters of referenced files

Hi
I created a new referenced library with about 35000 images and for the few days it worked fine. The Referenced files are located on a Drobo that is connected to My Mac OS X server. I connect to it Via AFP.
About 2 days ago, I opened the library and the library does not see the referenced files. When I choose a file and select 'Locate referenced Files from the File menu, the locate window pops up and it shows the Drobo as being offline, even though I have mounted it, and outside of Aperture, I can access it and use it - it is definitely mounted. the "Mount" button is greyed out in the Locate referenced files window, and when I select the file using the file browser in this window, which I am able to do even though Aperture Shows the Drobo as Offline Volume Status section above, the "reconnect button remains greyed out.
I have rebuilt the library, rebooted the server, unmounted and remounted the Drobo, and no matter what I do, it does not see the referenced files.
Can anyone help me recoonect these files?

I am having the exact same problem in Aperture 3.0.2. Aperture says that 529 files in a particular library are "offline" when they are on a mounted volume. The external volume on which they reside is very much ONLINE despite the fact that Aperture says it is offline.
In fact that same volume shows up in the bottom half of the window that pops up when you select the files in Aperture and choose "Locate referenced files". I was able to successfully reconnect several thousand files by simply navigating to the files that Aperture identified as "offline" in the bottom window. But these 529 (out of a total of 4266) won't reconnect and in the bottom window the pixel dimensions for the file I'm trying to reconnect are missing. If I navigate to the files in the Finder the pixel dimensions are shown. I was able to reimport some of the so-called "offline" files on the "offline" volume. There were originally 572 that would not reconnect, and I reimported 43 of them, leaving me with 529 that should be connected, but aren't.
Last week I spent several hours on the phone with the tech support team at Apple, but they so far have been unable to help me solve this problem. I could just reimport the files, but then would have to lift and stamp adjustments for all 529 files and get rid of the "offline" masters. One of the tech support people was going to research whether it might be possible to somehow do a "force reconnect", but hasn't gotten back to me about this.
The external volume on which these files reside is an OWC Qx2 which is a 4.5 GB Raid 5 connected via firewire 800. In addition to being completely accessible outside of Aperture, I have run Disk Utility on it, and it verifies.
I am hoping that Apple will come up with a fix for this problem soon.

Similar Messages

Error saving Project 2010 files to network drive - doesn't see network drive

ANSWERED (11 April 2014):
So it seems the resolution to this is to simply create a new share with a different name. I used the existing folder (to retain NTFS permissions) and just select to Add a new Share (applying the same Share permissions as the non working Shares).
Deploying this new Share via Group Policy as a test resulted in staff being able to open files from Windows Search, save files through MS Project and the Share being accessible through browsing SMB.
All problems resolved by using a new share name for the existing folder. Seems to be a corruption in the namespace.
Note: I had previously deleted the share and recreated it. I had removed all NTFS permissions and readded (through both the GUI and icacls). This didn't make a difference.
Only changing the name of the share fixed the problem.
Original Question
Already
posted here... but Microsoft Support has not responded.
It seems some staff on some computers are having problems saving MS Project files to the network. This is only since an upgrade to SBS2011 (from SBS2003). The only difference now, is that network drives are mapped via group policy rather than a 'net
use' script.
This is affecting users on Windows 7 and Windows Server 2008 R2, with either MS Project 2007 or 2010. The users have full change access to the folders and can create new files and modifying existing files, just not a MS Project file. Other file tyes, e.g
Word .docx, Excel .xlsx, Adobe .pdf files, all work fine. These files can be opened, edited and saved normally without problem.
To replicate this:
The user opens an existing file or creates a new file on the network folder (either through Windows Explorer or MS Project). They then click File > Save in MS Project and receive the following error (see pic below):
An interesting symptom of this is that if you select File > Save As in MS Project, the Sae As dialog box doesn't remeber the path location of the network drive. MS Project instead prompts to save the file in the local users documents folder (see pic below):
If they browse back to the original folder where the file was saved and choose to save it there, they are of course, prompted to overwrite the existing file and they can save the file. But the same thing happens every time they open the file.
It seems the problem is that Project isn't seeing the path of the file or that the network drive is attached.
If a user closes the file without saving it, they are prompted to save the file and the prompt shows the drive path:
Do you want to save changes to "N:\... Projects\Active Projects\CC...\F4 Project Plan File\004 Programme\test project file.mpp"?
But choosing to save the file gives them the same result as Save As, they are prompted for a new location as if the original file location doesn't exist.
I have disconnected the mapped drive and connected it again using net use but get the same error.
I have reinstalled MS Project 201, installed Project 2010 SP2 and installed Windows updates and it does the same thing, exactly the same symptoms.
Further, if the user opens a file from the network drive, the file shows in the Project recent files list. If they try to open the file from the recent files list in project they get the following error:
"Project cannot open the file.
-Check that the file name and path are correct.
-Check that the file format is recognized by Project.
Project files saved in a version earlier than Microsoft Project 98 can't be opened...."
This is a test file that I created on the user's computer and network drive, This is being opened with the same version it was created in. If I browse to the folder in Windows Explorer I can open the file. Of course, I then can't save the file (I still get
the original error). I'm logged on with Domain Admin privileges.
I've checked these links from other threads (neither apply to my scenario):
http://support.microsoft.com/kb/983458/en-us|
http://social.technet.microsoft.com/Forums/en-US/excel/thread/2eeea140-7e6c-4cb9-a89b-06d2102bd9f7/
I've downloaded my TechNet version of he software and installed it with Sp2 and Windows updates and it does the same thing. This also happens on the Remote Desktop server (Server 2008 R2) using MS Project 2007.

Case 1
This error message appears when the document is open on two or more computers that are running different operating platforms. For example,
if the document is open on a Macintosh computer and you open it on a second computer running Windows or Windows NT, the error occurs when either user tries to save the document.
This problem stems from a difference between the ways Macintosh OLE and Windows OLE open files. As a result, you cannot save a file on two different operating platforms at the same time.
Case 2
This error occurs in Word 97 for Windows if you save to a MAPROOT type network drive connection on a NetWare server where spaces exist in
the file or folder name.
Case 3
This problem may occur if an anti-virus program running on a network has the ability to scan for macro viruses in documents in shared network
folders.
For example, if you have the following:
a shared folder on a network server
-and-
an anti-virus program is running on the network server that is set to monitor the shared folder,
when you attempt to save a document (across the network) to the shared folder, the anti-virus checker may cause the error to occur.
Case 4
This problem may occur on Novell networks when the AutoRecover files path is either blank or set to a network drive.
According each, please try the following workaround:
WORKAROUND
To work around this problem, use one of the following methods appropriate to your situation.
Case 1
Method 1:
Move the document to your local hard disk for editing. Move it back to the server after you finish.
Method 2:
Save a copy of the
file with a different
file name, and work on the copy, either on your hard disk or on the server.
Case 3
Method 1:
Move the document to your local hard disk for editing. Move it back to the server after you finish.
Method 2:
Do not use spaces in the directory or document names.
Method 3:
Do not use MAPROOT-drive connections. Map your drive connections to the volume-level only.
Case 4
Turn off the anti-virus protection on the network server and then try to
save the document. Contact your anti-virus protection software company for additional details and/or updates to their programs.
Case 5
Set the AutoRecover files path to your local drive. To change the AutoRecover path, use the following steps:
1.
On the Tools menu, click Options.
2.
On the File Locations tab, select AutoRecover files and then click Modify.
3.
Change the Modify Location dialog box to a
folder on your local drive and then click OK.
4.
Click OK to close the Options dialog box.
Hope that helps.
Smith

Aperture doesn't see proper iPhoto folder structure for Locating Referenced

I've got some photos in Aperture 3.03 that were imported from an older version of iPhoto. I needed to reconnect the Aperture photos to the iPhoto originals, so I searched for the location of the photos with Spotlight, which found them in a folder in the iPhoto package.
But when I select the preview photo in Aperture and go to Locate Referenced Files, I can see my iPhoto library, but when I go to look inside the iPhoto library, the folder structure is all wrong. Thus, I can't find my photo.
What would cause Aperture to misread my folder structure? Is it using an old database of folder structure and how to I reset that database?

Thanks for these two responses. I can see the photos fine with iPhoto '09, version 8.1.2 (424).
Right now, I'm backing up my Aperture vault before moving to Aperture 3.10. Hoping that will give me a chance to solve the problem.

Can't see network drive attached to AirPort

Hi All
I'm a newbie Mac user (just got my MacBook Pro last Thursday, in fact-- OS X 10.5.7). While I've got most of my issues doped out, I'm running into a problem connecting to a network drive that's plugged directly into my AirPort Extreme. I have three Windows systems (running XP and Vista) that can attach to the drive with no problem, but I can't figure out how to mount the drive under OS X.
If I use the Finder and select the router under "Shared", the Finder just spins with the message "Connecting..." for ages until it times out.
If I try to attach to a server, that doesn't work-- I've tried all the protocols in various flavors. Everything times out. I do get the message that the server or password is incorrect, but I never see a prompt for a password, so I am not sure what's going on there.
In short, I'm stumped. When I open up the AirPort utility, and view the disk, the drive is attached-- it has a name, and it gives the correct statistics on used/free space. When I go to File Sharing, the checkbox for Enable File Sharing is clicked.
Any ideas?
Thanks!
-Ed

Well, I'm stumped. I spent an hour on the phone with Apple support-- they ran through the scenarios I had already been through, and they came up with nothing useful. I ended up taking a second 160gb HD that was formatted NTFS, and formatted if for HFS+. This drive was visible through Finder. I took the same drive, formatted it for FAT32 and, surprise, surprise, NOTHING VISIBLE.
The "just works" philosophy is OK, but it's bunk when it comes to network drive support. I'm doubting the wisdom of this purchase now.
$2500 for a computer that can't connect to a network drive that can be seen by an $500 Dell laptop?
The issue simply seems to be this: put a FAT32 drive on another box, and it can be shared by Macs and Windows boxes.
Put that same FAT32 box on an AirPort Express, and my Mac is BLIND. It can't see the drive.

M8530f desktop PC with a m2n78-la mother board doesn't see my drives

i have a m8530f desktop PC with a m2n78-la mother board it doesn't see my drives for some reason. i thought it might be a bios problem. is there any way to fix this or do i need to get another board

Before you begin, disconnect everything from the computer (USB devices, printers, floppy disks, and CD/DVD discs) but leave the mouse, monitor and keyboard connected. You already checked and made sure that the power and data cables have a good connection to your drives and the motherboard now go to your BIOS Setup (should be F10) and reset the BIOS to its' defaults (should be F5 and then press the enter key). Arrow over to the Main screen and the hard drive should be recognized. Exit BIOS and save the changes. The computer should load the Windows OS if it's installed on the hard drive. If you get into Windows, check the Device Manager to make sure that the drive is showing up there too. If the hard drive was not detected, after you save the changes and exit the BIOS, turn off the computer. Disconnect the power cord from the back of the PC then press the power button on the computer for 5 seconds. Reconnect the power cord and turn on the computer and see if it boots up. If it still doesn't boot up, try a different SATA connection on the motherboard (one that hasn't been used). If that doesn't help, disconnect the Memory card reader connections inside the computer and try to boot again. If it still doesn't work and since you already tried a new hard drive, I would suspect a SATA controller/bus problem and you may need to install a SATA controller card to resolve the problem.

Brasero doesn't see my drive, but PCManFM see it...

Hello
I just installed Brasero and I wanted to burn some audio CD but Brasero doesn't see my drive. It says that Brasero will drive my audio project to an iso file because it doesn't see my drive.
My drives works, I've installed Arch with it, PCManFM (my filemanager) see it, and see that I insert a Blank disk...
Any ideas ?
Thanks

Similar thread https://bbs.archlinux.org/viewtopic.php?id=101192
Edit: Do you have hal running?
Last edited by karol (2010-07-17 16:55:01)

I updated to Mavericks and Aperture 3.5. After the update, Aperture doesn't see referenced files. I get "No Referenced Files"

I updated to Mavericks and Aperture 3.5. All my images are referenced on a stand-alone drive. After the update, Aperture displays thumbnails, but I can't edit because Aperture doesn't see the referenced file ("image offline") and when choose all of my images and I run locate referenced files ... I get "No Referenced Files." I don't get the screen to "look" for the files.

Did you make a clean install and restore the library from a backup? No.
Or did you install the new system amd new version on top of the old system? Yes.
What version did you upgrade from? 3.4
Is your Aperture library onyour internal drive or also on an external drive? External
During the update, has your Aperture library been moved in any way? No, its still where it was on the external drive.
Thanks for your help. Ideas?

ESX 3.5u3 doesn't see network after firmware update on x6250

Hello,
We have got several Sun blade x6250 with ESX 3.5u3 with latest updates.
We have updated firmware on one of them from ELOM 4.0.45 -> ILOM 3.0.3.33 recently.
Now a ESX server doesn't see network:
Node ISOLATED form Network. Either repair network or override agent startup ...
I executed embedded PC-Check test, it saw all four NICs and said that they were 'Success'.
Also, I cleared statistic on a Cisco Catalist interfaces where the blade was connected.
After a day 'Receive' statistic is 0
Also, I tried to load the blade with DSL Linux, it didn't see network too.
Do you have any idea concerning the situation?
Thanks!
Regards,
Andrey.

Hello,
We have got several Sun blade x6250 with ESX 3.5u3 with latest updates.
We have updated firmware on one of them from ELOM 4.0.45 -> ILOM 3.0.3.33 recently.
Now a ESX server doesn't see network:
Node ISOLATED form Network. Either repair network or override agent startup ...
I executed embedded PC-Check test, it saw all four NICs and said that they were 'Success'.
Also, I cleared statistic on a Cisco Catalist interfaces where the blade was connected.
After a day 'Receive' statistic is 0
Also, I tried to load the blade with DSL Linux, it didn't see network too.
Do you have any idea concerning the situation?
Thanks!
Regards,
Andrey.

Cannot see Network drives via my router on iMac

I just purchased a new iMac today, set everything up and find that my 2 network drives that are connectd to my BT buiness hub 3 router are not showing in finder and I cannot remember what to do. I have a time capsule as well as a WD Network drive.
They both show on my old iMac (Early 2011) but on my new on they are not in my finder window?
Any help appreciated.

Hello there, welshreduk.
The following Knowledge Base article offers up the steps for connecting to shared peripherals:
OS X Mavericks: Connect to shared computers and file servers on a network
http://support.apple.com/kb/PH13779
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

Windows NTFS network drive no longer able to edit files in Osx 10.9

In the OSX 10.8x and before, the network drive hosted by Windows 2008 server in our .local domain was able to be modified by my imac under a local user account with the same user name without any problem. The only issue was not able to join the AD due to the existing .local domain setup. Upon upgrading to OSX 10.9 today, the network drive still connect properly, and the files on the share drive is still able to be opened, read, copied and deleted as before. However, any attempt to save the changes to the opened file display an error message saying that it is been locked and I have no privilege to modify the file. The funny thing is now that the mac computer is able to join the windows AD without problem, although under the network account, the same problem exited. Something has to do with the SMB right/ share has been changed in this release. Anyhelp on how I may resolve this problem?

I'm hoping you or someone can solve this. We're using Tuxera to add SMB NTFS write capabilities to Mavericks and it works great for everything ... except for iWork 2013. iWork 09 still reads and writes perfectly, as does every other app I have on my Mac.
At this point, I fear using iWork 2013 in a mixed Windows/OSX environment is dead if your server is NTFS. It's another quiver in Microsoft's argument that iWork is for children only. Despite all the griping about deprecated functions in the new iWork, there's no show stoppers as far as I'm concerned, and I use Pages, Keynote and Numbers in serious ways daily.

Mac Doesn't See External Drives on WinPC, PC Doesn't See Mac

I'm trying to transfer some files that are on an external drive connected to a Windows PC to my new Mac Pro.
On the Mac, in Finder, I can see the PC, but I can only see it's internal Hard Drive; the external drive don't show up in Finder.
On the PC, I'm not seeing the Mac Pro at all. In Tiger, it seems to me, there was check box under the "sharing" preferences for "Windows sharing," but I can't find that in Leopard. So, the PC doesn't see the Mac at all.
It does suddenly dawn on me that I could just detach the external drive that I'm trying to copy from the PC and plug it into the Mac, but... that would be too easy. I would still like, at least, to be able to see the Mac from the PC.
Any suggestions?
Thanks,
--PS

My recommendation is to format the drive as FAT32 via OSX's Disk Utility, this will allow you to read/write from both the Mac and PC environment.
Like I said, I don't think that's the issue, because my MacBook shares everything with the PC just fine (except the externals on the PC). And of course, I don't want to reformat the external drives until I've got the data off of them.
I just checked, and Tiger has a "Windows sharing" checkbox under the "Sharing Preferences" that allows the MacBook to show up in "My Network Places" on the PC. The problem I'm having is getting the MacPro to show up on the PC; the Pro has Leopard, and there's no "Windows Sharing" in Leopard that I can see.
Thanks again,
--PS

Aperture doesn't recognise network backup disk

I use Aperture (2.1.4) for processing pictures and back up the vault periodically (learned the hard way) to an external drive connected to my Time Machine. Set up fine under Leopard, the drive was recognised and I could update the vaults using Aperture from time to time. It was necessary to open the external disk via Network before Aperture 'saw' the vault, but that was no problem.
Upgrade to Snow Leopard and Aperture says no vault is connected (even when I have opened the disk using network even though the icon for the disk appears on my desktop).
Do I need to reformat the drive under SL (via a USB connection), reconnect the disk to Time Machine and then re-establish the vault?
Help - as it stands I cannot back up any photographs.

What is the file system on the remote drive?
I am using an Infrant ReadyNAS to hold a vault, but I created a Mac OS X "sparse image" with an HFS+ disk image on it. It continues to work fine on Snow Leopard (I mount the network share, and then double click the .dmg file which then mounts it on my host, and I vault to it). If you have some sort of network drive on something like a LaCie or Infrant or anything that's not formatted as HFS+, I would anticipate problems at some point, as the file system just won't properly handle the names that Aperture uses within its vault.

MMC cannot see network drives

I have just build several PCs with Windows 8.1 Pro for my team. I have a problem with mmc.exe - it cannot seem to see any network drives. When I try to save a custom console, the dialog box only presents the local drives. If I try to open a saved file from
a network drive, I get an error box saying:
"MMC cannot open the file Z:\test.msc.
This may be because the file does not exist, is not an MMC console, or was created by a later version of MMC. This may also be because you do not have sufficient rights to access the file."
If I then move the MSC file to the local disk, it opens correctly.
I can confirm that my NTFS permissions are fine (I can open the MSC file from my Z: drive just fine on my old Windows 7 PC). No matter what I do, though, MMC on the new PCs simply doesn't acknowledge the existence of any network drives. No other programs
have problems with network drives - only MMC. The only thing I could find when searching for the problem was someone reporting the same symptom on Windows 7 after installing the RSAT tools, but there were no answers on that page. The RSAT tools are installed
on my machines, and I have tried uninstalling them, but it made no difference. Does anyone have any ideas?
Thanks,
Iain

I think you are running into a situation due to User Account Control.
As you probablu know, UAC enforces administrators to run as a normal user by default, and 'elevate' to administrative privileges on a per process base. This measn that there are actually two user sessions: the user and the elevated one. each of those can
have it's own mapped network drives.
verify if this is the case by running bot a normal and an elevated command prompt and running
net use to show the mapped drives.
then on how to solve this... this behavior is by design and as expected. you should map your drives twice: once as user and once being elevated.
A possible workaround is to disable UAC, which I would not recommend as UAC is an important security boundary
MCP/MCSA/MCTS/MCITP

PC can't see network drive

I have a drive connected to my Airport Extreme as a music server for my iTunes.
My MacBook and my G4 can connect to the networked hard drive with no problem but I have a PC running Windows XP that doesn't see it. Not in any of the methods listed here -
http://support.microsoft.com/kb/308582
The PC DOES see the AE because it is using that to get onto the net. How can I force the PC to see the drive connected to the AE ?
Thanks

Do you have Bonjour for Windows installed on the PC? That is required to access the drive. See http://www.apple.com/airportextreme/specs.html

Import "Copy To:" choose button doesn't see other drives in Win 7?!

When I click "Choose" beside "Copy To:" on the import photos window I only see "My Desktop" and folders under my Windows username. I can't see any other drives on my system. I've tried both 2.5 and 3 Beta and I've encountered the same issue: I can only import to my C:\ drive and the workaround is to than move the imported files to the other drive in the Lightroom catalog menu. I'm running Windows 7 64-bit now (clean install). Any suggestions? This never happened with Vista... is it Win 7 related?? I can see the other drives in other parts of Lightroom, it's just the Import window that doesn't see them? Anyone?

On Mon, Oct 26, 2009 at 12:15 PM, aar1123 <[email protected]> said:
>
Oh, I see another post with the same issue from a few months back: http://forums.adobe.com/message/2174302#2174302
>
No replies to this thread - hopefully someone knows what to do?
That post mentions a DROBO (i.e., a non-local drive). Is that your
problem, as well? The drive you want to see but can't - is it an
internal drive? External, but directly attached drive (USB)? Some
networked drive?
>

Aperture 3 doesn't see Network Drive that holds masters of referenced files

Similar Messages

Maybe you are looking for