Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Postscript error on print jobs to HP printers ( undefinedresult )

We've noticed an increasing number of issues with our users experiencing the following postscript error when printing to our HP printers:

ERROR: undefinedresult

OFFENDING COMMAND: show

Note: sometimes the offending command will be 'xshow'.


-We've seen this happen on 10.10, 10.11, 10.12, & 10.13.

-This has been confirmed to occur on the following HP models: M602, M603, M605, M651, M680, M880.

-Problem persists regardless of the postscript printer driver used.

-We've successfully printed the same offending files to other printer manufacturers (using the same 'Generic Postscript Printer' driver).

-Updating the firmware on devices has not resolved the issue.

-Updating the HP Printer Software to 5.1 (HP Printer Drivers v5.1 for OS X) has not resolved the issue.

-Resetting the Print System from System Preferences has not resolved the issue.


Note: in our printing environment, we are set up to only use postscript drivers.

MacBook Pro with Retina display, macOS High Sierra (10.13)

Posted on Nov 14, 2017 6:04 AM

Reply
Question marked as Best reply

Posted on Nov 15, 2017 12:10 PM

HP has released a new HP Easy Start today (2017-11-15) for the M602 device. You might check the other models in your original post, to see if the same is true. I would install and run these to see if they find new driver code for the respective models.


Word .docx documents created on Mac or Windows do not embed fonts, but rather use font references. If a Windows created .docx attempts to make a faux font (italic, bold) from an installed font that does not offer that font face on Windows, then printing that document on a Mac will have an issue because the font won't exist either.


If the .docx was created in Word 2008/2011 for Mac, then the font reference will point to a System font location where that Office package installed the Microsoft fonts. If this document travels to a Mac that does not have the Office 2008/2011 fonts installed, but instead either has no Office installation, or Office 2016 for Mac, then again, the Microsoft fonts won't be found. Office 2016 stores its fonts within each application bundle.


Conversely, if one creates a .docx with Office 2016 for Mac, and that .docx is printed on a Mac that only has Office 2008/2011 installed, then it won't find a font that it thinks is stored internal to an Office 2016 Word application.


Computing used to be easier.

41 replies

Feb 6, 2018 6:45 AM in response to JLG89

1. no multicast are using while printing. And my router does not permit multicast.

2. it is non secure print across the public internet - there is IPSec tunnel (for example) for that and AirPrint works perfectly via IPsec (I had checked it right now) - I had print file from macbook situated in Belarus to printer situated in USA without any problems.

3. If you are using multi-site configuration you should open IP address and some TCP ports because of network printing. In case AirPrint driver you also should open IP of the printer and may check what current ports are using via i.e. tcpdump

Feb 6, 2018 7:24 AM in response to shuliakovsky

If you're able to auto-discover AirPrint printers on other subnets, then your network is either passing multicast, or your local DNS is configured with all the necessary A/PTR/SRV/TXT records for off-subnet Macs to search for the printer services using DNS.


You are correct that it is possible to manually create an IP printer using the AirPrint protocol, and print to a remote printer (which I had never tried, thank you for pointing it out). With our HP printer, that appears to work properly.

The OP was trying to determine why the non-AirPrint HP drivers are throwing Postscript errors. It may be that Apple and HP are expecting us all to just switch to AirPrint.

Feb 15, 2018 11:54 AM in response to rekruse

I've found that a soon-to-be-released firmware version is supposed to resolve the issue. But that would need to be installed on each printer by someone who manages the fleet or individual printer. Word is that this should be release near the end of Feb 2018, but there are different timetables for Futuresmart 3 and Futuresmart 4 devices.


Also the beta release of 10.13.4 seems to resolve the issue. But I'm not sure what the release date for that is either.


Another workaround, is to open the .PPD file being used by the printer and find "*TTRasterizer: Type42". Then change "Type42" to "None". There may be some permissions issues to deal with, when making this change.

Feb 27, 2018 11:35 AM in response to rekruse

I applied the most recent updates for Microsoft Office and printing on my HP LJ M604 is now working again using the PS driver and firmware from Dec'17. The MS Office release notes do not have details about any printing issues addressed: Release notes for Office 2016 for Mac - Office Support I am wondering if the issue has been resolved with this MS update or if others still have it.

Feb 28, 2018 2:50 PM in response to rekruse

Found this on an HP site, and this worked for us on a M551:


From the Finder, select Go > Go to Folder...

In the dialog box, enter: /etc/cups/ppd

In the folder that opens, you should see a .ppd file with the name of your printer -- open it in TextEdit (just drag the file onto the TextEdit app)

Look for the line *TTRasterizer: Type42

Change "Type42" to "None"

Save (may need to replace and remove the .txt to deal with permissions)

Postscript error on print jobs to HP printers ( undefinedresult )

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.