Forum Discussion

PeterBretherton's avatar
PeterBretherton
Level 2
13 years ago

Cluster Server v2 doesn't detect Print Spooler W2K

One for all you traditionalists out there :-)  I've a two node cluster running Cluster Server v2.00 on Windows 2000 and occasionally when failing a resource group over, I get the following error :-

VCS:230012:PRINTSPOOL:XXXX_PS:clean:Could Not detect Spooler on Machine XXXXX.

The resource then faults and the resource group can't be brought on line.  I'll be grateful for any help.

Thanks

business continuity
Cluster Server
Clustering
Error messages
Failover
  • Wally_Heim's avatar
    Wally_Heim
    13 years ago

    Hi Peter,

    I understand where you are coming from.  You can check out the ToleranceLimit and the RestartLimit attributes for the affected resource(s).  The ToleranceLimit tells VCS to ignore a number of monitor cycles that return as offline and not to fault the resource right away.  The RestartLimit tells VCS to attempt to restart the resource a number of times before faulting it.

    I hope these help.

    Thank you,

    Wally

  • Wally_Heim's avatar
    Wally_Heim
    Level 6
    13 years ago

    Hi PeterBretherton,

    The product and the OS that you are inquiring about is very old and has not been supported in a long time.  I'm not sure that you will find many people here that have supported it and even less that are able to assist you with your issue.  You might want to consider upgrading to a supported version of the OS and of cluster server if you are not able to resolve your issue.

    With that said, I would recommend that you check your event logs for Servcie Control Manager entries to see if the Spooler service is actually stopping or not during the time in question.  If the spooler services is actaully stopping and hopefully restarting, then you will need to increase the RestartLimit limit on several of the printshare/printspool service groups resources so that they will attempt to restart when the resources.  If the service is not stopping then you can try increasing the ToleranceLimit.

    Thank you,

    Wally

  • PeterBretherton's avatar
    PeterBretherton
    Level 2
    13 years ago

    Hi Wally,

    Thanks for the reply.  I appreciate my systems are a bit long in the tooth and I'd like nothing better than to upgrade but sadly the application running on this cluster says "No".  The Print Spooler service on the affected node appears to be up the whole time.

     

    Cheers

    Peter

  • Wally_Heim's avatar
    Wally_Heim
    Level 6
    13 years ago

    Hi Peter,

    I understand where you are coming from.  You can check out the ToleranceLimit and the RestartLimit attributes for the affected resource(s).  The ToleranceLimit tells VCS to ignore a number of monitor cycles that return as offline and not to fault the resource right away.  The RestartLimit tells VCS to attempt to restart the resource a number of times before faulting it.

    I hope these help.

    Thank you,

    Wally