Hi all, this problem blows,Adobe is almost as bad as Mac these days. What happened to the days of Mac, the best, fastest, most stable machine in the industry with the Adobe programs to top it all off???? Gone are those days.
ANYWAY, this doesnt fix the program error but will get you out of trouble. Print a POstscript file first, then run it through Distiller. Works every time. Remember Distiller, haha.
@thunkup, another way is this script here, I've referenced it once on this thread already (), if you're comfortable with using scripts it might be a bit faster, it's just another method of bypassing the background export like the book method does.
Great advice, I'll try that. Anyone else have problems with Packaging in CS5? Some files when I package them for output to my printer it freezes on the last stage of the process the "open file" stage, the file is corrupt after that too. Maybe I'll try the new book solution on that too?
Anyone else have problems with Packaging in CS5? Some files when I package them for output to my printer it freezes on the last stage of the process the "open file" stage, the file is corrupt after that too. Maybe I'll try the new book solution on that too?
Are you upodated to 7.0.2? There were packaging issues on Mac with filenames that had "illegal" characters in them (characters not allowed on unix or Windows systems), though I haven't heard of file corruption being one of the side effects.
Good news. The root cause of this issue has been determined. The key factor is a PSD placed such that it crosses the spline of a spread, and preflight is enabled. The Photoshop Library (PSLib) which reads the PSD data and translates it into information that the preflight can analyze, was getting stuck on the main thread. The background PDF export was then forever waiting for the PSLib to be free on the main thread.
So the easiest workaround for this issue would be to disable preflight before exporting to PDF if you have PSD files spanning your spreads.
More importantly, now that this is understood, we believe we will have this addressed in a future release. Stay tuned to your update notifications, or this thread.
Many thanks to the community, and those who provided files, for helping us identify the cause of this problem.
I found that this problem was mostly due to corrupted Helvetica Neue T1 fonts on a Mac. Once I fixed the font issue the PDF export problem has gone away, but I will keep an eye out for PSD files across the spine as well. Thanks
Is your failure showing up as a hung background process? If not, then your issue has nothing to do with the issue I'm discussing, which was the start of this thread (it's gotten off on general PDF export problem tangents which don't belong here). If it is a background task hang, but there is no PSD crossing the spline, check to see if there is a transparency effect crossing the spline. I believe transparency effects also use the PSL.
If not a background task hang, here's a good doc that can help to determine the scope and cause of your failure, and workaround the issue:
If you find something that you think is a product defect, please send me a private message so I can follow up.
That's good news, and I don't want to rain on your parade, but you should know that none of the files on which I experienced a hang had a cross-spine object that I can recall. I haven't seen a hang for quite some time, and haven't been able to repeat it on any file where it happened before.
Yes even I have not had any problems exporting yet I must say that I make it a point to open the Background Tasks panel before I start the process of exporting. Whenever I have done that the export went well and no hangups. I have had it hang up before on single page documents so I don't know if the spine/preflight solution has anything to do with the problem.
Bob's idea of saving a PDF from a book file worked for me. Turning off Preflight didn't help, neither did upgrading to 7.0.2. Apparently, exporting in the foreground is the crucial ingredient.
Each new version of Creative Suite adds new features, many of which I appreciate, but the price seems to be problems like this that can stop you cold from getting anything done. I'm not sure the tradeoff is worth it, certainly my boss doesn't think that it is.
Your description exactly matches my experience with this issue. Ever since your first note mentioning the connection with preflight, I've had that feature disabled by default and have not had any problems exporting pdfs. Thank you for the update -- looking forward to the next dot release.
If a document has a transparency across the spine, switching the Preflight off does not solve the problem for me. Have just lost an important deadline by 5 minutes :-(
From now on I will return to my first suggestion, that of exporting only using the book panel. Otherwise too much time is wasted to export in background.
I wish that Adobe never thought of background exporting. So much time has been wasted by us users.
InDesign CS5 users print from the book panel and forget trying to solve the problem. It must be embedded deep in InDesign CS5. Only Adobe can solve this problem 100%! Hopefully with the next update.
Please post a sample document of the problem you are having, and I'll test it in an internal build that has the fix. If it isn't addressed with the fix, then we will investigate to see what the root case is for your case. You can post it for free on Acrobat.com, just log in with your Adobe ID, then share and copy the link and paste it in a reply here.
I'm having the same issue (PDF not exporting and hanging in Background tasks). I've removed the PSD files. There is no spine being crossed by anything. I can export the same file as part of a book. I've restarted 3-4 times in the process and had to force quit Indesign to get out. The same file worked fine an hour ago. I updated some .tif images and went to export.
Is there a way to change the export pdf back to the foreground?
Uwe Laubender posted a script that exports inthe foreground here: http://indesignsecrets.com/forum/general-indesign-topics/pdf-export-pr oblems-with-cs5
I've a similar problem. Some but not all ID5 files that have been converted from ID4 will not "Package". The process freezes the application about 90% of the way through the process. I can rewrite it as an INDL file and reopen in ID4 and create the "'Package" with not a blink.
Anyone else seen this?
CS 5 on Mac OS 10.6.6
After not being able to reproduce a crash with some of the files I've been provided, I worked with Josh to get a crash log from his background PDF export failure. The crash log appeared to indicate an impact from the Extensis font auto-activation plug-in. If you are using any of the Extensis tools in conjunction with InDesign CS5, and are experience failures to export to PDF in the background, please disable the Extensis toolset, restart InDesign, then try to export again and see if the export is successfull. Please report results here, including the exact Extensis product[s] and version[s].
If you're having issues with export, and believe that it's the plug-ins causing it, that's not normal. I recommend contacting the Extensis technical support team with the versions that you mention, etc. so that we can appropriately diagnose the issue.
I switched from Linotype FontExplorer Pro 2.5.2 to Extensis Suitcase Fusion 3 v 14.0.5 (162) for about a month without any problem. That is, until I updated OS X 10.6.6 to 10.6.7 last weekend.
Among other performance issues, I could not export PDF or IDML from InDesign CS5 22.214.171.1245. It crashes when the background progress bar still at 0.. I should, however, print and save as PostScript file and user Acrobat Distiller to create PDF.
By doing following steps, I concluded thart sure enough, Suitcase Fusion 3 is the culprit.
1. Copied the document fonts into ~/Library/Fonts.
2. Moved ExtensisFontManagementIDCS5.InDesignPlugin out of /Applications/Adobe InDesign CS5/Plug-Ins folder
3. Quitted Suitcase Fusion 3.
4. Launched InDesign and opened the document.
5. Exported as PDF successfully without any crash.
Perhaps, it’s the combination of )S X 10.6.7 and Suitcase Fusion 3 that causes all the hassles.
See this thread I created: