- Copy the version (8) folder to your desktop.
Almost certainly they meant MOVE (not Copy) the Version 8.0 folder. Copying it isn't going to do anything. But moving it will cause InDesign to regenerate preference files there. Files that might (somehow) have gotten corrupt. Did you try moving or copying?
Adobe REALLY needs to remedy this, I don't understand how they can release a brand new version where a program crashes like this.
The glib but true answer is that it happens to you but it doesn't happen to most people, and didn't happen to Adobe in testing. That's how it can happen. And it's not going to get fixed until someone figures out why it's happening. Was Adobe Support able to reproduce your problem?
You're right, it is "move the folder", I obviously can't go back and edit but you are correct.
Alas, Adobe Support wasn't trying to reproduce the effect. I send them the crash report, every single time, so they should have something to work with. Regardless, I can't see how this wouldn't have been reproduced, or have happened when testing, when this was the first project I cretaed with this version. Oh well, doesn't matter. They still need to look into this as I'm not the only one, obviouslly.
Encryptics-Graphcs wrote:
I can't see how this wouldn't have been reproduced, or have happened when testing, when this was the first project I cretaed with this version. Oh well, doesn't matter. They still need to look into this as I'm not the only one, obviouslly.
Rest assured, if this had shown up in testing it would have been fixed.
What you did essentially was replace the preferences (though you only did half the job), the number 1 troubleshooting step for program oddities.
I'm having the exact same problem -- CS6 InDesign crashes when I try to print or make pdf. Instantly. I'm on a new Mac with new software. Fonts were managed by FontBook at first and then by Extensis Suitcase 4 -- no difference. There is no old baggage on my machine so it's unlikely that anything has corrupted. But the problem persists. Any inspirations? Did the moving the preference files work? How did that go again -- Peter Spier seems to think that was only half the solution...
@Catherine – did you try exporting to PDF in "foreground"? That means, did you try the script Marijan Tompa was pointing to?
I don't know if this is still working for InDesign CS6.
You could also try my script "ExportPDF_in_Foreground.jsx" from 2010, that does not change any preferences of InDesign. Just invokes the PDF export menu you are used to in an older method like in InDesign CS4 or CS3.
Save the script to a pure text file in your Scripts Panel folder, you can access it now instantly in the Scripts panel of InDesign.
Double-click the script from the Scripts panel. A window will pop up and you will be asked where to save the PDF, after "ok" the next dialog will show up asking you how the PDF should be named. The edit field is pre-populated with the name of your InDesign file plus ".pdf".
After that it's all like you are used to with the "normal" pdf export menu. Except: you cannot work in InDesign as long as the pdf is exporting. Thus the "Foreground" in its name ;-)
Here is the script:
//ExportPDF_in_Foreground.jsx
//Uwe Laubender
/**
* @@@BUILDINFO@@@ ExportPDF_in_Foreground.jsx !Version! Wed Jun 23 2010 17:08:10 GMT+0200
*/
//DESCRIPTION:PDF-Export in foreground (old school like in InDesign CS4)
if(app.documents.length>0){
var d=app.activeDocument;
};
else{
alert("Please open a document to execute export to pdf. Script will be aborted.");
exit();
}
if(d.saved == false){
alert("Save your document first before executing export to pdf. Script will be aborted.");
exit();
};
var pdfPath = Folder.selectDialog("Folder to save pdf:");
var pdfName = d.name+".pdf";
var userDefFileName = prompt("File name:",pdfName,undefined);
if(userDefFileName == null){
exit();
};
var pdfFullName = pdfPath+"/"+userDefFileName;
if(File(pdfFullName).exists){
c=confirm("The PDF-file \""+userDefFileName+"\" is already existing. Do you want to overwrite it?",true,undefined);
if (c==0){exit()};
};
//Error-handling if PDF file override is on and PDF is already opened in an PDF reader app:
try{
d.exportFile(ExportFormat.PDF_TYPE,File(pdfFullName),true,undefined,undefined);
}catch(e){
alert("Error:\r"+e.message+"\r\r(Line "+ e.line+" in script code.)");
exit();
};
I cannot say, if that will help you, 'cause I have no crashes by exporting to PDF with InDesign CS6. Never had those crashes in InDesign CS5 or CS5.5 as well.
But maybe it's a thing with your latest version of Mac OSX.
I'm still on OSX 10.6.8…
Uwe
Message was edited by: Laubender
I'm sure Peter has a point, but I can only agree to disagree.
I ended up having to find which graphic(s) was causing the warning message to generate. I did, and once those images were removed it converted to PDF fine.
I did another project, had the warning pop up and it crashed again.
I can only hope there is a fix that's pushed soon.
Encryptics-Graphcs wrote:
I'm sure Peter has a point, but I can only agree to disagree.
Please feel free. My point about half the job was that probably more than 90% of the time when a user replaces only one of the two files that make up the preferences set in ID the problems persist. This doesn't necessarily mean that replacing prefs will solve all problems -- it won't, and clearly will not solve a bad graphic -- bu tif you are going to try a prefs repalcement there is essentially nothing to be gained, and a lot of potentially wasted effort, from only doing half the job. Either use the keyboard shorcut method during launch, or manually move, rename, or delete both the InDesign Defaults and InDesign SavedData files.
FYI - I have an outstanding case with Adobe regarding InDesign crashing anytime an warning message is presented by the application. I've had it happen numerous way (PDF export, Packing, Page Deletion). In all cases a blank warning message pops up very briefly and then the application crashes. The solution I've found is to find a work around in each instance that would not trigger the warning message. If I can avoid the warning messages I've had no crashes.
My case has been elevated to the 2nd level of engineers and I spoke to one directly about this. They acknolwedge and know about the issue and say that they believe it is specifically realted to OS 10.7.4 and it only occurs when it's being run on new hardware that was recently released (I'm a new 2012 MacBook Air).
Hey, there is some workaround here :
http://forums.adobe.com/message/4550204#4550204
Same problems as here.
Just had an issue where CS6 was giving error message "Failed to Export PDF File" when trying to create a pdf. After much trouibleshooting, we found the culprit to be an icon created in Illustrator and pasted (not linked) into InDesign. Just thought's I'd share in case anyone else was having similar issues and have been unable to resolve.
I too was having a problem exporting an InDesign CS6 file to a PDF. The error message simply said, "Could not export PDF". So I tried printing to an Adobe PDF file and noticied that the exporting would hang up on page 12 of a 19-page document. Then I tried to print to PDF using a 3rd party distiller called PDF Complete (http://www.pdfcomplete.com/cms/default.aspx). This 3rd party distiller gave me the error message "There is a problem with a font file on page 12" and it produced a .txt file with the following error:
%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[Page: 2]%%
%%[Page: 3]%%
%%[Page: 4]%%
%%[Page: 5]%%
%%[Page: 6]%%
%%[Page: 7]%%
%%[Page: 8]%%
%%[Page: 9]%%
%%[Page: 10]%%
%%[Page: 11]%%
%%[ Error: undefined; OffendingCommand: 1.#NAN ]%%
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
I went to the "Type" menu and selected "Find Fonts" and tried to eliminate any erronenous fonts, but this did not correct the problem.
After deleting the contents of page 12 (except for what was in the master page), the file exported to a PDF perfectly with no errors.
In the end, I had re-create page 12 of my document, the page that was causing the issue, which is much better than having to re-create the entire document, which incidentally took 20 hours to create the first time.
North America
Europe, Middle East and Africa
Asia Pacific