Printer Filter Failed

[JamesH]

Hi All,

We are facing a strange issue, it started when we noticed that the clocks on a few of our machines were incorrect. During the investigation, we discovered that the admin accounts on the machines had become standard. We fixed this issue and determined that the time issue was due to a corrupt "localtime" file. We fixed this but there was fall out, iTunes would not launch (corrupt plists) and we could not print unless we print from Adobe products.

When printing, the queue returns with "Stopped - 'Filter' failed". This happens regardless of the protocol used, whether they have the latest drivers or not or what printer manufacturer it is. The log shows the following:

D [13/Sep/2018:18:44:35 +0100] [Job 28] PID 35467 (/Library/Printers/Xerox/Filters/xrpdfprefilter) did not catch or ignore signal 13.
D [13/Sep/2018:18:44:35 +0100] [Job 28] Page = 595x842; 14,14 to 581,828
D [13/Sep/2018:18:44:35 +0100] [Job 28] pstoxrps filter done, exiting... D [13/Sep/2018:18:44:35 +0100] [Job 28] PID 35470 (/Library/Printers/Xerox/Filters/pstoxrps) stopped with status 1.
D [13/Sep/2018:18:44:35 +0100] [Job 28] Hint: Try setting the LogLevel to "debug" to find out more.
D [13/Sep/2018:18:44:35 +0100] [Job 28] PID 35471 (/usr/libexec/cups/backend/lpd) exited with no errors.
D [13/Sep/2018:18:44:35 +0100] [Job 28] End of messages
D [13/Sep/2018:18:44:35 +0100] [Job 28] printer-state=3(idle)
D [13/Sep/2018:18:44:35 +0100] [Job 28] printer-state-message="Empty print file!"
D [13/Sep/2018:18:44:35 +0100] [Job 28] printer-state-reasons=media-empty-warning

Any ideas as I am at a loss. Thank you for your time.

[abutterman]

Have there been any updates on this? I'm experiencing what appears to be possibly the exact same issue. We deployed a large number of new Macs in the last few weeks through DEP/Jamf and there were some reports of the local admin account that we created being turned into standard accounts. I also just received reports of the filter failed error when printing. We do have a script that sets the time server to our on prem server and we did also notice extreme slowness/tomcat issues in the web console and policy deployment. Jamf recommended we flush a large amount of our logs as we are running a single server rather than clustered. I just flushed the logs and am hoping for improvement...