Hello,

I have been having problems with both Indesign CS3 and CS4 and exporting large documents to a PDF-file. Exporting halts with error messages like: "Failed to Export the PDF file" in CS4 or "Error encountered while reading JPEG image" in CS3.

Problem can be corrected by simply closing InDesign and restarting it and opening the same file again. It appears that problem occurs more often the file is large. Any suggestions how to fix this problem?

I'm using Vista 64-bit and have 8GB memory.

How much free space on Drive C:? Emptying the temp folders may help.

And I also get error "Error encountered while reading JPEG image. Image may be damaged or incompatible. Resave the image with different settings and try again." when Exportin to PDf.

And if I just save/quit/reopen, I'm able to export the pdf fine. Sometimes I have to close other programs, before I'm succesful.

Free space on C is 20.7GB.

I have a vague memory, too that there are problems with JPEG2000 files, but that doesn't seem like the problem if you can get the same file to work after a restart. Empty the temp folders and see if it helps.

In terms of Vista 64-bit, InDesign only runs as a 32-bit applications meaning that it only has approximately 3 gigabytes of virtual memory available, regardless of how much physical memory is available on your system. Only 64-bit applications, such as Photoshop CS4 can really take full advantage of the 64-bit addressing.

I also encountered similar problems with exporting PDF from very large documents with InDesign 5.0.x on all versions of Windows. That problem seems to have gone away with InDesign 6.0, at least for my very large documents. I suspect that there may be some process memory leak problem that you are encountering. What got me around those problems was (1) save early and save often and (2) exit and re-enter InDesign before performing such large exports, making sure that you don't page through the document prior to doing the export.

- Dov

Every time we open a document that was created in InDesign CS3, edit it, and try to export or print it, we get generic failed errors. Whether printing to a printer or Acrobat, or exporting a PDF, we always get a failure.

We've discovered that if we go through and manually re-link all of the links, it fixes it.

Wow... what a dumb bug, and one that has cost us a horrendous amount of time on large projects.

Adobe, please release a fix for this immediately.

Thank you.

nocfurry: This is a user-to-user forum. Adobe reps don't necessarily 
read these posts. No one here is going to release a fix. If you think 
you've found a bug, please report it at

http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

I've opened plenty of CS3 files with linked graphics in CS4 and I 
haven't seen any errors. Do your linked files reside on a network?

-- 
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

Thanks Kenneth - there is a post on this thread from someone claiming to be from Adobe however.

Yes you're right; we just realized this problem is far more severe than simply a CS3 compatibility bug. This is an intrinsic design flaw in the InDesign linking system. We used to use Version Cue CS3 until they unleashed VC4 upon us and nearly crippled our entire studio with that nightmare of a release. So we moved all of our data safely onto a shared network drive before we lost anymore of it in VC4, and apparently that's what has caused the linking problem. InDesign does not have relative links, and it does not properly indicate that it's the links that are causing the problem, leaving us to fend for ourselves and eventually figure out on our own that we have to re-link everything.

Disastrous. Someone needs to be fired.

      InDesign does not have relative links




ID is smart enough to look in subfolders of the folder in which the document is stored, but how would you expect any application to find a link with an unspecified path on an external server? There's no way you'd be sure you have the right link if there were multiple files with the same name, which is not that unusual.

      and it does not properly indicate that it's the links that are causing
      the problem




Actually, it does. You should have received a warning when the file was opened that the links were missing. I know because that feature was missing in early pre-release versions and I fought a hard battle to get it restored. Missing links are also highlighted in the links panel and in pre-flight. If you don't know you have missing or modified links it's because you've turned off features and ignored a warning on open.