Thank you for using the Support Forum. Please take a look at this blog article for information on the pros and cons of the PostScript and PCL drivers.
That is up to the end user. Typically I prefer PS, but anyone using AutoCAD, Quark, Corel, Excel etc typically go PCL. Just depends on your workflow, I primarily deal with much larger DocuColor machines so PS is prefered due to the increased color handling.
Thank you for this information. We will try it out immediately. We have the printer loaded using PCL, would PS be the better choice?
It could be defective but the more likely thing to do is give it a different IP address, then redirect the drivers to the new IP.
The code is a catch all for network issues, but typically it is a job with unexpected data, which can happen when a printer is placed in the spot of another on a LAN for convenience. (Occasionally causes SNMP errors due to same IP but different Hostnames)
Other possible options are to disable Advanced Printing Features in the driver properties
And enable Download as Softfont in the Printing Preferences
If all that changes nothing you may have a defective device, but all of the options I listed here can only improve things so they are worth trying.
We recently deployed a replacement Phaser 6500 and almost immediately started receiving Controller Errors no matter what the print job, web site, Word, Excel, didn't matter. The previous Phaser 6500 only experienced the issue a few times in just over a year. Our public computers and the printer are on a VLAN and we use Smart Shield for the computers to work off of a virtual image. When it occured yesterday, the staff shut down all the public computers and the printer. Upon restart a user was able to print and email without problem but a staff member received the Controller Error after submtting a Word document containing "The quick brown fox jumped over the lazy dogs back." The problem does not occur on any one computer but seems to be on all of them. Again, not a real issue until the replacement 6500 was installed. Staff reported this morning that yesterday afternoon the error occurred 7 times in 30 minutes. We've already done the driver thing, removed the printer reinstalled the printer. I can ping the printer without problem. It seems to be getting worse. Do I have a defective printer?
Solved! Go to Solution.