Want to highlight a helpful answer? Upvote!

Did someone help you, or did an answer or User Tip resolve your issue? Upvote by selecting the upvote arrow. Your feedback helps others! Learn more about when to upvote >

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

rekruse Author

Level 1

12 points

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

Best reply

VikingOSX

Community+ 2024

Level 10

111,809 points

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.

View in context

41 replies

rekruse Author

Level 1

12 points

Dec 14, 2017 11:20 AM in response to alexandraswenson

The upgrade to v5.1 has been tried on multiple computers in our environment, but we did not see an improvement.

maurpra

Level 1

8 points

Dec 19, 2017 1:13 AM in response to maurpra

Update: just noticed HP has posted a further new firmware revision 3.9, for M60x series as of today. Not yet downloadable from the support page but worth to test as soon as.....

maurpra

Level 1

8 points

Dec 19, 2017 8:56 AM in response to maurpra

Managed to install latest firmware revision 3.9 for the M605. The problem is still present. Not a solution...

Gormo

Level 1

4 points

Dec 21, 2017 1:08 PM in response to maurpra

I concur!

Jan 12, 2018 4:40 PM in response to rekruse

Same symptoms. From iMac, mid 2015; iMac, late 2012, Macbook Pro w/touchbar 2017. Common denominator, High Sierra.

techZili

Level 1

4 points

Jan 26, 2018 6:02 AM in response to rekruse

I had the same problem.

I replaced the font Calibri and the problem was solved.

JLG89

Level 1

104 points

Feb 6, 2018 5:51 AM in response to shuliakovsky

The problem is that the AirPrint driver won’t allow you to configure printing across subnets; you have to be on the local network.

JLG89

Level 1

104 points

Feb 6, 2018 6:20 AM in response to shuliakovsky

That just means your internal routers are configured to pass multicast. That’s not an option for many situations, e.g. VPNs or multi-site that must route across the public internet.