-
1. Re: Framemaker 12 unstructured version 12.0.2.389 crashes when trying to print
Arnis Gubins Aug 27, 2014 8:22 AM (in response to StudioSm)A couple of things could be contributing to the issue.
During the FM12 installation, did they use the default settings or did they disable the installation of the PDF Creator add on? If they didn't disable the add-on, it probably stomped over their existing PDF printer instance and Distiller components. They can try using the Help > Repair in Acrobat.
Is the AdobePDF printer instance the default printer for the entire FM session? If not, invoking print and then switching (if the printer instance has been damaged as per the installation issue) may be a factor. Using the Sundorne SetPrint utility would avoid this issue. See: Sundorne Communications - SetPrint
For FM12, using SaveAsPDF is the recommended route. Where is the AdobePDF output port pointing to? This ideally should be a local folder, so trying to connect to an output folder on a network drive may be hitting some network communications issues.
-
2. Re: Framemaker 12 unstructured version 12.0.2.389 crashes when trying to print
Error7103 Aug 27, 2014 9:04 AM (in response to Arnis Gubins)> They can try using the Help > Repair in Acrobat.
They'll still be using an [unspecified] older version of Acrobat [Distiller] which might not work with FM12.
If they are stuck with using an older Acrobat Std/Pro, Print-to-Ps-and-Distill might work after Repair, even if Save-as-PDF and Print-to-PDF don't, but P2P&D is deprecated in recent FM versions.
-
3. Re: Framemaker 12 unstructured version 12.0.2.389 crashes when trying to print
Arnis Gubins Aug 27, 2014 9:55 AM (in response to Error7103)IIRC, it was starting with Acrobat 8 that the default locations for the joboptions files was changed. This created problems for FM's SaveAsPDF depending upon the FM version (FM8 and newer, I think) as it may have been looking in the wrong place and failed.
So unless they're using Acrobat 7 or older, the Help > Repair advice should be one of the avenues to follow.
-
4. Re: Framemaker 12 unstructured version 12.0.2.389 crashes when trying to print
galanoh Aug 28, 2014 9:24 PM (in response to StudioSm)I'm experiencing the similar crash since yesterday. The FM I have is v12.02.389, and I'm authoring in unstructured mode as well. I'm wondering if this was the same issue but I'd like to describe this error here rather than create a new but possibly a duplicate post.
FM version: 12.02.389
Internal Error Code: 12024, 24704628, 24704922, 27638133 (I was kind of surprised that four errors came all at once! Man, that's a whole bunch of zombies!)
Repro:
1. Open an existing fm file with more than 3 pages. (The reason of doing so is I was about to print page 64 to 69 of this chapter to PDF)
2. Go to Print Setup > Properties, disable the "Rely on system font...".
3. Save the changes then go back to File > Print and set the pages to be printed(say, 64 to 69).
4. Click Print.
Then I saw the progress bar moving but when it reached to the end, a prompt message box came up saying something like "Framemaker 12 closes due to Internal error 12024, 24704628, 24704922, 27638133".
I'm wondering if it's a bug or it crashes due to some improper settings? The FM12 was doing OK in the past. I've no idea what's going on. I was trying to look for the troubleshooting guide or similar stuff which might allow me find out the solution based on the error codes presented in FM12, but all the search ended up in vain.
-
5. Re: Framemaker 12 unstructured version 12.0.2.389 crashes when trying to print
StudioSm Nov 12, 2014 12:56 AM (in response to StudioSm)I actually found a least one culprit in the trouble with crashing FrameMaker. Imported *png images with 24 bit colorspace! We had some documents with a lot of images in *.png format with 24 colorspace. When we either converted the images to *.jpg or reduced the colorspace to 8 bit, FrameMaker stopped crashing. Strange but true!


