Cshow problems in Distiller 9.1

Hi all,
I'm having these nasty PostScript-problem which I can't seem to find a solution for. Out of all the files for three major newspaper being distilled every day I get the following postscript-error on 1-3 files every day:
NewspaperAds_1v3(1).joboptions
%%[ Error: typecheck; OffendingCommand: cshow ]%%
Stack:
0.0
{--pop-- --pop-- ct_str1 --exch-- 0 --exch-- --put-- ct_str1 --show--
{_ct_na _ct_i --get--} --stopped-- {--pop-- --pop--} {_ct_x _ct_y
--moveto-- 0 --rmoveto--} --ifelse-- /_ct_i _ct_i 1 --add-- --def--
--currentpoint-- /_ct_y --exch-- --def-- /_ct_x --exch-- --def--}
-mark-
-mark-
If I send the same PS-files to the RIP they will RIP with no problem. If I open the same PS-files in Apple Preview they open fine with all fonts embedded as subset.
I'm pretty sure that it has something to do with fonts, but can anybody point me in the right direction?
Actually I have 8 files that all fail on a Windows 2008 Server running Distiller 9.1. I I run the same files through Distiller 9.1 on another computer running Distiller 9.1 under Windows XP (using the same settings), 5 out of these 8 files are OK. Same thing happens if I run the files through Distiller 9.1 on Mac OS 10.5.6
Regards
Erik Terkelsen

Please understand that this forum is absolutely not an official portal for Adobe Technical Support nor is it official feedback to Adobe's engineering organization. It is a user-to-user forum frequented primaily by end users.
It is very unclear from your posting what your problem is. The original thread was related to what appears to be intermittent PostScript errors occurring when distilling certain PostScript files into PDF with Distiller 9.1. The problem file was analyzed at Adobe and the problem was not reproducible at that time with that particular PostScript file with the provided joboptions. Furthermore, the problem wasn't consistently reproducible on the user's systems. It seemed to vary by system. Perhaps it was a temporary disk space issue, a system configuration issue, etc. But we never were able to find the problem.
You are stating that you “have several eBooks in PDF format that seem to suffer from the same issue.” The problem originally stated was not with PDF files, but rather, with processing PostScript files. Thus, it is not clear how you are relating whatever symptoms you are seeing in Adobe Reader and Acrobat Standard with PDF files with PostScript errors in Distiller.
Please better describe exactly what symptoms you are seeing including error messages, screen shots, etc. such that some assistance may be provided. If it isn't a Distiller error, you really should have started a new thread, and preferably in the Acrobat forums for which this seems to more appropriate.
- Dov

Similar Messages

Problems installing Distiller job options

A customer has supplied their job options for web, but they will not install, I get the message:
Error in Library/Application Support/Adobe.Adobe PDF/Settings/abcweb.joboptions:/CompatibilityLevel out of range
Does anyone have any idea what this error relates to?

It could be corrupted, and might need to be created again. Or, they may have made choices which are incompatible with Distiller.
You should probably post a copy of the .joboptions file so we can test it out.

Problems converting eps to PDF in Distiller - claims "file is in use"

Hi,
I've recently starting having a problem in Distiller (the version that same with Acrobat 9). When I try to convert EPS files, I get the message "Cannot open the file. The file is being used by another process". This is a new problem, only a month or two ago it worked fine. The only thing I can think of that may have changed is
a) Adobe Reader was updated, I believe
b) in an effort to speed up my computer, I tried removing a number of items from my startup. But I've put them all back in, I think. Here's what's running (although I did start Acrotray manually, and it seems to close when Disteller closes.
Any suggestions?

Hi, Bill,
Ok, well, the problem is still here. I have updated the program. Created
new eps files that have never been open in Distiller (or any other
program) .When I try to use Distiller, I get the same message; Cannot
open this file. The file is being used by another process."
i have copied the directory to another drive - no change.
Possible clue: If I try to delete a file from Distiller/File/Open, it
again tells me that the file is already open and so can't be deleted.
How strange that it would think the file is still open. It does this
after a fresh boot, when my first action after booting is to open
Distiller and try to convert an EPS file.
I CAN combine the EPS files within Acrobat by using Combine/Merge files
into a single PDF. But of course that's horribly slow and only an
emergency solution.
Using Acrobat 9 Pro version 9.2.0
Windows 7 professional service pack 1
16 gigs of RAM
Here's what's running:
any more ideas?
Thanks!
Peter S. aka PeterCymbal

