3 Phaser 6280's with the same 116-324 Error message

[RichM]

Another possible cause is garbage data on the network wire. Had the same issue and error code, but found its CAT5 cable had big kinks in it and the network lights were blinking erratically. Replaced network cable and it's working fine now for 8 users. -Rich in CLE OH

[Kimzi]

Hi, jltholdings.

Glad it worked out for you!

Best Regards

Kimzi

[jltholdings · Accepted solution]

power cycling did not resolve the problem for one of my offices with this problem. But clearing the print queue did fix the problem.

We powered it down, cleared the queue, powered back on.

Thanks Kimzi.

[Kimzi]

Hi!

116-324 is a common problem, and what I can understand by reading ur explanation is that it only shows up when connected through LAN.

Which means you have a corrupt job in the queue on one of the computers, remove this job and everything will work again.

99% of the problems with this fault code is a corrupt job hiding somewhere in the queue on the clients or the server.

Everytime you connect the printer the same job will try to print, as the job is corrupt the printer cannot read it and will go berserk :)

Thanks!

[CherylO-Xerox]

Hi Chris,

Thank you for using the Support Forum. Are you able to ping the printer?  If so then you would need to please consider contacting your support centre for further assistance.  If you are unable to ping the machines then please contact your administrator to troubleshoot the network. 

[cholubaz]

We have 3 Xerox Phaser 6280's and all three started showing a 116-324 Error message a few days ago.

So far I have updated the firmware, Shut them down and rebooted and even left them off for a extended period of time. I have tried all three types of print drivers although that has nothing to do with it because the message appears even without anyone trying to print to them.

What I did find was that the error only apprears if its plugged into the network.

Our network is segmented by VLAN's and the printers are on their own VLAN and nothing network related has been added to that VLAN anytime recently.

This morning I rebooted our Cisco 4506 core switch along with the print server and still the problem exists.

Has anyone ran into this before and have been able to solve it?

Cheers,

Chris