So I showed up with all the usual suspects: firmware, image memory, HDD, main PWB. I actually see the code for the first time (third call).
"Call For Service" (Self-diagnosing) and at the bottom of the screen "cf248".
First I tried the firmware, then image memory, then format HDD, then repl HDD ... then I my brain began to work. I noticed that when the NIC connected, for 1/2 second a flie name was displayed "Executing print job --------------.pdf", then the error. Always the same file name!
There is no server on-site, just a router, so I have no clue which of the 25+ PCs currently in the office is repeatedly sending the same print job, but I do know that it is here on-site, and that it's On, and on the network. To add to the challenge, there are 40+ laptops in and out of this office, depending on the time of the day, and who's working where. And the cast changes daily.
Here's a little trick I discovered totally by accident. I disconnected the MFP, then set a static address on my laptop same as the MFP. When I connected the cable the sending PC is satisfied, and quits sending. Of course, my laptop can't do anything with a PCL print job but I don't care about that. I just want to clear the queue. Then the code vanishes and stays gone. It sure would be nice to know which PC has sent the job. The next logical step is to delete and reload that specific print driver.
I have come to the conclusion that it's a corrupt print driver or corrupt print job that's pulling the cf248. The print history does not store any of these erroring print jobs, and I've seen it at least 6 times (wouldn't that have been convenient?). The Error Log does record the error events. Has anyone else seen this? =^..^=
"Call For Service" (Self-diagnosing) and at the bottom of the screen "cf248".
First I tried the firmware, then image memory, then format HDD, then repl HDD ... then I my brain began to work. I noticed that when the NIC connected, for 1/2 second a flie name was displayed "Executing print job --------------.pdf", then the error. Always the same file name!
There is no server on-site, just a router, so I have no clue which of the 25+ PCs currently in the office is repeatedly sending the same print job, but I do know that it is here on-site, and that it's On, and on the network. To add to the challenge, there are 40+ laptops in and out of this office, depending on the time of the day, and who's working where. And the cast changes daily.
Here's a little trick I discovered totally by accident. I disconnected the MFP, then set a static address on my laptop same as the MFP. When I connected the cable the sending PC is satisfied, and quits sending. Of course, my laptop can't do anything with a PCL print job but I don't care about that. I just want to clear the queue. Then the code vanishes and stays gone. It sure would be nice to know which PC has sent the job. The next logical step is to delete and reload that specific print driver.
I have come to the conclusion that it's a corrupt print driver or corrupt print job that's pulling the cf248. The print history does not store any of these erroring print jobs, and I've seen it at least 6 times (wouldn't that have been convenient?). The Error Log does record the error events. Has anyone else seen this? =^..^=
Comment