We currently have a problem with a spooler on a two node cluster. Occasionally some of the printers 'hang,' which we believe is cause by volume of print requests being processed combined with the variety of printer drivers. By stopping and restarting the printer spooler the risk of this problem is minimised. On the non-clusterd printer spooler we automate this process with the command line scripts net stop "printer spooler" and net start "printer spooler," however with we cannot simply use this commands with a cluster because it also stops the cluster active resource. Does anyone know what script we can use to stop the printer spooler, restart the cluster active resource and then restart the printer spooler? Alternatively does anyone know of script to simply restart the cluster active resource?
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 John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Restarting a Printer Spooler on a Cluster 1
- Thread starter Adeboy
- Start date
MikeBatters
Technical User
Are you running W2000 or W2003 clusters?
Mike
*************************************
Remember - There is always another way..........I just haven't found out what it is yet!
![[yinyang]](/data/assets/smilies/yinyang.gif "[yinyang] [yinyang]")
Mike
*************************************
Remember - There is always another way..........I just haven't found out what it is yet!
- Thread starter
- #3
MikeBatters
Technical User
Hmm....That will be more problemattic although do-able with a bit of a hack.
If you ensure that the Spooler resources in the cluster are set to "Do not affect group" you can do the "net stop" "net start" without making the Virtual Server fail over. If you set the Virtual Spooler to restart on failure it will all recover automatically.
It is not the cleanest way of doing to job however there are no script or command interfaces that allow resources to be taken offline or brought online in 2000.
All the functionality you want is in 2003 clusters though....for future reference.
Mike
*************************************
Remember - There is always another way..........I just haven't found out what it is yet!
If you ensure that the Spooler resources in the cluster are set to "Do not affect group" you can do the "net stop" "net start" without making the Virtual Server fail over. If you set the Virtual Spooler to restart on failure it will all recover automatically.
It is not the cleanest way of doing to job however there are no script or command interfaces that allow resources to be taken offline or brought online in 2000.
All the functionality you want is in 2003 clusters though....for future reference.
Mike
*************************************
Remember - There is always another way..........I just haven't found out what it is yet!
-
1
- #5
Hello Adeboy,
I think you mean the spooler hangs.Printer cannot hang.Most of the reason are 3'rd party print processors and language monitors.A spooler dump can be usefull to find the cause of the problem.
You can create a spooler dump with adplus.vbs.Before, you should install debugging tools for windows.
I know that "HP Language Monitors" (HP Master Monitor) is is mostly causing the spooler to hang or crash.This component should be deleted from the registry and the .dll from the spool folder.
My advice is to set winprint as default print processor on all the print queues and remove the language monitors.This is not easy in a cluster environment.If you are interested in to clean and optimize you printer environment I can send you an action plan.
The 3 rd party language monitors are listed under the cluster registry hive / spooler guid.You can also search the microsoft knowledgebase for articles.
There are some articles that describes how to remove language monitors in a non-clustered environment but you will not find an article that describes how to clean language monitors on an clustered environment.This is much different.
Kind regards,
Cengiz Kuskaya
I think you mean the spooler hangs.Printer cannot hang.Most of the reason are 3'rd party print processors and language monitors.A spooler dump can be usefull to find the cause of the problem.
You can create a spooler dump with adplus.vbs.Before, you should install debugging tools for windows.
I know that "HP Language Monitors" (HP Master Monitor) is is mostly causing the spooler to hang or crash.This component should be deleted from the registry and the .dll from the spool folder.
My advice is to set winprint as default print processor on all the print queues and remove the language monitors.This is not easy in a cluster environment.If you are interested in to clean and optimize you printer environment I can send you an action plan.
The 3 rd party language monitors are listed under the cluster registry hive / spooler guid.You can also search the microsoft knowledgebase for articles.
There are some articles that describes how to remove language monitors in a non-clustered environment but you will not find an article that describes how to clean language monitors on an clustered environment.This is much different.
Kind regards,
Cengiz Kuskaya
- Status
Similar threads
- Locked
- Question
- Locked
- Question
