Skip to main content
Participant
June 1, 2010
Question

Problems making a PDF from Indesign CS5

  • June 1, 2010
  • 46 replies
  • 74901 views

Hi friends. I have recently switched to CS5 and I find that I usually need to close the program and then reopen it before I can make a PDF. It says it is working in the background but all it does is spin without creating the PDF. Anyone else having this problem? 

TED

    This topic has been closed for replies.

    46 replies

    Adobe Employee
    June 30, 2010

    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

    Known Participant
    June 29, 2010

    This banter aside, the basic problem remains: it is not possible to create a PDF from an InDesign CS5 Document. I have a 700 page book that I need to get into a PDF document so I can send it to the printer. If anyone has a solution (Adobe included) it would be most appreciated. Thank you.

    designerBeans
    Participating Frequently
    June 29, 2010

    Hi China,

    After hours of tech support, we found that most of my problems was with CS4 legacy files (especially books) and figured out a workaround. You have to export your file(s) to IDML file. Then open again. To me this is not a good solution not to mention time consuming to have to do this to hundreds of legacy files but it works for me.

    Let me know if it helps.

    Known Participant
    June 30, 2010

    Thank you so much for responding. I will try that. Thanks.

    Participating Frequently
    June 29, 2010

    This is a forum on Adobe's website. It is not run by a private party. This is Adobe's game. They through the ball and we are not playing. I can't speak for you, but we have paid tens of thousands of dollars to a company over the past 15+ years. We deserve better than this.

    I understand your motivation to have us all sit around the campfire, hold hands, and sing pleasant songs... but not this time. We will share once Adobe gives us $40. That simple. Don't take it personally. Instead, rally behind our actions. Like I said before, if Adobe can do it to us, we can do it to Adobe.

    L

    Participating Frequently
    June 29, 2010

    We have the same crashing problem, or shall I say had the problem.

    My group and I have been systematically working though our documents determining what is causing this problem. About 6 of us decided to spend part of yesterday and all of this morning looking for a common denominator. At first we thought it was with the tables that were linked in the documents. About an hour ago we had a breakthrough and are certain that what we found is a real bug.
    We know this because it is not associated to any of the other elements we brought into the document. Instead it is an element of the software that is used my some (explains why not everyone is experiencing the problem) and is reproducible.


    Here is my approach. We are not going to share this bug with Adobe until they pay us $40. Why $40? That is the amount they were requiring us to pay when we called their god awful tech support. We spent thousands on an upgrade and then were asked to pay them for service??? This was after 1.5 hours of being bounced around the planets telephone cables. Well Adobe… It goes both ways. We worked our tails off to solve an issue that was yours to begin with. If you had treated us differently we might have been inclined to participate in “community testing”. After what we have been through, it is now a matter of principle.

    Sorry I can’t help (I have the solution), but Adobe is to blame for this. When we get the $40, we will share the bug. Adobe will be getting a call in a few minutes where I will explain our terms. Again... it goes both ways.

    Customers unite...

    Lance

    BobLevine
    Community Expert
    Community Expert
    June 29, 2010

    This is a user to user forum, where users SHARE information with each other for everyone's benefit.

    So, either share or take your ball and your bat and go play somewhere else.

    Bob

    Participant
    June 29, 2010

    Well, no need to get emotional, but any hope that bugs will be promptly fixed is not founded.

    Some (  but not by any means  all ) reasons:

    - Fixing the bug will mean that manufacturer indirectly admits that the software is poorly designed at the the beginning -don't expect such an admition.

    - Adobe has embedded itself firmly in the market  and has no real insentive to deploy more brain power - people buy the products anyway...

    - Buggy InDesign will make you buy another Adobe product, say, Acrobat Pro. Result - more money for Adobe corporation.

    - If any bug-fix is done  it will come as an upgrade you have to buy  - again more revenue for Adobe corporation.

    Hope you get the picture :-)

    So keep calm and try to get by with the buggy InDes CS5 - there is no other option.

    BobLevine
    Community Expert
    Community Expert
    June 29, 2010

    InDesign has always received the highest number of dot releases of any product in the Creative Suite. It's flat out impossible to release bug free software. Nobody can do it. Not Adobe, not Microsoft, not even Apple.

    Bob

    Known Participant
    June 25, 2010

    I find that I am able to create a PDF file, but when I try and open it in Acrobat I get an error saying the file is damaged. Would seriously appreciate a fix for export to PDF.

    June 25, 2010

    On top of the problem I've been having. On of the files I have pdf'd and crashed when I was able to finally get a pdf I must of closed and not saved. I can not open this file its totally corrupt. no matter what I try moving changing name, I cant open it, it just crashes CS5. I really haven't had a corrupt indesign file in probably 4 years. Ever since CS2. This sucks.

    Participant
    June 25, 2010

    I've found if you force quit Indesign it stops the hung up background process and when you restart the app it will make a pdf (at least so far today)

    Somebody at Adobe tested making pdfs in Indesign CS5 BEFORE it went gold master right?

    Daniel Cilia
    Known Participant
    June 25, 2010

    We might complain about Adobe for messing up the background pdf printing yet I am sure they are working on it and will fix it with the next update for free. Something like this cannot be fixed for at a charge. Can someone at Adobe please confirm this.

    BobLevine
    Community Expert
    Community Expert
    June 25, 2010

    This is not a direct line to Adobe. It's a user to user forum.

    If you wish to make you case directly, do so here: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

    The more people they hear from the better.

    That said, I've yet to see this issue and while there have been several reports, it doesn't seem like a widespread problem, so the more details you can provide the better chance of seeing it fixed.

    Bob

    Participant
    June 24, 2010

    I'm pretty furious about this problem with PDFing files from InDesign CS5. I've been an Adobe user for about 12 or 13 years now and this problem sucks. What happens to me is I try to make a PDF file for printing on a Heldelberg press with the preset given by my printer. The program then just goes off into some endless loop, without an error message I might add! I have to force quit the program on my Intel based Mac that is running OSX 10.6.4, with 4 gigs of memory... When I restart the program and open the file I can then print one PDF file. After that the program goes back into the same model of running off in some endless loop without an error message. Note too, I quit all other applications, so that there are no conflicts.

    Adobe, THIS IS THE WAY WE MAKE OUR LIVING. You might just want to fix this problem and post an update soon! This is the kind of thing that gives companies a very, very bad name!

    Interestingly, we bought a Volume license for the product and now Adobe wants us to pay more to get a fix!  :-(

    Daniel Cilia
    Known Participant
    June 24, 2010

    I really hope that Adobe fixes this really soon, yet my way around the problem ( I already mentioned it earlier on)  is to make a new book, insert the document I want to do the Pdf of and then print the Pdf from the book panel. By doing this it does not do the background 'printing' and works like CS4 without background printing. I think the problem lies in the new background printing in CS5.

    June 24, 2010

    I had the same problem. I would export pdf and it would go to background and create pdf. I would open my next document to make a pdf and and it would get hung up at 9% and spin, always 9%. this was at 2:00 am with a 10:00 am deadline, I love stress.

    My work around would be to launch indesign CS5 export hat document, save, close document, shutdown indesign CS5, restart indesign CS5 open new job to export and repeat the whole process for each Document.

    I hope they fix it, cause its a huge waste of time.