Frame 7.2 and InDesign CS3 Distiller conflict

I am using Frame 7.2b128, Distiller 7.0. I recently installed InDesign CS3, which uses Distiller 8.0.
Whenever I work in InDesign and create a final PDF, and then go back to working in Frame and generate a PDF by using Save As ..PDF (working in a book with all files open), I get "Internal Error 7204..."
In the past, the only way I could recover was to uninstall and reinstall Frame. Today even that won't work.
1. How can I generate a PDF in Frame? I get the same error when I use Print to file...
2. How can I configure my system to use either Distiller 7.0 or Distiller 8.0 all the time, and which should it be? Will this fix the problem?

Indesign's interaction with Distiller is no different from Frame's: From
either application you can print to the Adobe PDF printer instance. From
there, Acrobat takes over and the originating application (Frame or
Indesign) no longer plays a part in the PDF creation process.
Do you run into the same problem when you Export to PDF from Indesign?
Indesign's Export to PDF does not involve Distiller in any way.
Have you tried redirecting the Adobe PDF printer's output to File,
instead of to the Adobe PDF port (in the Ports tab of the Adobe PDF
printer instance)? This shouldn't change anything for you, except to
separate the two processes (printing and distilling). My guess is that
the error you're seeing is a problem with Distiller, not with Frame. But
if you're printing to the Adobe PDF port it's kind of hard to figure out
where things are going wrong. If you change the port to File, you can
print to a PS file from Frame, close Frame, and then distill the PS
file. Obviously any error you see at that point is not from Frame.
Have you tried uninstalling and reinstalling Acrobat 7?
I wouldn't bother buying Acrobat 8 just to fix this problem, although
uninstalling Acrobat 7 and reinstalling some version of Acrobat might
fix it. Plenty of people are running IDCS3, Frame 7.2, and Acrobat 7
without these problems (me being one of them).
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

Ps to PDF problem

Hello there,
I've a little annoying problem with distiller. I'm using a linux program which is creating ps files than transferring into windows and converting to .pdf with distiller. But PS files have this string;
stroke showpage savepage
this causes a program termination and distiller stops working. Than I'm changing string with this;
stroke showpage savepage restore
it's working and converting to pdf.
Now it's not possible to modify linux program to create the second command line. Is there any way to get pdf files with first situation?

This seems more a question about bad PostScript: the PostScript
programming forum may be more suitable. It's not possible to say
whether it should work, because savepage is not a part of the
PostScript language. It is a procedure somewhere else in the file.
Aandi Inston

Distiller failure on a portion of text in the document

I have a question that I'm hoping someone can assist me with, we have a Mac running Acrobat 8.1.6 (Distiller version 8.1.3) that continually fails on a portion of text in the document when creating a PDF from an EPS file. I have verified that this machine is setup identical to the other Mac that is doing the same type of tasks just watching different folders, the PDF creation is successful on the machine we'll call EPS2, yet fails on EPS1 with the below failure log.
Can anyone point me in the correct direction as to where to look to try and rectify this issue?
The Stack portion of the error is the text I'm talking about (* Tax credit to 1st time homebuyers who have) this text is the beginning of a sentence about a promo for 1st time homebuyers, like I stated above the PDF creation is successful on one machine and fails on the other. I am at a loss as to where to look to correct this issue, any assistance that can be provided would be greatly appreciated.
Error log:
Distilling: 07-29-2009 Page-01.eps
Start Time: Wednesday, July 29, 2009 at 9:29 AM
Source: /Volumes/Vol1/4 Shaun/EPS Files/07-29-2009 Page-01.eps
Destination: /Volumes/Vol1/4 Shaun/EPS Files/07-29-2009 Page-01.pdf
Adobe PDF Settings: /Users/EPS2/Library/Application Support/Adobe/Adobe PDF/Settings/folder.joboptions
%%[ Error: ioerror; OffendingCommand: show ]%%
Stack:
(* Tax credit to 1st time homebuyers who have)
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
Distill Time: 21 seconds (00:00:21)
**** End of Job ****

