SAMS-Disabling/Enabling

[Kirk Solano]

We have networked printers that often do not print when a print job is sent to them. When this happens we look at the status of the printer in SAMS and check if it is disabled/enabled. However, we've found out that these printer do not show as being disabled. To cure the problem though, we first disable it and then reenable it again. Then, the printer seems to print whatever was submitted again. This didn't used to happen. But not it happens to random printer intermittently. Anyone know the cause and cure? Thanks in advance.

[Edward Sedgemore]

Either the lp system has gotten confused which basically means you will need to do a fair bit of work to clear it up or else the lp daemon has received a funny status back from the remote printers.

Check the log /var/adm/lp/log and grep it for any return codes; grep "rc=" /var/adm/lp/log
If you find some then you need to investiate their value.
(I hope you have lp logging on! - to do this lp needs to be started as; lpsched -v -a)

If its a problem with your lp setup I recommend using the print spooler backup facility in SAM and then the same facility to restore your entire lp setup, this should clean out any inconsistencies which may be causing your problem.

[Vincenzo Restuccia]

Try remove printer and reinstall it.

[dan mcelroy]

Last week we had a similar problem...The user ran out of labels and turned the printer off to replace them. This apparently confused the system in thinking that it was still online when the user turned it back on. By dis-enabling, then re-enabling it, the printer was able to go along its merry way. So, ask if the users are turning the printers off occasionally. That may be the problem?