Print ready files: PDFs won't convert (keep having an error)
So, I am using Indesign CC to make a print book. I'm using Lulu's full bleed PDF job options. I've used these job options before on the same indesign files I'm using now, but have started having problems.
The problem I am having is, I recently updated my Indesign document (corrected some typos) and exported it the same way as usual, but when I get to the stage where I have to convert the PDF to a print ready file... it takes several hours, and then gives me an unexpected internal error message.
I've tried re-exporting the PDF from indesign a few times and doing this again, I've tried making a new project from scratch. Same problem.
I've found I can get the PDFs if I export them as separate chapters to convert into individual print ready files, but the conversion process breaks when I try to export them all together.
I also tried making a print ready file by adding all the separate chapters to the book and then running the converter, but while it can handle them individually, it fails if I try to add them all to the project together. This would not be ideal in any case because I need the document to have bleed, and combining individual chapters results in losing that.
The files are well under the maximum, at just slightly over 80mb, so I know that's not the issue.
I really really need to get this book ready this week and make an order, I've sent an email to Lulu, but haven't heard from them yet. I know they try to get back to people ASAP and I would give them that I've actually been impressed by their customer service thus far.. but this is a situation where I'm really in a hurry to update the project with typos fixed and get it shipped off. I've been trying for 2 days to get the file to convert to print ready.
What should I do?
Comments
In case it matters, creating the print ready file seems to progress to about 90%, hang for a good long while and then progress to the end only to show the error and not allow me to proceed beyond this step. I've checked and the print ready file will show up in my files, but that does me no good since I can't go to the next step in the content creation wizard.
He hasn't been back in touch and all I get are errors at the moment
As Salith commented, file analysis for complex files can take some time.
I recommend you both contact our print support team.
They will be happy to have a look at your files and provide recommendations for speeding the process. In the mean time, I can suggest you flatten the file and remove all transparencies before you upload it.
It is a image intense book, there's at least one big image on each page, but it being graphically intense is pretty important to me. I exported it with transparency flattening, but it doesn't help, still seems to be timing out. I've been trying to do this for 3 days now. I never had problems with image intense files before, so I'm guessing this has something to do with a recent update to the system.
I've messaged them, but am pretty sure I'll just hear the same thing the other poster with this same issue heard.
In any case, this makes sense, it does seem to be timing out, but I've tried... well over 10 times to do this in the last 3 days now, no luck yet.
This issue is of particular interest to our print support team.
We are actively investigating the cause and seeking a solution.
PS.: post author, please let me know if I'm disrupting this thread, we're in the same situation but I'll understand and take the discussion elsewhere if you prefer.
I having same problem
I just resaved file as PDF/A and flattened it and that seems to have done trick
I just resaved file as PDF/A and flattened it and that seems to have done the trick
Hi all,
Just wanted to add that I too have a problem of being stuck at the "Please be patient, Lulu is making your print-ready file" page.
I've uploaded a 8MB PDF file, generated by LaTeX, like I have done dozens of time before w/o problems. This time however, I seems to get stuck. Will be happy to provide more info if this will help you debug.
Ivan
It can often be the fault of how busy Lulu's site is, and even how busy the Internet is, even how many in one's own street are on line, and Wireless does not help either. People tend to forget that a site and/or tool they are using on one, could be 1,000s of miles away down a mesh of wires, cables, microwaves, mainframes etc etc, and that the transmissions are split in to little Packets that wizz around trying to find the fastest route, hopefully all melding together at the right place, in both directions. I wont even bother to add that one's own PC and router and ISP can make a difference too, speed etc. We just take it all for granted.
I just come back later.
One thing I have discovered is that if one steps back a process in the Wizard, then forward again, the up-load or conversion has happened anyway, it's just not told you! It was the tool's progress bar that stuck. (Although you should get a mail to say it has converted.)
Myself and my friend combined know everything there is to know, but he's not here.
In the midst of this same problem. Support has reached out, and, initially suggested I get the file size down (originally it was a 700M PDF, and is now a 450M file). Still not converting.
It's a very image intensive book (graphic novel).
Any suggestions on what to do (or not do) in InDesign?
Thanks!
Sorry to hear about the error. I noticed our converter doing that while I was working on a project recently too.
I suggest trying to run the converter a couple more times. It may well be a glitch on our end that's showing that error when it shouldn't.
I found your support case as well and passed that to a member of our team, they'll reach out to you as soon as they can to assist.
Even if your local internet service is working fine, if there are connectivity problems down the line it can affect what you're trying to do with a project on Lulu.
R.F.G. Cameron a.k.a. Sphinx
My work can be found at:
http://www.lulu.com/spotlight/antiqua_sphingehttps://www.amazon.com/-/e/B00DDZJOT2
https://antiquasphinge.wixsite.com/booksThe internet may work perfectly in one geographic area while having issues in another geographic area. I've been around the block as system support where a facility in one state was up and had great connectivity while a plant in a different state (hundreds of miles away) was unable to connect due to local issues.
R.F.G. Cameron a.k.a. Sphinx
My work can be found at:
http://www.lulu.com/spotlight/antiqua_sphingehttps://www.amazon.com/-/e/B00DDZJOT2
https://antiquasphinge.wixsite.com/booksBack when I did system support we tested with actual end-users and it was amazing the glitches they found as opposed to the developers. The reason being the developers know how a system is supposed to work so they have a good idea what not to do. End-users on the other hand have varying levels of expertise and will often push a system's limits.
As for software working perfectly, I'm still looking for that critter, but that's another story.
R.F.G. Cameron a.k.a. Sphinx
My work can be found at:
http://www.lulu.com/spotlight/antiqua_sphingehttps://www.amazon.com/-/e/B00DDZJOT2
https://antiquasphinge.wixsite.com/booksBut your idea is a good one.
It would help to test on at least a mild cross-section of the different operating systems available and being used to upload the files that might shed some light on what's happening.
Win XP, 7, 8, 10, Perpetual Rental
Ubuntu (whatever flavor, I think mine is Leaping Lizards or something like that)
Mac OS (I can't keep track)
As well a further testing qualifier would be file type uploaded, from .doc to .odt to .pdf.
R.F.G. Cameron a.k.a. Sphinx
My work can be found at:
http://www.lulu.com/spotlight/antiqua_sphingehttps://www.amazon.com/-/e/B00DDZJOT2
https://antiquasphinge.wixsite.com/booksI'm told we've upped server capacity. If you're still seeing the error please submit a support ticket as well as posting here. The more visibility we have, the more likely we can get the problem fixed.
That said, 200mb isn't that big, so I'm surprised you're getting that error. I would start with ensuring all your images are 300dpi resolution and that the entire document is flattened. If you continue to work with our support team, they can always offer additional advice and assistance.