hockeyshaun wrote:
Philip,
Yes I had looked into clearing out the font caches, that also seemed to make no difference. We had one extra license sitting around for Acrobat Pro 9.0 so I installed that version and what do you know? the problem went away, must be something with the Intel's and how 8.1.3 handles the conversion. The file would fail on ALL the intel's but not the G5's, as soon as I upgraded the Intel with version 9.0 the problem vanished....odd, but understandable to a point I guess.
THat's good to know. Now we will know if you have a problem with Distiller 8 and you using a Intel machine perhaps Distiller 8 is not completely compatible with Intel machines.

Distiller hangs: OffendingCommand: ÐÏà¡±á

Distiller 5.0 hangs halfway through task. The output is:
Start Time: 13 July 2008 at 21:26
Destination: C:\Abc.pdf
Source: Abc.doc
%%[ Error: undefined; OffendingCommand: ÐÏà¡±á ]%%
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
Distill Time: 1 seconds (00:00:01)
**** End of Job ****
I have no problems in the past with Distiller. Does anyone know how to fix this problem?

>Distiller 5.0 hangs halfway through task.
This shouldn't hang. It should just stop after an error like this.
>Source: Abc.doc
Distiller does not read Word documents, never has. This is a normal
error if you try. Distiller only opens PostScript files.
Aandi Inston

Distiller will not stop distilling postscript file

I use Distiller 6.0.2. Lately, when I try to distill a Quark layout into a pdf the distilling process will not stop. The progress bar shows a number that just keeps on climbing up. It seems if I quit the program and then restart it, this will solve the problem and distiller will make a pdf of the postscript. However, I will get the same problem once I try to distill another page. I tried to trashing the Distiller preferences and then restarting the program. This did not do anything.

It's not a specific file and it doesn't matter how big a file is. I am distilling a postscript file. My Mac is running on 10.3.9. I only print from Quark to get postscript files.

Acrobat Distiller prompting for administrator username & password

I have built 2 images on 10.6 with the acrobat 9 (patched with latest updates) and im getting problems with distiller launching under standard accounts. All apps a launched under admin and work fine. However users only have standard account privileges and acrobat application works fine but when i launch distiller (patched to latest update) it prompts the user for the administrator login details.
New mac book pro and mac mini
10.6 (fully patched)
acrobat 9 fully patched
works under administrator account
created a local standard account on machine and it has the same problem.
help!!!

extra info - all our users worked in locked down environment so they dont have admin rights. I believe when distiller starts one of its checks/processes needs admin rights to enable to it to start the application. This was checked under the console.app.
i have tried giveing the application full read/write access and permissions but this doesnt resolve issue.

Distiller 9 crashes at launch

I just upgraded my system software to OSX 10.6.4 on my iMac and Distiller now crashes on launch. I then upgraded all my CS software's to CS5 but the same thing happens with the new version. I use SuitecaseFusion 2 for font managment. The error report has this message in it
"Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000b021effc
Crashed Thread: 4
Can anyone help?

Robbie Adkins wrote:
I have a LOT of fonts as I am a graphic desig
ner. How do I turn off the fonts?
That's what I thought you were; Graphic Designer.
The girl that works with me does a lot of design and she has all kinds of fonts loaded on her computer and sure enough quite often she has problem launching Distiller. It happens to me too when I do a bunch of design and I have to turn a bunch of fonts on.
What do you use for font management? Suitcase? Font Book?

Distiller produces log file, not a pdf

I'm trying to create a PDF from a quark file and getting this:
%%[ Error: ioerror; OffendingCommand: charpath ]%%
It's only happening with one file, but it's one pretty important file.
I tried created a ps file, putting it on another computer (identical computer) and it PDF'd perfectly...which leads me to believe it's a problem with Distiller, not the file.
Any thoughts?
Working in Mac 10.5.5, Distiller 8.1.2, Quark 7.3

>But wouldn't it indicate the bad font in the log?
Not in general, no.
>
>Also, there appears to be no rhyme or reason: we work from templates. All of the pages come from the same quark templates and use the same fonts; some will pdf, others won't.
It's all there is to go on in the log.
>
>And again, when I brought the ps file to another computer, Distiller PDF'd it fine.
Local font files could be relevant.
>
>I tried removing the art, too, which didn't work either.
The art it won't be. "charpath" is a PostScript instruction directly
related to text. (Unless it is art in the shape of a character, or
some such).
Try dropping all the text from this document. If it works now, you can
use divide and conquer techniques to isolate the problem.
Aandi Inston

