Windows Server TechCenter > Windows Server Forums > Clustering > New 3rd node to cluster, What is print server cluster group error message 'Failed to ugrade printer settings'
Ask a questionAsk a question
 

QuestionNew 3rd node to cluster, What is print server cluster group error message 'Failed to ugrade printer settings'

  • Friday, November 06, 2009 3:04 PMGeorge Perkins Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I have an Windows Server 2003 R2 active/active two-node file and print cluster with 3TB of file share data and about 600 printers (four cluster groups "virtual servers"). It has been running flawlessly over a year and I have been able to do administrative moves of the groups as well as have had a hardware-related failover event.

    To increase more capacity I added a 3rd node, the aim being an active/active/active cluster. First step was to add the 3rd node. That worked. I moved the 'Cluster Group' and the quorum drive Q showed up on the new node. I then moved a file server. No problems, all resources and the group moved over fine. I then moved a print server. No problems. Feeling confident I then moved another print server. I got a great number of the following message for a variety of printers and print drivers:

    Event Type: Error
    Event Source: Print
    Event Category: None
    Event ID: 22
    Date:  11/5/2009
    Time:  11:01:31 PM
    User:  NT AUTHORITY\SYSTEM
    Computer: FPNODE01C
    Description:
    Failed to ugrade printer settings for printer \\PCWMS07\BCMAS09Q,LocalOnly driver C:\WINDOWS\system32\spool\drivers\26a0a155-877f-475e-b905-19c8661b4a1d\DRIVERS\W32X86\3\UNIDRVUI.DLL error 1801.

    Event Type: Error
    Event Source: Print
    Event Category: None
    Event ID: 22
    Date:  11/5/2009
    Time:  10:43:42 PM
    User:  NT AUTHORITY\SYSTEM
    Computer: FPNODE01C
    Description:
    Failed to ugrade printer settings for printer PCPMR01Q driver HP LaserJet 4 error 1801.

    Notice that in one case the printer is identified with a UNC path (\\PCWMS07\BCMAS09Q) and in the other case only as the printer name (PCPMR01Q). Also notice the typographical error in the message "ugrade" not "upgrade". I've done some searchs on Google and Technet but can't find any clues as to what this is. I'm sure it is related to the fact that this is a cluster resource since that is the only variable that changed.

All Replies

  • Monday, November 09, 2009 5:54 AMTim Quan - MSFTMSFT, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
  • Thursday, November 12, 2009 4:20 PMGeorge Perkins Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I too had discovered the 839125 and 773827 articles you link to in your thread reply. If this were a client Windows XP computer and I were installing a new print driver, I would probably research what about the newly added printer was messed up. But what these articles don't do is help me understand why I would get these errors when adding a new node to an existing file and print cluster. Am I correct in my understanding that when the print server is created the first time on a new node it will copy the print spooler files (print drivers, etc.) and registry entries to the new node's Windows OS? Why would this process generate errors not seen on existing nodes? The message "Failed to ugrade printer settings for printer \\PCWMS07\BCMAS09Q,LocalOnly driver C:\WINDOWS\system32\spool\drivers\26a0a155-877f-475e-b905-19c8661b4a1d\DRIVERS\W32X86\3\UNIDRVUI.DLL error 1801." sounds as if the cluster service is unable to update the local files on the node. Why would that be? And how do I fix it?

    I have another theory: I got the above errors (a great many more than I pasted into the thread) because the client printers were powered off at the time I added my 3rd node to the existing file & print cluster. Would that explain the error messages?