E
Ed Lother
Greetings,
Any solutions / recommendations for the following???
*SYMPTOM: Unable to add HP 4100, 4550, or 4050 printers to
W2K Cluster
"Printer driver could not be installed" "The
specified Print monitor is unknown".
Unable to add HP 4100, 4550, or 4050 printers to W2K
Cluster
Nothing relevant found searching for these two strings in
MS Premier KnowledgeBase.
This is not a domain controller.
W2K, SP1 CL380 cluster with 1Gb RAM, and dual 700Mhz
processors per node with 3 18Gb Drives in a
RAID 5 array. The C:\ drive is 4Gb. Running Win2k
Advanced server with SP1 and a couple of
hotfixes. They are currently unable to add any more
printers to the server and the only significant event that
has occurred since this started was the installation of
Print Services for Unix. This was done a couple of days
ago. They currently only have 25 printers assigned to
this cluster but will have many more in the future.
When trying to install a new printer the wizard allows
them to create a port and when they select the driver it
says complete however they get an error msg that says
"Printer driver could not be installed" "Print
monitor is unknown".
Nothing relevant found searching for these two strings in
MS Premier KnowledgeBase.
[ANALYSIS] Other that the Print Services for Unix being
installed there doesn't appear to be much relevant data
regarding this problem. The problem didn't happen before
a couple of days ago, and the only significant event that
occurred since then is the addition of these services. I
asked if they had
reinstalled SP1 after installing the Print Services for
Unix and the customer had stated that they had not. I
explained the general philosophy of Service Packs with
relation to native services that come with the OS.
Service Packs generally need to be reinstalled when adding
any of these services.
We tried ....
1) Install the printer locally on each node using the Add
Printer Wizard.
2) On each node specify the correct LPR or TCP port (may
need to create the port)
3) Do not share the printer from any of the nodes
4) Then go to \\ and click on Printers
5) Add the printer via the "Add Printer Wizard"
6) At this point you can share the printer with a unique
name.
BUT>>>>> we dont get this far. Fails when goes to load
driver
"Cannot Install Driver, Print Monitor Unknown"
OK, PJ solution was to use Microsoft driver, but there is
no driver from MS.
HP driver for 4100 and Windows 2000
Downloaded the drivers, LaserJet 4050.
Installed locally, not shared.
It created a new key called "HP LaserJet 5 Language
Monitor"
The key has an entry on the right showing Driver:REG_SZ:
HPDCMON.DLL
Tried:
How to Add Digital Print Monitor to Windows 2000 [Q232822]
Print Spooler Support on Microsoft Windows 2000 Server
Cluster Q228904
Tried installing locally - shared and not shared - fails
CUSTOMER APPLIED SP2, no change.
I know we tried this....
1) Install the printer locally on each node using the Add
Printer Wizard.
2) On each node specify the correct LPR or TCP port (may
need to create the port
3) Do not share the printer from any of the nodes
4) Then go to \\ and click on Printers
INSTEAD of using the virtual name, try the machines
NetBIOS name. If we
cannot even install locally with server NetBIOS, then we
do not have a
cluster issue, we have a HP driver issue. If this is
successful then the
drivers will be on the box and we should not have any
trouble virtualizing
the print spooler.
[UPDATE]
I escalated this up to M$ today. The following items have
come out:
*This is only happening on clustered servers.
*All other servers have no problems installing the
drivers, etc.
The customer is currently in the process of renaming
a .dll and attempting
to reinstall the driver. THe customer just came back and
said that that didn't help.
We have now been transfered to a cluster engineer.
He believes that he has seen this problem before. He is
researching...
Speaking with Microsoft. They are having the cust cleanly
remove the printer, and then attempt to add the printers
back as if non-clustered on each node and then share
them. This sounds like something that was tried before,
but the customer is going to try again.
Virtual name, add printer wizard: define via virtual name,
drivers are propogated.
Cluster workaround: preinstall drivers so they're already
there. Then add printer with
port and driver already in place.
Confirmed that this procedure worked for this printer.
He has to add a few others, and is assuming additional
printers will work using the same approach.
Thanks for taking a look...
Ed
Any solutions / recommendations for the following???
*SYMPTOM: Unable to add HP 4100, 4550, or 4050 printers to
W2K Cluster
"Printer driver could not be installed" "The
specified Print monitor is unknown".
Unable to add HP 4100, 4550, or 4050 printers to W2K
Cluster
Nothing relevant found searching for these two strings in
MS Premier KnowledgeBase.
This is not a domain controller.
W2K, SP1 CL380 cluster with 1Gb RAM, and dual 700Mhz
processors per node with 3 18Gb Drives in a
RAID 5 array. The C:\ drive is 4Gb. Running Win2k
Advanced server with SP1 and a couple of
hotfixes. They are currently unable to add any more
printers to the server and the only significant event that
has occurred since this started was the installation of
Print Services for Unix. This was done a couple of days
ago. They currently only have 25 printers assigned to
this cluster but will have many more in the future.
When trying to install a new printer the wizard allows
them to create a port and when they select the driver it
says complete however they get an error msg that says
"Printer driver could not be installed" "Print
monitor is unknown".
Nothing relevant found searching for these two strings in
MS Premier KnowledgeBase.
[ANALYSIS] Other that the Print Services for Unix being
installed there doesn't appear to be much relevant data
regarding this problem. The problem didn't happen before
a couple of days ago, and the only significant event that
occurred since then is the addition of these services. I
asked if they had
reinstalled SP1 after installing the Print Services for
Unix and the customer had stated that they had not. I
explained the general philosophy of Service Packs with
relation to native services that come with the OS.
Service Packs generally need to be reinstalled when adding
any of these services.
We tried ....
1) Install the printer locally on each node using the Add
Printer Wizard.
2) On each node specify the correct LPR or TCP port (may
need to create the port)
3) Do not share the printer from any of the nodes
4) Then go to \\ and click on Printers
5) Add the printer via the "Add Printer Wizard"
6) At this point you can share the printer with a unique
name.
BUT>>>>> we dont get this far. Fails when goes to load
driver
"Cannot Install Driver, Print Monitor Unknown"
OK, PJ solution was to use Microsoft driver, but there is
no driver from MS.
HP driver for 4100 and Windows 2000
Downloaded the drivers, LaserJet 4050.
Installed locally, not shared.
It created a new key called "HP LaserJet 5 Language
Monitor"
The key has an entry on the right showing Driver:REG_SZ:
HPDCMON.DLL
Tried:
How to Add Digital Print Monitor to Windows 2000 [Q232822]
Print Spooler Support on Microsoft Windows 2000 Server
Cluster Q228904
Tried installing locally - shared and not shared - fails
CUSTOMER APPLIED SP2, no change.
I know we tried this....
1) Install the printer locally on each node using the Add
Printer Wizard.
2) On each node specify the correct LPR or TCP port (may
need to create the port
3) Do not share the printer from any of the nodes
4) Then go to \\ and click on Printers
INSTEAD of using the virtual name, try the machines
NetBIOS name. If we
cannot even install locally with server NetBIOS, then we
do not have a
cluster issue, we have a HP driver issue. If this is
successful then the
drivers will be on the box and we should not have any
trouble virtualizing
the print spooler.
[UPDATE]
I escalated this up to M$ today. The following items have
come out:
*This is only happening on clustered servers.
*All other servers have no problems installing the
drivers, etc.
The customer is currently in the process of renaming
a .dll and attempting
to reinstall the driver. THe customer just came back and
said that that didn't help.
We have now been transfered to a cluster engineer.
He believes that he has seen this problem before. He is
researching...
Speaking with Microsoft. They are having the cust cleanly
remove the printer, and then attempt to add the printers
back as if non-clustered on each node and then share
them. This sounds like something that was tried before,
but the customer is going to try again.
Virtual name, add printer wizard: define via virtual name,
drivers are propogated.
Cluster workaround: preinstall drivers so they're already
there. Then add printer with
port and driver already in place.
Confirmed that this procedure worked for this printer.
He has to add a few others, and is assuming additional
printers will work using the same approach.
Thanks for taking a look...
Ed