Phaser 4622 - jobs being "Held By System"

[Joe Arseneau]

If everything is the same but something is different is there a difference in firmware level?

Besides firmware the only thing else is bad RAM/HDD.

[jimmyb_nyc]

Thanks for the response. We actually already have it set to use LPR and are using the Pull Print PS driver. From the looks of it, the user sends basic Text based ASCII/Terminal type files, looks like from a Mainframe app, so each job is about 35K.  We have about 500+ 4622s running the same firmware, set to use LPR, and everyone's printing with the same version PS driver. This is the first printer we've run into where the jobs go into a Held state for no apparent reason. 

[Joe Arseneau]

It's a little machine with limited memory and it si filling the cache.

Streamline submissions by switching your printer ports from RAW to LPR and disable SNMP

Use PS instead of PCL

If using Acrobat/Reader make sure Print as image is not selected in the Advanced window of the application.

The printer is running on 256MB RAM.

Print jobs when spooled tend to be increased by 10x.

So one 2MB file when printed will spool to 20MB.

20 of those is 400MB, the printer may or may not have an issue at that point, but if using a RAW port you introduce a 30 second timeout into the equation. Job one fails to RIP in time and the other other jobs fill the space it needs to do so and job 1 fails, jobs 2-20 cannot do anything because job 1 is stuck leaving you with the first job waiting for something to give it space to RIP, and jobs 2-20 that caused the issue waiting for job 1 to finish to allow them to start.

The LPR port will solve the timeout, the PS driver will help reduce the spooled size and make it easier for the printer to interpret at the same time.

It may or may not solve the issue, but nothing I listed will make it worse.

If it is wireless I can't imagine a scenario where 20 simultaneous jobs will ever reliably print.

[jimmyb_nyc]

Hi - running into an issue where a Phaser 4622, when printing 20 or so jobs at a time, stops and goes into a Held state. Resources are a plenty, so it's not being held for a lack of paper. Toner is at 89%, Drum is at 81%. No other alerts are showing. Looking at the Active Jobs from the device web page, the first job says "Held By system", the others are "Pending". Any thoughts as to why they would go into a held state?  The user ends up reprinting the jobs at another printer. Running System 35.011.26.000.