Skip to main content
Inspiring
November 17, 2009
Answered

Package. . . Cannot copy necessary linked file(s)

  • November 17, 2009
  • 20 replies
  • 81968 views

I created a publication based on a previous one. It's in a new folder with the default [fonts] and [lins] subfolders. Preflight shows no linking errors. Since there are numerous unused graphics in the link folder (from the old version), I wish to create a new package before sending to production. I get the above error with no explanation. How do I do this without manually copying every link (70) and font (46)?

This is CS3 on Vista Home Premium.

Correct answer rivet-sBGFMg

I had a image file with a forward slash ("/") in the name that was causing the issue for me.

20 replies

Participating Frequently
March 20, 2026

I’m running Mac OS 26.3.1 and InDesign 21.2.   I have 214 pages I want to package. I found a fix for us. I couldn’t package a single InDesign file, but if I created a book of multiple files it works. Best to not do more than 20 pages though it takes FOREVER. 

Abhishek Rao
Community Manager
Community Manager
March 30, 2026

Hi ​@MK178,

 

Thanks for sharing the workaround, I’m sure this will really help others facing a similar issue with large documents.

To help us investigate this further and isolate the root cause, could you please confirm if you’re packaging the file locally on your system or to a remote location like a server or cloud drive. I’d recommend trying to package the file locally to see if that makes a difference.

Also, please try embedding all links first, then package the file, and once done you can unembed them again. In addition, move the InDesign file and all linked assets to a simple folder path with shorter names and try packaging again. It would also help to check if any of the linked files contain special characters like a forward slash in their names.

Since you’ve already tried breaking the file into smaller chunks, if possible, please observe if a specific set of pages or links consistently causes the failure.

 

Let me know how it goes, and I’ll take this further based on your update.

Abhishek

Participating Frequently
March 30, 2026

Your request is illogical as that is not how our work flow is. If you’re going to investigate the root cause then you should be following the same set up instead of reinventing the wheel. I am packaging the book’s pages from a server. Why would I put the file locally when I don’t have space to put the 214 indesign docs with the 4 gig of images that goes with it. There is no way I’m going to embed the images when they have to be moved from page to page with each new design. That again doesn’t follow our work flow. There are no special characters as all the images are saved under a 10 digit number and the page is “J123.indd”. I packaged only 20 pages at a time because if you do more it hangs at around the 20 page mark with no error message; just sits there like it’s going to do something but doesn’t. You cancel it and it doesn’t cancel it just hangs. You have to force quit Indesign. I apologize if this sounds like I’m being difficult but it is what it is. You can’t change the game when that may not fix the problem. You have to work with what is given. 

_polygram
Participant
January 29, 2020

My issue was I dragged and dropped an image straight from Mail onto the spread and while packaging it up MacOS was denying the access to the system folder where attachments are stored. After manually copying the picture to 'regular' folder everything worked fine. 

 

Hope this helps someone. 

Participant
May 18, 2019

I was having this issue with CC- no missing links or special characters in file names. I turned off "include PDF(Print)" in the Save As dialogue box and it worked after that. Might help someone else.

Inspiring
May 20, 2019

CJaegle, are you saving the PDF locally, or to a server or other attached volume?

Sometimes it takes a while to write the PDF for larger ID files. If there's a slight hiccup in the server's acknowledge/response to the system, the writing of the file fails. We've experienced this even with single page PDFs. Writing them locally, as part of the package, typically works.

Participant
December 11, 2018

i tried to find link files with "/" but can't find any, turns out its the file path gets too long. try resave the indesign file to another location with less folder hiarachy/ shorter names might help

Caito
Participant
April 18, 2017

I solve the problem erasing the links that was outside de artboard page.

Or, trying export groups of links until find the wrong one.

Known Participant
January 4, 2016

I just received the same error message and have read a dozen threads to find out how to solve the problem. I'm using MacOSX 10.10.3 and InDesign CS6.

I'm currently working on two annual advertising projects that I update once year for over 20 years. Never seen this message before. I've tried all the fixes that have been suggested.


In the one project, I removed all the new elements and then packaged it (advertising flyer). It worked! Then I added each new element one at a time. Each time it worked. Until the final one which had the same font, logos and photo elements as the first time it gave me the error message. This time it worked!  What's going on here?


I'm trying to do the same with the second advertising flyer, but it has many more new elements which will take me longer to package it over and over.


Both of these design projects are done in InDesign CS6. For years I used OSX10.6.8 and never had this problem. Then I upgraded to 10.10.3 a few months ago. Could this be the source of the error message?




Participant
October 16, 2015

This just happened to me exporting a 300+ pg. INDD catalog to Epub from CC2014 (Mac). It would not export from our network, so I decided to package the files and run them locally which is when I started getting the error. All image files met "best practices" for naming conventions so I knew that wasn't the issue. Turns out there was a single rogue image that had become corrupt and caused the export/copy to puke. Resaved the image on the network and that appears to have solved the problem. Hope this info helps.

Participant
September 3, 2015

I have the same problem with InDesign CC.

I discovered that it was a permissions issue. I had a duplicate profile with conflicting permissions. After I removed the duplicate my file packaged fine.

Inspiring
May 11, 2015

late to the conversation, but this is the first time I've ever experienced this error.

Yes, it's due to slashes ("/") in the file names. Changed the names, and the problem went away.

Using CS6, latest updates, on a Mac. Tried packaging to two different server volumes, with full rights and permissions, as well as the local desktop.

What would be _extremely_ helpful was a more descriptive error. Perhaps some sort of error trapping, and a notice that there's an issue with one or more file names, because of characters like slashes and colons. (I'm assuming a colon would cause a similar error.)

chameleon_stew
Participant
April 30, 2015

The problem still exists, I'm using Adobe InDesign CC2014 and a forward slash in a linked file (which I might add was named automatically when I took the screenshot of a website) stopped from packaging the file. Fortunately I found this thread. So thanks guys.

This wouldn't really be an issue if the dialogue box that appeared actually explained what the problem was! Surely that's simple to do right?!

Cheers