Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Print Queue, RE: Novell 5.2

Status
Not open for further replies.

MLENDER

MIS
Mar 24, 2000
10
US
Every job is remaining in the print queue until I purge the list. This happened for about 3 weeks and stopped for about 2 weeks. Now it is happening again. The queue lists every job; except, for the jobs that have already printed, in the "Progress" column it says "0 bytes of xxxKB" (xxx is the actual size of the job). It shows up on every user's computer, not just mine. I do not see it happening on other queues, just one.

A really weird thing happened at the start of this problem: the list would not purge, so I rebooted the Netport. When I did that, my jobs printed again (but no-one else's). This happened a couple of times, but now I can purge the list successfully and nothing re-prints.

Thank you.

P.S. I have Client 3.2; others do not. Windows version varies: 95, 98, XP.
 
Sounds like you have a corrupted print queue which may be causing the print server to hold onto the print job or not service it. i recommend deleting the queue and re-creating it. This by far would resolve most print problems.

I would also check the print server as well. If job goes into queue but sits there, problem is with it being serviced, if print job goes into queue then goes to printing but does not, then more than likely the print job is getting corrupted between the queue and ps. However, being that this may be host specific (pc), I would still lean toward re-creating the queue and ps.

The only other thing you may want to do before any of the above is run ds-repair on all of your servers. Including those that do not have replicas. You may find erros within the NDS info that is stored on a server.

Little lesson on NDs: If you repair only the Master, it only fixes the Master, does not fix anything else. So you need to repair not only the servers with read/writes but also those without a replica becuase they hold external references and backlinks to other servers. If one of these encounters some sort of problem, then you could encounter similar problems.

HTH Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com

With more than 10 years experience to share.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top