I've had to write my own printer driver and print spooler for a Ruby on Rails web app that prints thousands of complex court-specific legal filings every day. After two years of clean running, I'm getting this error reported via SNMP on just one of the identical production printers. All the printers are the exact same model running the exact same firmware revision, but one of them has printed more pages than the others.
Everyone on this thread is quick to blame CUPS or Apple, but in my view, the printer firmware is the culprit. It simply should not be reporting warnings as errors. Sure, the driver can be "fixed" (ie "broken", technically speaking) to treat that specific reported "error" as "a status reminder, not an actual error", but printers shouldn't lie about what's wrong with them. I have a lot of sympathy for folks who have to write the drivers for devices that are sloppy with SNMP. Basically, you have to accomodate the bugs in certain firmware versions of certain printers in order to overlook what that device says is going on, because it probably isn't true. Except sometimes it might be...
For fun, open a terminal and type:
snmpwalk -Os -c public -v 1 192.168.0.142
where you replace the IP address with the actual address of the printer on your network. Then try to sort out the 1,000 accurate values from the (occasionally) inaccurate one.
In the end, the customer just wants it to work, and they blame the OS vendor for the device's bugs. I suppose that is natural enough, but at least this little rant gives you some perspective on the problem.