We have a print cluster with a recurring problem (W2K Adv., SP2). On various printers (mostly HP and Tektronix) with different drivers, the queue will work fine for a while and then the queue will stall. There is no way that we can find to start it up again short of restarting the spooler which then causes the failover to the other node. One thing we've noticed is that when the queue stalls, we look at the queue and the "port" listing is blank. We can recreate the queue with a different port name and it works fine for a while. This happens with PCL and PS drivers for NT and 2000. I've heard of other departments with clusters having similar issues but no solutions yet. Microsoft couldn't give us an answer either. Their last susggestion was to make the drivers identical on both nodes. We're working on that now. Any other ideas?
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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Windows 2000 Print Cluster - stalled queue problem
- Thread starter ntmntm
- Start date
I don't know exactly how did you configure it. It looks like a configuration problem. What is with "same driver" on nodes?
Anyway, here are few ideas:
- you don't have to create locally defined printers on each node
- port configuration is shared via registry between the two nodes. So if you are saying that port information is volatile, then you should check that there are no clustering problems, like resource configuration errors, or problems with the quorum. Have a look in winnt\cluster\cluster.log too. Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, soon MCSE2k
Anyway, here are few ideas:
- you don't have to create locally defined printers on each node
- port configuration is shared via registry between the two nodes. So if you are saying that port information is volatile, then you should check that there are no clustering problems, like resource configuration errors, or problems with the quorum. Have a look in winnt\cluster\cluster.log too. Gia Betiu
giabetiu@chello.nl
Computer Eng. CNE 4, CNE 5, soon MCSE2k
- Thread starter
- #3
Thanks for the information.
MS looked through all of our logs and reg settings, including the cluster.log. They noticed that there are some different drivers on the nodes and suggest they be made the same.
Maybe you already know this but only the queues are created and shared on the cluster. The drivers are installed on the owning node when the queue is created and the same driver has to be installed manually on the other node(s). The drivers don't failover.
Everything in the cluster configuration appears to be in order and no errors are reported anywhere that I can find.
MS looked through all of our logs and reg settings, including the cluster.log. They noticed that there are some different drivers on the nodes and suggest they be made the same.
Maybe you already know this but only the queues are created and shared on the cluster. The drivers are installed on the owning node when the queue is created and the same driver has to be installed manually on the other node(s). The drivers don't failover.
Everything in the cluster configuration appears to be in order and no errors are reported anywhere that I can find.
- Status
Similar threads
- Locked
- Question
- Locked
- Question