Start by doing the standard troubleshooting:
(1) In the file that exhibits the problem, save your InDesign file as IDML to fix a possibly corrupt document and reopen, then repeat the PDF export. Here's how:
If that doesn't work, try this:
(2) Restore your InDesign preferences. Here's how:
Thank you for the post.
I am sure the ID file is not corrupt. We can just remake the PDF without doing anything and it will be fine again. That is what makes this a big problem... you don't know when it is going to happen.
I agree with you if we could keep replicating the issue it would be easier to investigate!
Does this only happen from one computer?
When the problem happens is the file residing on your computer or on a file server?
Only one Mac so far.
Our storeage structure is like a file server but it is basically a 2nd HDD in the Mac that we call 'Andy Work Disk'. So, the application files and everything are on one HDD and all our software is on the Mac HDD.
Hope that makes sense.
Steve, can the PDF file be 'interrogated' to see if is gives any clue why a pages is not there?
I'm more of a software person than a hardware person. I'm going to let others help you from here. If it's on one computer, I'm suspecting that there's something going on with that computer, but I don't really know.
Even if the file seems uncorrupt, I'd still follow Steve's advice and "wash" the file through IDML. If the file's formatting was based on a series of old jobs, I might even try saving it as an ID template first to remove XMPmmHistory metadata (which can build up amazingly in IDCS4).
I think of novels as generally being fairly simple text, unencumbered with footnotes and cross-references, but I once had odd things happen when exporting to PDF a 500-page file with 2000 cross-references. I usually use ID's Book feature to break jobs that size up into smaller files, but cross-references are said to be more reliable within a single file. I didn't lose whole pages, but a dozen or two footnote numbers (out of hundreds) were changed, seemingly at random. Happily, Acrobat's PDF Comparison flagged the changes on pages I thought didn't needed re-proofing. This happened just once, and for lack of a better explanation I assumed I'd overtaxed IDCS4/Win7, perhaps squeezing its memory by working on another task during ID export.
Hi Steve and David,
Thanks for your posts.
Steve, It has only happened on the one Mac 'so far'. The other isn't used to the same extent so it could happen but hasn't yet! In any case, thanks for your advice.
David, Hi, the ID file did initiate from an ID template file so should be clean of anything. It is one we use very often so I would have expected more problems if it was that. We have though re-saved it as suggested. It can't do any harm.
So surprised that we are the only ones this is happening to!