Windows Server

Guest

Ok, I folled all the documentation... I have an active/standby cluster
with two identical servers, attached to a Fiber array. Everything
works perfect as far as the "cluster" is concerned. Both nodes work,
all services fail over. I used the Print Migrator 3.1 to restore
backups from our old print servers (we had two nearly identical
servers). The first node works fine (the one I ran the utility on, but
restored to the cluster itself, not the server itself). Problem is,
when I fail over to the other node, everything "looks" to fail over
fine, but NO printers show up on the cluster when the second node is
hosting the services.

I've tried all of the following tips:

278455 How to set up a clustered print server
http://support.microsoft.com/?id=278455

302539 How to Troubleshoot Printing Issues on a Windows Server 2003
Cluster
http://support.microsoft.com/?id=302539

257897 MSCS Printer Shares May Not Come Online If Quorum Log Is Too
Small
http://support.microsoft.com/?id=257897

All the drivers are located on the Printer Spool drive, and the quorum
size is currently 16,384, even though the files are less than 3mb.

Any suggestiosn?

Guest

Also, I have stopped the cluster service on the second node, evicted
it, and readded it to the cluster, and still the same results. All
resources fail over and come online, no problem, but the printers are
not listed in the printers folder and on the workstation I receive the
message:

"Printer not found on server, unable to connect" when I fail over to
the second node.

seth · Guest

so when the second node is active and you browse through the virtual server,
you don't see any printers?
are the drivers installed on the second node?

<kazsmir@gmail.com> wrote in message
news:1129041662.925155.78570@g49g2000cwa.googlegroups.com...

Ryan Sokolowski [MVP] · Guest

It sounds like your cluster didn't like the restore process for creating the
printer resources. Have you tried deleting and manually re-creating one
printer and verifying if that works...bet it will...

--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP

"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."

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

"seth" <seth@work.org> wrote in message
news:uDDOeinzFHA.268@TK2MSFTNGP09.phx.gbl...

Guest

Well I tried two things. According to the Print Migrator 3.1
documentation, the one thing that is distinct with Windows 2003 is
you're not supposed to have to install the information to the various
nodes. In WinNT4 and Win2k clusters, you did have to migrate the
information to every node of the cluster. With Win2k3, the
documentation stated you simply had to install the information directly
to the cluster, rather than the node, and it would copy the drivers to
the shared space, which it has. I've checked the Shared Spool drive
and it has a "drivers" folder with all the drivers required. But, I
did follow older instructions and ran the migrator again on the second
node but to the same location (I have print01 and print02, cluster
named printers, and I ran the migrator from print01 and used the
migrator to restore to \\printers\, then logged onto print02 later and
restored again to \\printers with print02 active). But alas, it had no
effect. I still see no printers on the virtual server when the second
node is active.

Guest

Also, is the MS DTC required for the cluster? When I followed the
cluster setup instructions for the cluster, and for the print cluster
specifically as well, it never mentioned the MS DTC... it wasn't
mentioned in the SQL Documentation I used to implement a SQL cluster
either, but it is specifically mentioned and installed with Exchange
Clusters. Thoughts?

Rodney R. Fournier [MVP] · Guest

MSDTC is not require in a file/print cluster. SQL may need it, depending on
the application, Exchange has to have it to install or apply patches.

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training

<kazsmir@gmail.com> wrote in message
news:1129052789.089494.41270@z14g2000cwz.googlegroups.com...

Guest

Well we're trying to migrate the two print servers we have to the
cluster and then using a DNS Alias redirect to keep things up and
running as smoothly as possible... I'm worried if I add them one by
one it won't be "exact" and there might be a glitch or two with the
printers.

I did have them failing over previously with manually added printer
queues, but I've got around a hundred or so print queues, and I'd
rather not have to do them manually if I can. But then again, if I
spend enough time troubleshooting this, I could have just spent the
time adding them manually.

Guest

I just tried removing a printer and adding it back to the cluster, and
that did not work. It still will not show up when the cluster is
failed over to the second node. This did work previously. Also, I
tried to manually add it on the second node and when I bring up the Add
Printer Wizard, I can only select "Use the following port:" and there
is nothing available in the drop down window. Any suggestions?

Alan Morris · Guest

Can you add a printer on the local node that is not able to host the current
virtual server configuration?.

There should be print event log entries for failing drivers and ports. If
you are using a port monitor that MS does not install by default (LPR Port
or another vendor), you must add this to each node.

Is this Server 2003 RTM of SP1?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

<kazsmir@gmail.com> wrote in message
news:1129051409.323538.274020@g47g2000cwa.googlegroups.com...
[quote]Well I tried two things. According to the Print Migrator 3.1
documentation, the one thing that is distinct with Windows 2003 is
you're not supposed to have to install the information to the various
nodes. In WinNT4 and Win2k clusters, you did have to migrate the
information to every node of the cluster. With Win2k3, the
documentation stated you simply had to install the information directly
to the cluster, rather than the node, and it would copy the drivers to
the shared space, which it has. I've checked the Shared Spool drive
and it has a "drivers" folder with all the drivers required. But, I
did follow older instructions and ran the migrator again on the second
node but to the same location (I have print01 and print02, cluster
named printers, and I ran the migrator from print01 and used the
migrator to restore to \\printers\, then logged onto print02 later and
restored again to \\printers with print02 active). But alas, it had no
effect. I still see no printers on the virtual server when the second
node is active.
[/quote]

Alan Morris · Guest

Can you add a printer on the local node that is not able to host the current
virtual server configuration?.

There should be print event log entries for failing drivers and ports. If
you are using a port monitor that MS does not install by default (LPR Port
or another vendor), you must add this to each node.

Is this Server 2003 RTM of SP1?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

<kazsmir@gmail.com> wrote in message
news:1129051409.323538.274020@g47g2000cwa.googlegroups.com...
[quote]Well I tried two things. According to the Print Migrator 3.1
documentation, the one thing that is distinct with Windows 2003 is
you're not supposed to have to install the information to the various
nodes. In WinNT4 and Win2k clusters, you did have to migrate the
information to every node of the cluster. With Win2k3, the
documentation stated you simply had to install the information directly
to the cluster, rather than the node, and it would copy the drivers to
the shared space, which it has. I've checked the Shared Spool drive
and it has a "drivers" folder with all the drivers required. But, I
did follow older instructions and ran the migrator again on the second
node but to the same location (I have print01 and print02, cluster
named printers, and I ran the migrator from print01 and used the
migrator to restore to \\printers\, then logged onto print02 later and
restored again to \\printers with print02 active). But alas, it had no
effect. I still see no printers on the virtual server when the second
node is active.
[/quote]

Chuck Timon [MSFT] · Guest

http://www.microsoft.com/windowsserver2003/techinfo/overview/availableprinter.mspx

--
Chuck Timon, Jr.
Microsoft Corporation
CCS Beta Engineer
This posting is provided "AS IS" with no
warranties, and confers no rights.
<kazsmir@gmail.com> wrote in message
news:1129051409.323538.274020@g47g2000cwa.googlegroups.com...

	Windows Server Forum Index -> Clustering	All times are GMT
Page 1 of 1