Kyocera M6535cidn XPS Print error NEED HELP!

**Santander** · 01-06-2017

Originally Posted by cowboyjimmy

I forgot to mention that I am using KX driver on both machines.

May sound silly, but if you have the KX driver on both units why are they printing XPS?

**bronco31** · 01-06-2017

i get not just a few service calls about Kyo mfp stuck in "processing"... and then its the battle to find who is the offending PC or Mac or tablet that sent the screwy print job. (turning off the MFP power doesnt help cause the print job just returns a few min later!)

yet under Device Settings i always turn ON ... Auto Error clear at 30 seconds. Why doesnt the print processor say "OK this data arriving is in "error" state.. and dump it ? instead of throwing F000 or F24B etc??

**wragsdale** · 01-06-2017

You cannot get an XPS error unless you're printing from an XPS driver. I would heed the advice already given.

1. Turn off WSD.
2. Change the IP of the copier and make sure the workstations that need to print are on the most up-to-date KX driver with the new IP address.

Additionally, a F000 code is not a print processing issue. It is a communication error between PWBs. If you're getting intermittent F000 codes, then you have something else to address.

**wragsdale** · 01-06-2017

Originally Posted by bronco31

yet under Device Settings i always turn ON ... Auto Error clear at 30 seconds. Why doesnt the print processor say "OK this data arriving is in "error" state.. and dump it ? instead of throwing F000 or F24B etc??

If you're referring to "Form Feed Timeout," this only applies to documents where the end of job data isn't received and the machine will simply print what it has received. This is different from any of the F codes, which are fatal communication errors, because they occur when the engine software has crashed.

**cowboyjimmy** · 01-06-2017

Thanks Guys. I am still trying to work this out with your advice. I have to admit that this is over my head and I am sending this thread out to another that may be able to help me more. Keep the ideas coming and I will let you know my progress.

**bronco31** · 01-10-2017

Originally Posted by wragsdale

If you're referring to "Form Feed Timeout," this only applies to documents where the end of job data isn't received and the machine will simply print what it has received. This is different from any of the F codes, which are fatal communication errors, because they occur when the engine software has crashed.

1. nope..referring to "Auto Error Clear".. wondering why it doesnt work and the Kyo MFP will still throw F248 style codes!

2. Agree there must be a machine using the XPS driver in this OP case...

keep on keeping on all you road warrior techs!

**Santander** · 01-11-2017

Originally Posted by bronco31

1. nope..referring to "Auto Error Clear".. wondering why it doesnt work and the Kyo MFP will still throw F248 style codes!

2. Agree there must be a machine using the XPS driver in this OP case...

keep on keeping on all you road warrior techs!

If the unit is throwing F248 codes have you checked the print log to see what is being printed? And from where? Our experience has been that a unit that throws a F248 code that Auto Error Clear does not clear is usually from a mal-formed web page or one that contains a virus. Match up the F248 codes with the failed pint jobs in the log and I think you will find that they are trying to print a web page. Are they printing directly to the unit or through a server? Simply clearing the machine and getting it back on line will only lead to more F248 codes as the offending print job is still in the queue. Without clearing the print queue, especially on a server based print queue only keeps sending the bad job. This is where looking at the print job log will help you narrow down what the print job is and where it is coming from. Hope this helps.

**NeoMatrix** · 01-11-2017

Sounds like you may be getting web page deliberate over size font scripting forcing huge print pages an/or unknown fonts.

Clear the print spool directory on the offending PC's eg. :
In a DOS window do the following.

c:
cd\
c:\windows\system32\spool\PRINTERS
del *.*

HTH

**bronco31** · 01-13-2017

"Clear the print spool directory on the offending PC's en"

yes ...that IS the goal to to find the offending PC.

and these little C5400 or 7035 color printers dont have much in the way of Print Logs...

im going to lunch!

**qbert69** · 01-16-2017

Make sure the KX Print Driver is installed on the "problematic" computer. Take your XPS document and save it as a DIFFERENT FORMAT!.....such as PDF and try reprinting with the KX Driver!