Can't find text in distilled file, using some fonts

The products I have are Mac OS 10.6.8, Acrobat X and 9, and Word 2011 and Apple Pages for Mac; Acrobat 9 and Word 2007 for Windows XP.
There are numerous ways to create PDFs on both platforms, whether through save as or creating a PostScript file and distilling it. The problem is that with docs I have using Calibri, Cambria, and Candara, if I distill a PostScript file made from Mac Word or Pages, neither Acrobat nor Apple Preview can find text in the resulting PDF, whether the file distilled with Mac or Windows Distiller. (Meaning a "find" for a string comes up as not found.) All other combinations are okay, even writing a PS file in Windows Word and distilling with Mac Distiller.
I mention the fonts specifically because most of the time I use OTF faces, which always work. I even tried using the Windows TTF versions in the Mac operating system -- same failure.
And even if I force these fonts to be embedded in the Distiller job options, still no joy. If I take so much as a comma and set it to an OTF, I can find the comma. Also, Acrobat *can* find Arial text in a Visio flowchart placed in the Word doc. I don't know how the author placed it there, but it's probably copy from Visio, paste into Word.
The reason why I care about this is because the distilled PFDs are just a tiny bit better looking on the screen than other options, such as "Save as PDF" from the Mac OS Print dialogue. The only other one that looks as good is the Create PDF button in Windows Word, but I would rather not have to use Windows just to get a better-looking PDF.
So to summarize:
Mac app > write PS file > Mac Distiller = fail
Mac app > write PS file > Win Distiller = fail
Win app > write PS file > Mac Distiller = okay
Win app > write PS file > Win Distiller = okay
Mac app > save as PDF directly > okay
This might not be a problem with Distiller per se; it could be the Mac OS engine that creates the PS files. You see, I had heard that Apple used their own internally developed engine for the options to save PDF files directly, but was using Adobe code when one used the option to write a PostScript file, so that's why I'm so surprised and disappointed it fails.

tlmurray23 wrote:
The reason why I care about this is because the distilled PFDs are just a tiny bit better looking on the screen than other options, such as "Save as PDF" from the Mac OS Print dialogue. The only other one that looks as good is the Create PDF button in Windows Word, but I would rather not have to use Windows just to get a better-looking PDF.
Hmmm. In what way are Distilled PDFs "a tiny bit better looking on screen" than those made by OS X?
You are viewing both in the same app and platform?
And you're referring to font display?
What settings are you using in Distiller which you think might have some bearing on this?
tlmurray23 wrote:
This might not be a problem with Distiller per se; it could be the Mac OS engine that creates the PS files. You see, I had heard that Apple used their own internally developed engine for the options to save PDF files directly, but was using Adobe code when one used the option to write a PostScript file, so that's why I'm so surprised and disappointed it fails.
OS X's native graphics drawing environment, Quartz, is essentially a "Display PDF", so creating a PDF file is a very simple procedure.
Writing PostScript for printing uses Apple's own cgpdftops CUPS filter. I doubt there is any "Adobe code" as such, and I dispute the implication that "Apple code == bad; Adobe code == good", which you seem to suggest.
The specifications for PDF and PostScript are clearly documented, and it should be easy for anyone to follow them.
However, the fact remains that when Apple converts these MS fonts to PS, something goes wrong. It may be a bug in Apple's code; or it may be that Apple it strictly interpreting font data which MS is playing fast and loose with. Windows' own PS export would no doubt be designed to work with the looser implementation in MS's fonts. This is just hypothetical of course, though is in keeping with tradition.
What you could do is use a decent text editor like TextWrangler (free from BareBones software) to compare the PostScript code from Windows and OS X.
You could also look a the Properties tab in Acrobat of the PDFs, and compare the font encoding.
You could also test running out PostScript from any other app on OS X that you have using those fonts.
However, I think it is unlikely that you will see resolution unless MS releases a new version of their fonts, or some new version of OS X makes an amendment to fix the bug or cater for the MS issue. Perhaps Lion will do this; perhaps it won't.
Are you using the versions of these fonts that came with Office 2011 for Mac? What happens if you use the Windows versions of the fonts on OS X?

Saving Acrobat 9.0 files to open in Acrobat 5.0

