Printqueues unaccessible after SP1



I installed SP1 on my first node of my test printcluster (2 nodes, 1 active,
1 passiv).
It seemed that all worked fine.
I installed it on the second node and don't recognized my problem.
I can connect the queues from clients, print and work on the
active node ( change queue properties etc. ). Failovertest was successful.
The logical hosts and the printqueues are visible at the passiv node also
but than
I can't access the printqueues.
I always get the errormessage:
"Operation could not completed. Either the printer name was typed
incorrectly, or the specified printer has lost its connection to the server".
The Cluster Administrator GUI says all hosts online, no errors.
If I use the command-line Clustertool to check the state of a group I
receive the errormessage: ”System error 5013 has occurred (0x00001395). The
cluster group could not be found.”
Nameresolution is Okay.
I deinstalled the servicepack on my productiv system and the problem went
away.

Know anyone the reason ?

Regards,

Rudolf Kniess

.



Relevant Pages

  • Re: Shared printer
    ... server or clustered name as Alan suggested., This should add to both physical ... physical boxes to use the print queues. ... be resolved or having a print cluster is pointless. ... If you can connect to it then goto printers and faxes. ...
    (microsoft.public.windows.server.clustering)
  • Re: Queue Manager in a heterogeneous cluster
    ... But I had no queues anymore. ... And of course we will as soon as possible upgrade the other ... VMS 6.2 notes, because most of the reasons to stay with 6.2 (last free ... > (like monitor cluster). ...
    (comp.os.vms)
  • Re: Broken Exchange 2k3 Cluster
    ... the backend. ... We tried rebooting the Front End servers one at a time with no ... The queues had an error message that referrenced DNS however I forgot ... My boss suggested failing over the cluster to ...
    (microsoft.public.exchange.admin)
  • Re: system job que manager not running
    ... cluster so when i ran the logical .com file (which also contained DSE ... kept getting bad parameter errors. ... rerunning the logical file and starting the queues sorted it. ... I think you confused it with the parameter for starting a queue manager ...
    (comp.os.vms)

Loading