Windows Server - Clustered printer missing but share still exists

Asked By Peter J. Dickason, MCSE

08-Feb-10 09:34 AM

Hi all,

We have a Win2k3 x64 cluster with 2 nodes for print services.  We have a
shared printer that is causing me fits.  This printer was created earlier
but it is missing now.  I could not explain why it is missing so I just went
ahead to recreate it.  So I select the IP address that was there from the
previous printer and named the printer and the sharename the same as it was
before.  It then proceeded to complain that the sharename already exists.  I
did a net share from the node and sure enough it was listed.  Now how in the
world can a share be out there that is not defined to any printer?  The
printer is definately not in the printer list so I begin to wonder what
corruption I could have that would cause a printer to disappear from the
list but the server still thinks its there?  Any ideas?  I currently only
have 250 printers defined but the number will grow into the thousands so
things like this does not give me warm fuzzies about the whole thing.

Thanks
Pete

08-Feb-10 01:11 PM

it is listed under the LanmanServer\Shares
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares

most likely you are missing some required print driver resource on one of
the nodes.  The printer most likely cannot be enumerated after failure due to
the missing resource.



http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

09-Feb-10 12:30 PM

Hi Alan, thanks for the reply.



Yes they are.


I do not install drivers on either of the nodes but rather the cluster
itself which gets stored in sanvol1\PrinterDrivers.  Since this is the
shared location I do not understand how it can be missing on either node.
How do I correct the driver as the printer does not appear in the pritner
list?


Pete

12-Feb-10 04:39 PM

Anybody?

11-Apr-10 09:19 AM

Hi,

A good practice is to double the current size of the Clusdb file to
determine the Reset quorum log at value. For example, if the current size is
already close to 8,192 kilobytes (KB), increase the maximum size of the Reset
quorum log to 16,384 KB (16 megabytes). Make sure that you enter the value in
kilobytes.
The above is one of the reason for not finding print queues if you failover
to other node but it exists in registry.

Cheers,
AD