I just purchased Acrobat 9.0 Pro. We have a workgroup of 7 staff, 3 use Acrobat 5.0, 2 Acrobat 8.0 and 1 - Acrobat 9.0 Pro. The issue is that when we use 9.0 and try and save docs, then those working in 5.0 cannot open them. We have tried everything, optimisation PDF/X/A/E, etc. Still nothing, those using 5.0 cannot open the 9.0 saved documents. It states that the files have been damaged. Is there anything that can be done? Has anyone else encountered this issue?
Yes, the natural answer maybe to upgrade everyone to 9.0, but I don't wish to. One of the main reasons is that many of our clients do not have 9.0 reader.
Any advice?

I had the same problem when I installed Acrobat 9.1.2 ... others with Acrobat 5.0 received the "damaged" message trying to open the files. I found this was fixed by re-saving the file in Acrobat 9.1.2 using the "Document", "Reduce file size", "Make compatible with Acrobat 5.0 and Later", "Save". This works fine and the users with Acrobat 5.0 can open the file for editing/viewing.
This is tedious to do for every file printed.
I attempted to fix my problem ongoing by setting the Distiller settings that are supposed to be used by Acrobat. In Distiller V 9.1 "Settings", "Edit settings", "Compatability", picked "Acrobat 4.0 (PDF 1.3), "Save As". Distiller now displays "Compatibility: Acrobat 4.0 (PDF 1.3)".
However, when I then print from Acrobat 9.1.2 the resulting file's "Properties" displays "PDF Producer: Acrobat Distiller 9.0.0 (Windows)" and "PDF Version: 1.5 (Acrobat 6.x)". And the file can not be opened in Acrobat 5.0
This appears to be a problem with Distiller not correctly saving the PDF 1.3 parameters (it appears to save PDF 1.5 by default); I have contacted Adobe directly but have not received a reply.

Can't create pdf files

I puchased a new computer with Windows 7 Home Premium 64-bit preinstalled. I installed by Acrobat 8.0 Standard program and performed all of the updates for windows and acrobat and everything worked fine. I could create pdfs from both the adobe pdf printer and the links in Office 2007 and IE8. 3 months later I had to perform a factory restore on the computer due to an unrelated problem. When I reinstalled Acrobat 8, I lost all the create pdf functionality. When I print to the pdf printer, it shows it in the queue and then it disappears without creating anything. When I use the Office 2007 create links, it hangs on "creating pdf". When I click on the links in IE8 nothing happens. Any help would be appreciated.

If you start Distiller, then you have to open a file to process. That would be the file you created with the print-to-file. The file may have a prn extension if you did not change it to PS, but it will be a PS file as long as you used the Adobe PDF printer. You can also look at the PS file in a text editor to see what is there and be sure you do not have an Empty job. When you come back, indicate the exact steps you take to get to where you have the broken problem with Distiller.

Keynote PDF output: fonts appear "bold", milky background

Hello,
we observed two problems when exporting a Keynote presentation into PDF ("export" and "print" exhibit the same behaviour):
(1) when opening the PDF in Preview, the medium-size fonts appear to be "bolder" than in the presentation, small fonts look OK. We have tried several fonts (e.g. Trebuchet), the effect seems to be independent of the font. Colors look exactly as in the presentation.
(2) when opening the same PDF in Acrobat 8 Pro on either Mac or PC, the fonts look OK but all colours look as if through a "milky glass layer". This is an effect which is probably related to some color space conversion.
A similar topic was discussed last November, but no satisfying solution was presented. Many thanks in advance for any help with this.

It doesn't seem to matter what the Registry/Ordering is - I still get the error. I do recall that setting it to something known like Adobe and Japan1 had other effects, though, such as incorrectly chosen glyphs, though those could have been related to other issues we had at the time.
Since any value seems to prompt the issue, it leaves me even more confused as to what could be the root of this problem. Distiller seems to bypass embedding CMaps by using the "Identity" encoding and simply writing the glyph indeces into the text stream. Does Preflight just not like embedded CMaps?
I have uploaded a sample document to acrobat.com if anyone wants to take a look. It has several changes from the original description, in an attempt to root out the problem. Here is the URL:
https://share.acrobat.com/adc/document.do?docid=4284cd55-d710-411f-8a91-51359564a78b
Thanks again for any help.

Cshow problems in Distiller 9.1

Similar Messages

Maybe you are looking for