The cluster setup isn't new, but the secondary node was just replaced less than 7 months ago. When the new secondary node was put in place, all the resources would failover from one node to the other and vice versa.
The service does start on the primary node when the resources are brought back online on that node. For the DAS (sorry for the mis-type there... been a long several days) we have is a Dell MD3000. The file server is what we use for all our network drives for sharing between users, which is separate from the storage that the print server uses (although on the same DAS unit). The file the print spooler is looking for on both cluster nodes is located in the following location: %systemroot%\system32. Should this be different? Cameron From: [email protected] [mailto:[email protected]] On Behalf Of Miller Bonnie L. Sent: Thursday, February 13, 2014 10:47 AM To: [email protected] Subject: RE: [NTSysADM] Spoolsv issue Is this a brand new setup that has never worked, or was working prior to the last failover? Does the service start again on the primary node? We have a failover cluster WS08 R2 just for printing, connected to Dell Equallogic for the iscsi SAN, so somewhat similar. I'm not sure what you're using for your SAN storage, but the spool folder associated with the cluster is relocated on a shared SAN storage drive, so it moves during the failover-can't tell if that's what you mean by knowing the "File server is online" on the secondary node? -Bonnie From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Cameron Cooper Sent: Thursday, February 13, 2014 3:45 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] Spoolsv issue >From what I've read in the setting up a clustered print server (from MS), >LocalSystem is stated. To compare, I've looked at the Print Spooler service on the primary node and it's set to LocalSystem. 'That's a weird one' I agree. Cameron From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of James Rankin Sent: Thursday, February 13, 2014 5:14 AM To: [email protected]<mailto:[email protected]> Subject: Re: [NTSysADM] Spoolsv issue Does it need some sort of context to run in other than LocalSystem or NetworkService? That's a weird one On 13 February 2014 11:04, Cameron Cooper <[email protected]<mailto:[email protected]>> wrote: Was hoping that someone has experienced this and was able to resolve it.... Here's what's happening: We have two Windows 2008 R2 servers clustered together using Microsoft's Failover Clustering that are connected to a SAN. Within the failover clustering we have setup the following applications: DHCP, File Server and Print Server. In testing the failover from the primary node to the secondary node, the DHCP and File Server will failover without any issues, whereas the Print Server fails. In looking at the event viewer on the secondary node, I see the following event: Event 7000, Service Control Manager The Print Spooler service failed to start due to the following error: The system cannot find the file specified. When I go into Services.msc and try to start the Print Spooler, the following error appears: Windows could not start the Print Spooler service on Local Computer. Error 2: The system cannot find the file specified What I've done so far: - Made sure that the file server was online on the secondary node, since this is where the print server storage resides. - Checked the Print Spooler service to see where the spoolsv.exe file was and then confirmed that it is in that location (%systemroot%\system32\) - Tried to move a copy of the file from the primary node, but the file won't copy over since the system32 folder is protected. - Researched this online to see if there were any other suggestions and all I've been able to find suggested to copy the spoolsv.exe file Thoughts/ideas on how to resolve? Regards, Cameron ________________________________ CONFIDENTIALITY NOTICE: This email message is intended only for the person or entity to which it is addressed and may contain confidential material. Any unauthorized review, use, disclosure, downloading, copying or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and permanently delete all copies of the original message. If you are the intended recipient but do not wish to receive communications through this medium, please advise the sender immediately.
