I've found a few threads on this issue and have tried trashing my preferences and it didn't work. The problem started as soon as we got a new NAS. We had been using an old Windows 2003 Server for many years and never were there any problems packaging. As soon as we started using this much more powerful and larger NAS, we suddenly can't package anything that has links residing on the NAS. Nothing has changed in our file structure, just the device being used to serve the files. The links reside on the network and are spread over a number of shared folders. Never had problems like this before getting the NAS. Any suggestions?
I know that this isn't strictly an InDesign problem but trying to explain the premise of InDesign packaging and links to a group of NAS forum guys hasn't been very fruitfu so farl so I thought I'd come at this from a different point of angle. Thanks to everyone in advance!
Edit: The NAS is a Synology Diskstation 1512+ with two 2TB drives. S.M.A.R.T. shows the drives to be in perfect working condition.
What version of InDesign, what patch level, and what OS?
There were issues in the initial release of CS5 with links not packaging because of "illegal" characters in file or folder names. Path length may also be an issue, or possibly the protocol used for connecting.
Windows 7 (64bit) running InDesign CS5 7.0.4
I don't think it's any illegal characters because I can copy all links to a new location and then package and it works. Path length would surprise me since the file structure didn't change from one server to the next, but I've seen stranger things happen. The protocol for connecting is CIFS.
OK, the bug didn't affect Windows since the characters wouldn't have been allowed to begin with if the files didn't originate on a Mac, and it was fixed in the first patch, so that's done. I'm not really qualified to talk about network protocols and connectivity, but if you can package from a new location, I'd say ther's a problem inithe path statement.
Can you use the Copy Links To Folder and Relink To Folder commands to relink to a new forlder on the NAS and get it to package?
It had been a week or two since I tried since I left some information out. In order to copy the links into a single location, I first have to embed them and then relink to a chosen folder. I did that and chose the relink folder to be on the server. I then packaged it with the ID file located on my local machine and the links on the server. The result was that it suceeded.
So are you saying the links are all showing as missing until you relink them? I'm guessing not, as I don't know how you'd embed them if they were. Are you able to use the copy links to folder command?
This just keeps sounding more and more like a path problem. Keep in mind that the link is an absolute path, so moving them to a new server is going to break that path. This is a fairly well discussed topic, and there may be some script to help with migration and path change, but you'll have to do some searching unless someone else pipes up.
The links do not show as missing. This file was made and links were placed after the change over to the new server.
I am not able to just use the copy links to folder command. That's why I embedded the links first. I then unembedded them to a new folder.
Just verified all permissions on the NAS as well. My user login has all read/write access to every shared folder.
Not sure if this makes a difference ... the links are spread across various mapped "drives" (network shares that the NAS serves). There is a "T" drive, "N" drive, "M" drive, etc.
This has nothing to do with NAS or any other servers, but I found a simple solution that worked for me. One of my links had a slash in the name. Once I removed the slash and and relinked the file, everything packaged. Worth a try!
Europe, Middle East and Africa