--------------------
From: (e-mail address removed) (JPK)
Newsgroups: microsoft.public.win2000.printing
Subject: Re: Adding printers to a cluster
Date: 22 Dec 2003 07:48:42 -0800
I'm experiencing the same problem when trying to add a HP 1300n driver
to a Windows 2003 clustered print server. I loaded the driver for the
printer on both nodes and was able to print a test page from each one
to the printer. However, when I try to add the printer to the virtual
server, I get the same error message, "Unable to Install Printer. The
print processor does not exist."
Not sure if this is relevant, but the software that came with the
printer installs a "HP Standard TCP/IP Port" on each node. When I
attempt to load the printer through the virtual server, however, the
only option I get is for a "Standard TCP/IP Port".
JPK
Alan Morris\(MSFT\) said:
The cluster nodes themselves need the print processor. Install the driver
on each node, then add the printer to the clustered virtual print server.
--
JPK,
When trying to install a printer driver that installs a custom Print Processor to a Windows 2003 cluster we will get a message
like the one below:
Unable to install printer. The print processor does not exist.
The reason for this is cluster does not support the addition of custom Print Processors.
The solution is to contact the manufacturer for a version of the driver that is Cluster aware and does not try to install the
custom Print Processor.
To work around the issue we can install a driver that comes with Windows 2003, then go to the properties of this printer, go
to the Advanced tab, click the New Driver button and then point to the driver from the manufacturer for the printer. This
will normally install the manufacturer's driver without attempting to install the custom Print Processor.
Bill Peele
Microsoft Enterprise Support
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread
from which they originated.