1 person found this helpful
Thanks for posting this Eugene.
An additional comment about "fixing" problem text:
I often have very good luck replacing text that is causing file crashes using InDesign Tagged Text, which will preserve the formatting. To export tagged text you must have some sort of active text cursor, either a selection, or just a flashing cursor in the story. With an active cursor InDesign Tagged Text will become an option in the "type" dropdown when you select File > Export...
If you have selected some text, only the selection will be exported. A flashing cursor with no text selected will export the entire story, even if it is threaded across many pages. You will have two options after choosing tagged text and pressing OK in the dialog, abbreviated or verbose, and it doesn't seem to matter which you choose, other than a small difference in the size of the text file that is saved. To use the tagged text file you place it, in the same way you would place a Word file or other text file, but ID will interpret the internal tagging and bring it in formatted.
I will often replace an entire story this way, but on occasion I've also found it works well to export either the entire story, or just a selection of a section I've identified as a problem, then place the tagged text file on the pasteboard. From there I will copy the text I need and paste into position replacing a problem paragraph or two. This seems to give an added layer of cleanup without losing the formatting.
I actually developed this technique a few years ago working on a file that was causing problems for Eugene, but I'm not sure he remembers.
Oh I remember that file for sure. I wasn't aware or I forgot the method Peter used. Thabks for the step by step. :)
Some good advice here too http://forums.adobe.com/message/5468426#5468426
Dov Isaacs wrote:
There are a number of issues that can cause the failure you experienced.
One is obviously some type of dodgy content. Peter and Eugene have given you pointers to how to track such an issue down.
However, it is possible that at least with the 32-bit versions of InDesign (CS6 and earlier), you are simply running out of address space for InDesign and its core technology components to complete the PDF export. I have personally experienced this problem with long and complex documents. (This has nothing to do with how much actual memory you have installed!) The workaround I found for exporting PDF from such long and/or complex documents is that after I am done editing, I save the file and close InDesign. I then restart InDesign and open the document. I immediately invoke the export function and don't attempt any other operations before the export finishes! Do not page through the document. That uses up valuable address space and memory used by internal components.
If that doesn't work, ascertain that you have enough work space on your disk. PDF export can use significant amounts of temp space. (Under Windows, make sure the disk volume that has the TEMP directory has plenty of spare capacity!)
Addition to FAQ
Recently had an InDesign Book fail to print or make a PDF.
I went through my own procedures to identify the problem - didn't find any reason for it to crash.
Create a New Book file.
Then import the files into the new book file.
Everything worked fine.
other ideas welcome
One other thing to be aware of when exporting an InDesign file: all parts of the file MUST be locally saved / available.
I have everything saved on my SkyDrive, and the export kept failing until I made all parts of the file (links, etc.) available offline. Once I did that, the file exported perfectly. I am not sure why this is an issue, as InDesign reported no errors in my project, until I had to export the design for approval. It was blind luck that I tried offline availability; no searches brought up that as an issue.
If you are still having issues, I hope this may help!
I have tried exporting only a few pages, and different combinations and it still crashes. Is there any other workaround you might suggest so I can make this a InDesign file a PDF
You're going to need to isolate and repair/replace whatever is on a page that fails to export. Read about Divide and Conquer strategies above...
I am rebuilding the doc. Fortunately it's on 22 pages. I add a page, export to a pdf and so far it works. Only on page 7 right now. I figured that is the only way to isolate where the conflict is coming from since the original doc crashes every time I try to export as a pdf, whether 1 page or more.
I had the same problem, wound up exporting my CS6 doc to PostScript file first, then dropping PostScript file on Adobe Acrobat Pro. It made the PDF from there, was only workaround I could come up with. Believe its glitch in CS6. Not sure if those using CS6 off cloud are having the same problem. Hope this helps.
That is such an archaic workflow - and I do not recommend it.
Your file could have been fixed and exported to PDF - there would have been a way.
Anyway - you got a very basic PDF with no colour management in it all now - good luck with the colour reproduction... sorry for being harsh.
I rebuilt the InDesign doc page by page then exported to a pdf. All worked until I got to the corrupt image, then it crashed. I had placed an ai file directly into the InDesign doc instead of changing it to a jpg. Once I changed it, which also made the image file smaller, I was able to make a pdf no problem. Just took a while to go through each page at a time. Wish there was a way to detect a corrupt on non working image.
Thanks everyone for you help.
Changing it to a jpeg is not a great solution, there was probably something wrong within your .ai file that we could troubleshoot if you still have it.
But saving it to a jpeg removes the vector goodness that gives a much better output.
Alternate to this saving to PDF would have been much better.
I had a basic black and white document, no color. With a "to printer" date that could not change. The message I received from Adobe was "Adobe has found a solution to this problem, click here". Perhaps if the click here had taken me to that solution my discussion would not have been necessary.
I really don't know what you're referring to.
Rather then performing so much R & D on the PDF file. I think going with an automated tool would be much better for you. I had shared a solution to repair corrupt PDF files few days back on this forum. You may fix all your PDF issues in a click. You can follow the the article to Repair PDF files, mentioned on Microsoft. This could be a turning point for this thread. I hope you get your solution.
You've missed the entire point of this thread. One cannot "fix a corrupt PDF" if there is no PDF produced. The point of this thread is to help users find the problem in InDesign that prevents it from making the PDF in the first place.
Even still - it could come in handy for someone reading the thread anyway.
Sure, but it's off-topic and won't help with getting ID to make a PDF.
I totally agree - can you separate the threads and split to fix?
I suppose I could, but I don't think the post makes much sense without the context of this thread.
I need help. My problem is that when I export file into pdf I can't do anything with the file because it the export window stay up the page and could't be changed. The window cling at the page and export doesn't work.
Here is print screen of clinging window.
How can I solve this problem? Thank you!
Try turning on the Application Frame.
I am printing just one 24x12" in page. Most pages are just photographs. All images are saved as encapsulated post script (EPS) files. There are a few pages with text. Each completed page is roughly 2MB. I have installed as much RAM as possible when I purchased the computer.
Sitting next to the MacBook Pro is an iMac. I can print from InDesign on the iMac. When I purchased the MacBook i migrated the application software from a previous machine. Is it possible that I need to completely reinstall the entire creative suite from scratch?
It's probably text related, then. Have you tried exporting in halves, then halves of the halves, to locate a problem page?
I am having the same troubles. Did anything work for you?
I have found that saving the INDD file as an IDML file and exporting a PDF from that works but it is still a convoluted work around since now I will have to do that if I want to edit any file I've created since this update.
1 person found this helpful
I have discovered after much tinkering that if you relink all your links it will work. I don't know why this is since none of the links were broken, but once I did that everything seemed to work fine.
I ended up just starting the document from scratch as I couldn't figure out what was causing the issue! Thank you for the tips, I'll try those if it happens again.
2 people found this helpful
Here's what worked for me for a book originally built in CS 5.5 with only 1 link / image file.
1) I relinked the graphic, just to be safe
2) Preflighted book and got the go-ahead on every single file
3) When exporting the book to PDF, I selected the print option rather than the interactive option (which is what I needed anyway)
4) Then, in the second dialogue box, I changed the Adobe PDF Preset from "High Quality Print" to "PDF/X-a1:2001"
Yes that can work sometimes - but I strongly suggest that you try to find the problematic pages.
You can start by making a new Book file and adding half the pages.
Export with your normal settings and see if it progresses.
Then try with the other half of the files.
You may be able to narrow it down to a file this way.
Once you have the file narrowed down you need to divide and conquer again - halving the amount of pages as described in the opening post.
It's a long process but it's worth finding that file that's causing the crash.
I found the offending image
and just renmed and resaved the image
Cause of Problems with InDesign because of Strange Filenames when Making a Package.
Any Filename that uses ( ) / \ characters (and there maybe others) that will cause the Package to Fail.
I used to have a screenshot utility that saved filenames with: “Screenshot (02-20-2017-1802) ” This will not work when making a Package! Rename to: Screenshot_02-20-2017-1802
Also avoid Spaces at the Beginning of FileNames... Slashes / are subdirectories or indicate pathnames on PC or Mac so don't use them either... Underscore _ Spaces or Periods . or Hyphens - are okay.