Skip navigation

Background PDF export Help

May 28, 2010 9:26 AM

  Latest reply: John Hawkinson, Feb 22, 2012 2:29 PM
Replies 1 2 3 4 5 Previous Next
  • Currently Being Moderated
    Jun 30, 2010 12:12 PM   in reply to webheads1835

    I'd like to try to get to the  bottom of this and help as many customers as I can, with a workaround,  by driving a fix, or in any other ways. But to do that, I need some way  to reproduce the problem. I'd be especially grateful if one of the users  who had the issue solved by updating their .joboptions could post the  original .joboptions, and a document that demonstrates the problem when  trying to export it.

     

    Anyone who has a case that consistently shows this  problem, try to reproduce it with the fonts and links missing (to  minimize the data you'd need to post) and if that still fails, then post  the file, and your .joboptions which you are choosing when you export.  If using custom settings, save it as a new .joboptions (preset) file and  include it.


    If you need a place to post the files, try our  free Acrobat.com file storage and sharing. Or send me information for  your FTP siste, etc. You can email me directly by consulting my profile  here.

     

    Sincerely,

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 30, 2010 12:51 PM   in reply to webheads1835

    @Steve,

    .joboptions are the file format for PDF presets shared by several Adobe applications. In InDesign's PDF export dialog, if you save a preset, you're saving a .joboptions file. I'll try to give you a call.

     

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 6, 2010 4:01 PM   in reply to webheads1835

    Yeah, I had a file freeze on me today, too. Worked fine once, made a minor change and it froze the next time at 83%. Did an end task on ID, restarted, and it sailed through...

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 14, 2010 4:55 PM   in reply to Peter Spier

    This is sad... Unfortunately, the only solution to this problem (to date) is to "force quit" Indy, and then open the document again. You might get one or two proofs to export, but after that, it's "background task" time 


    However, if anyone comes up with a solution, don't forget to "give me a shout!"

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 14, 2010 5:04 PM   in reply to c kim

    @ c kim, Have a look at this post here, it mentions another one on this forum too, I haven't noticed anyone saying that the script solution doesn't work....

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 14, 2010 6:05 PM   in reply to Stix Hart

    I saw that posting earlier, but I'm kinda "scared" of that "script stuff."

     

    Did you try it? And if so, did it work for you?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 14, 2010 6:10 PM   in reply to c kim

    Don't be "scared" they don't bite!  Work on a copy of a document for complete ease of mind.  Yep, it worked fine, came up with the good old fashioned progress bar, mind you I haven't had half the problems most people are having...  Have a look at this post for some tips on installing them, it hasn't changed in CS5.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 5:22 AM   in reply to Stix Hart

    OK, I think I'm going to try it... However, I have a question (please excuse my ignorance), Once I "select" the code, do I place it in a "TexEdit" page and name it something? And if that's the case, what should I name it?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 5:50 AM   in reply to c kim

    Copy and paste the code into a plain text editor. TextEdit is fine. Save as plain text, but add the .jsx extension. I believe sombody already pointed to a link telling you where to put it once it's saved.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 5:58 AM   in reply to c kim

    Place it in NotePad or similar (not Word or any program that assigns styles) use a basic text editor.

     

    File>Save "<insertname>.jsx"

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 6:04 AM   in reply to Eugene Tyson

    In case of doubt use Adobe's own ESTK editor. It gets installed with InDesign so everyone has one.

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 6:09 AM   in reply to webheads1835

    Here's another suggestion that just popped into my head and if it's been suggested already, my apologies.

     

    Create a new book and add your document to that. Export the PDF from the book panel.

     

    Bob

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 6:57 AM   in reply to Stix Hart

    OMG... IT WORKS!

     

    I even tested it while I had the InDesign doucment "exporting" in the background... ran the script, and the PDF file was generated while the background exporting was still "Thinkin' about it!" Unfortunately, I still had to "force quit" out of the document because it would have been still "thinking" until next Tuesday.

     

    Thanks for the "workaround."

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 6:59 AM   in reply to Stix Hart

    OMG... IT WORKS!

     

    I even tested it while I had the  InDesign doucment "exporting" in the background... ran the script, and  the PDF file was generated while the background exporting was still  "Thinkin' about it!" Unfortunately, I still had to "force quit" out of  the document because it would have been still "thinking" until next  Tuesday.

     

    Thanks for the "workaround."

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 7:04 AM   in reply to c kim

    Ah, I'd gladly pay you Tuesday for a hamburger today (J Wellington Wimpy)

     

    I hope there's an update for InDesign on the way - I'm getting nervous of all these reports of things going wrong in CS5?

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 15, 2010 7:17 AM   in reply to Eugene Tyson

    ... I agree

     

    Thanks,

    Brutus

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 21, 2010 11:15 AM   in reply to Stix Hart

    Script works here too!

     

    10.6.5

    CS5

    Indesign 7.0

     

    (Before latest Adobe update all was fine... thank you Adobe, thank you.)

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2010 12:57 PM   in reply to webheads1835

    All,

    With the help of one of the forum members, Steve, I was able to reproduce the issue and now have this being investigated by the InDesign development team. Once their investigation is done, we'll have an idea of how to address it. Thank you for your patience in the meantime. If you want to query on the status of the investigation, use the reference #2670994.

     

    Many thanks to Steve!

     

    Sincerely,

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2010 1:09 PM   in reply to Matthew Laun

    Good news!


     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2010 1:15 PM   in reply to Matthew Laun

    Thanks for staying on top of this. You're helping to restore my faith in Adobe

     
    |
    Mark as:
  • Currently Being Moderated
    Jul 23, 2010 1:48 PM   in reply to Peter Spier

    That really is good news!

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Jul 23, 2010 3:22 PM   in reply to Matthew Laun

    Thanks Matthew. I cannot understand why people have to complain so much with a fault in an excellent program like InDesign. All programs fail somewhere. Done by humans who end up doing mistakes even if they do not intend to do so. With such a complicated program and with so many users with so many different computers and setups something is bound to slip, that is why Adobe provide free continuos updates after all!

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 3:33 PM   in reply to Daniel Cilia

    Yes - adding the document to a book, closing the book and exporting from the Book Options menu worked for us. Looks like background exporting was crashing us, though we can't be sure.

     

     

    Thanks for your help Bob and Matthew!

     

     

    But we shouldn't be too critical of people who come here and make complaints – often these complaints are the first steps to Adobe recognizing a problem and rectifying it, much to the benefit of all of us.

    Yes, the language gets a bit shrill sometimes. But, by the time people come here to complain, they've often already been through a lot of stress that's costing them a lot of money that should be going to their mortgage (and it could happen to all of us).

     

    Many users called tech support with this bug and were asked to pay a support call fee, which those users found objectionable. It's a longstanding point of disgruntlement in the professional community. (You can decide for yourself whether they're justified in that objection.)

     

    In our case here at the college and in my company, our tech problems are usually very time sensitive and serious enough to baffle even the most knowledgable users here (but, in this case not Bob!).  So it's very helpful to be able to communicate this to Adobe development personnel and get some info on the likelihood of a quick workaround. It lets us make critical business decisions that have a big impact on our livelihood.

     

    The fact that Matthew appeared here to work with users and ask for files to test was a big positive step and helped us keep our losses from this issue under $2000. It's still painful, but it could have been much worse (as in six-figure worse).

     

    We'd love to see more of this and perhaps a standardized way of getting that kind of interaction rolling in a timely fashion.

     

    Best of luck to all of you wrestling with this - hope this workaround solves it for you.

     

    Cheers

     

    Tom

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 3:50 PM   in reply to Thomas Dearie

    Ooops, that's:

    ... adding the document to a book, closing the document and exporting from the Book Options menu worked for us...

     

    Couldn't really close the book and make it work, could I?

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 4:12 PM   in reply to webheads1835

    Everyone having troubles exporting PDFs in the background,

    Can  you try a test to confirm our findings? Take a document that you know is  failing in the background, confirm it still fails (force quit InDesign  to get back to a working state :-( Now disable Preflight and try it  again?

     

    Note that the current theory is that a component  is unexpectedly hanging on to some memory it shouldn't be, so the size  of the document is not the issue, simply the document and application  circumstances to cause that component to be working while you're trying  to export to PDF.

     

    Thanks for any feedback you can offer, and for your patience while we try to address this.

     

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 4:17 PM   in reply to Matthew Laun

    I think this was discussed in an earlier forum, but here's something that I found out... Since I upgraded to CS5, most of the older docuents that were originally created in CS3 (and subsequently re-saved as a CS5 document) are the ones that are giving me the problems. New documents that are created in CS5 seem to work fine... Your thoughts.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 4:22 PM   in reply to Matthew Laun

    Hi Matthew.

     

    Ran the test you suggested and the document still crashes when Preflight is turned off through the preflight options panel.

     

    Let me know if there's anything else I can test.

     

    Tom

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 5, 2010 4:29 PM   in reply to c kim

    c kim wrote:

     

    I think this was discussed in an earlier forum, but here's something that I found out... Since I upgraded to CS5, most of the older docuents that were originally created in CS3 (and subsequently re-saved as a CS5 document) are the ones that are giving me the problems. New documents that are created in CS5 seem to work fine... Your thoughts.

     

    Yes, definitely we are primarily seeing this problem in CS4 legacy files, not files created in CS5, though we're just rolling out our testing of CS5, so it's early yet.

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 10:48 AM   in reply to Thomas Dearie

    Thomas,

    Thanks for the test. Unfortunately, there is one more step that needs to be added to make it a valid test for our hypothesis. Do the steps in this order:
    1) Disable Preflight

    2) Close all documents

    3) Open the suspect document

    4) Export to PDF

     

    The object holding on to the PSLibrary lock won't get destroyed until the document is closed, so that step 2 is critical. Could you please try again and let me know the results? It's possible that in your case there is some other action that the PSLibrary is doing unrelated to preflight, which could explain a failure even with these steps. If it fails with these steps, I'd very much like to get the file for additional data to feed into our investigation. It would ensure we have a comprehensive solution. If you can minimze the document and still reproduce the failure, then you can make the package upload/download faster. Post on Acrobat.com, or email me at mlaun at adobe dot com for FTP instructions.

     

    Sincerely,

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 12:41 PM   in reply to Matthew Laun

    Matthew --

     

    I was able to reproduce this with the test document that I sent to you earlier. However, I had to change the order of the steps slightly:

     

    1) Close the document

    2) Disable preflight

    3) Reopen the document

    4) Export

     

    Is preflight a document preference? Turning it off it before you close the document disables it for the remainder of the session with that document. But when the document is closed, preflight is enabled again in the app and stays enabled when the document is reopened. Closing the document, then disabling preflight, keeps it disabled when you reopen the document.

     

    Just turning off preflight and keeping the document open did not seem to fix the problem. (As you said.) The document has to be opened with preflight disabled.

     

    Anyway, once preflight was turned off the export worked perfectly -- I could watch the file being exported in the background tasks window. Sounds like you may be on to something.

     

    Fyi I ran this test on two machines and it worked on both.

     

    Steve

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 1:21 PM   in reply to Matthew Laun

    Hi Matthew

     

    Yes, I did the following and repeated to be sure:

     

    1. Disabled Preflight and Preflight for All Docs.

    2. Quit InDesign

    3. Reopened and confirmed Preflight was off.

    4. Opened problem doc and exported to PDF.

     

    InDesign crashed after I left the PDF options window.

     

    I can send you the document as a download link from our ftp page.

     

    What do you need:

    1. Document?

    2. Linked files?

    3. Fonts? (I suspect you have those already, being at Adobe.)

     

    Let me know and I'll prep the file.

     

    Cheers

     

    Tom

     

    Message was edited by: Thomas Dearie

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 1:39 PM   in reply to Thomas Dearie

    Thomas,

    If you are seeing InDesign crash, not just the background export hang and never complete, then you are experiencing something completely unrelated and would be better off isolating the root cause using the steps in this document:

    http://go.adobe.com/kb/ts_cpsid_49998_en-us

     

    Jump down to the section titled "Troubleshoot print/export problems at the document level."

     

    If you find the root cause, report back and we can look into whether there is a defect, or just bad data somewhere in the document(s) that we are not doing good error handling with.

     

    Sincerely,

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 1:51 PM   in reply to Matthew Laun

    Okee dokee. Will try this.

     

    Certainly, forcing the export to the foreground is 100% effective.

     

    Also, binary isolations show pages crashing in one combination and successful on another.

     

    I'll take a look at the export troubleshooting. I'm rough on time now, as I have to catch up with things missed during the problems, but I'll try to squeeze some time out.

     

    Cheers

     

    Tom

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 6, 2010 1:56 PM   in reply to Thomas Dearie

    Tom,

    Actually, if forcing it to the foreground always allows it to export without errors, then please package up the document and post it so that I can do the testing, and you can keep working ;-)

     

    Save a copy of the document, then delete pages/spreads to the most minimal size you can, while still reproducing the failure, then use the package feature to package up the pub, links, and fonts.

     

    If you need to use our FTP site, email me directly, mlaun at adobe dot com, and I'll send you the information.

     

    Matthew

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2010 2:12 AM   in reply to Matthew Laun

    I had a document made in Quark en converted to Indesign.

     

    Workaround that works for me:

    - Export page as IDML

    - close documents

    - open IDML document

    - Export

     

    Hope it helps.

     

    Michiel

     
    |
    Mark as:
  • Currently Being Moderated
    Aug 27, 2010 2:25 AM   in reply to mediataal

    Guys I still do not see why its still a problem to many of you. All you need is to make a new Book document (File>New>Book) insert the document you need to export to Pdf, and then make the Pdf from the Book Palette. InDesign CS5 will then work exactly as the PDF export in CS4 with no hangups, yet with Background Pdf export off unfortunately.

    Background tasks is a great feature because it lets us continue using InDesign whilst exporting yet we have to wait until Adobe fixes it up.

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 10, 2010 3:22 AM   in reply to Daniel Cilia

    I'm not sure why no-one has posted this yet, but I think an update to 7.0.2 released a month ago may fix some or all PDF exporting problems:

    http://www.adobe.com/support/downloads/product.jsp?product=31&platform =Macintosh

     
    |
    Mark as:
  • Currently Being Moderated
    Sep 10, 2010 3:42 AM   in reply to Yakflange

    The background export hang is not addressed in the 7.0.2 update.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points