Skip to main content
Inspiring
November 17, 2009
Answered

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

  • November 17, 2009
  • 19 replies
  • 81158 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.

19 replies

New Participant
February 9, 2015

I was having the same problem with a CS6 document and thought it was an issue with my new iMac running Yosemite since I had copied the file from a Mac Pro on an older system. So I recreated a new document, copying the pages from the old file and when I went to package it, it still gave me the "cannot copy necessary linked files" message. So I started recreating the document piece-meal, one page at at time and finally discovered it was a placed pdf that was causing the problem. The pdf file had a / in the name. When I removed the forward slash it packaged the files just fine! I was curious if my old Mac Pro running Snow Leopard would have the same issue but it didn't. It packaged the file with no problems even though the file name still included the forward slash. Guess I'll be careful not to use forward slashes when naming files on my new iMac.

New Participant
January 15, 2015

I was having the same problem. I tried everything listed here... I found that some of my links were saved as RGB and never noticed before, that was causing the trouble. I selected the RGB links and then Menu>Edit With, I opened them in Photoshop and then convert to CMYK. Luckily there were only 11 links, but then I had to go one by one which took me about 10 mins... all my images came from diff places from diff servers.... even worst. After doing that I was finally able to Package the file. So, there could be tons of possibilities that can cause this.

Good luck!

Participating Frequently
October 10, 2014

I should add, that this is SO annoying. My workload does not allow me to constant troubleshoot all my files. Is there ever going to be a fix for this? I have had problem after problem since upgrading to InDesign CC. I'm very close to reinstalling my old CS 5. I never had issues like this with CS 5. Has anyone else been plagued with problems since upgrading?

New Participant
January 13, 2015

I realize these posts are old, but I did a search for this issue of not being able to package a file and this came up. In the meantime, I figured it out for me at least. All linked files also had to be updated to cc files. I had cs6 illustrators files attached, once I reopened in cc illustrator and saved, same name as before, relinked, then try to package again, it all worked. For me.

Participating Frequently
October 10, 2014

I've been having this same issue since updating to CC. After trying a million different fixes, I've found that if you have a really large file and you downsize it in InDesign, it will also cause this error. My example: I had a 15 x 15 inch square, downsized to 3 x 3 inches in InDesign. After resizing the image it to 3 x 3 in Photoshop, problem was solved. Hope this helps someone out there!

New Participant
September 27, 2013

I had the same problem. InDesign CC, Mac OS 10.8.4.

Like other people have mentioned, my issue was fixed by checking the linked files and removing a '/' from one of the file names.

Annoying that this propblem still persits after 4+ version updates!

Participating Frequently
October 24, 2012

Issue is definitely still there in CS6. Renaming any links that had forward slash ("/") in the name did the trick (as per other comments above).

Pity my client has a naming and code system that uses a forward slash and will be impossible for me to change to avoid future issues.

Peter Spier
Community Expert
October 25, 2012

If your  clinet intends to do any work in a modern networked environment they're going to need to learn not to use slashes in file names.

Participating Frequently
October 25, 2012

That's the attitude. Adapt to the limitations of the way that the networked environmnet has been built and operate - rather than aim to improve and become flexible enough to work with characters and glyphs that have been used in communication for thousands of years.

I think i'll stick to complaining until things get easier to work with.

rivet-sBGFMgCorrect answer
New Participant
August 20, 2011

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

BobLevine
Community Expert
August 20, 2011

This thread is two years old and AFAIK this issue was fixed with a patch to InDesign. Make sure you're fully updated by checking under help>updates.

Bob

Jim Kinney AEL
Known Participant
October 11, 2011

One of my students was having the exact same problem with CS5.5 !!! The problem still exists and I suspect that it was as rivet proposed in the previous post. My student was using serial naming 1), 2) and I suspect that it was the parentheses that were generating the issue. I changed one GIF file from indexed colour to greyscale and renamed it without the bracket from 13) maid.gif to "13_maid.jpg" and this allowed the PACKAGING to proceed but it crashed InDesign before generating a copy of the original layout and the instructions file. It did manage to copy the fonts and links. However, on trying it a second time I got the dreaded "Cannot copy necessary linked file(s) error message.

I am going to get her to rename and re-link her files to see if this resolves the issue.

Peter Spier
Community Expert
November 17, 2009

You were moving the new package to a new folder, yes? I can see where there would be some issues in the same folder.

larrycfcAuthor
Inspiring
November 17, 2009

Yes, new folder.

Peter Spier
Community Expert
November 17, 2009

Very odd.

BobLevine
Community Expert
November 17, 2009

Do you have enough room and permissions to save the files to the new folder?

One workaround. Select all the links in the links panel and from the panel menu choose copy links to and select a new location.

Bob

larrycfcAuthor
Inspiring
November 17, 2009

No issue with space or permissions. In fact, I just packaged another publication with no issues. Your work-around is great, didn't know that was there.