Miscbrah (5th November 2013)
Thanks, that first article's super. I can't keep the spooler up long enough to change ports over though, and no ports are listed on any of the network printers shared out form this server. Also not 100% sure I'm doing everything I should be as even that article's a bit over my head.
If I bin ALL the printers and re-share them correctly, reinstall drivers, and use standard TCP/IP ports am I likely to encounter the same problem over again?
I'd flush everything non standard and try getting the spooler running then recreate, as long as you back up the reg keys as you kill them you can always put them back.
Last edited by SYNACK; 5th November 2013 at 02:31 PM.
Okay, just so I've got this right I'm going to maybe need a bit more spoon-feeding.
Been into Print Management and binned everything in there including the software printers you get with Office.
Now in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Monitors the default ones are listed in the article as:
AppleTalk Printing Devices
BJ Language Monitor
PJL Language Monitor
Standard TCP/IP Port
Windows NT Fax Monitor
So delete anything from there that isn't on that list, though likely wise to back up that whole monitors section to a .reg entirely beforehand. That sounding right?
Yes, sounds right, those moniters try to talk to the primers constantly, if one is out of wack it can easily kill the spooler.
The sodding spooler's still crashing and all I've got in there now are:
PJL Language Monitor
Standard TCP/IP Port
Which were the only ones I had off the list. Only option I can think of now is just let it fail, quit printing off this server and VM a new print server.
Think I've got any other options? :/
Is the event viewer not telling you why its falling over?
Just wondering if it is HP Printer Drivers that are causing the spooler to crash as I remember a number of other threads on EG where HP Print Drivers were causing issues and they have had to use a different HP Driver to get the HP Printers to work without crashing the spooler on the server
Only reason I say this is I can see in your list of monitors it states PJL Language Monitor which I think is related to HP ??
The Print Spooler service terminated unexpectedly. It has done this 224 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
And from Applog:
Faulting application spoolsv.exe, version 6.0.6002.18294, time stamp 0x4c6a9898, faulting module msvcrt.dll, version 7.0.6002.18551, time stamp 0x4ee8cc5a, exception code 0xc00000fd, fault offset 0x0000b824, process id 0x17a0, application start time 0x01ceda350ce6cacd.
Yay for event log :/
Oh one thing to check, is there anything currently in the spool folder (C:\windows\system32\spool\printers)?
Couple of week ago I had a printer that was spewing nonsense into that spooler and crashed it everytime I tried to start it. Turning bad printer off, clearing spooler folder, restarting spooler fixed it.
Nah I'd tried that - one I'd seen before.
If you look in the services.msc on the server do you have a service called pml driver hpz12?
If you do disable and stop the service, its from your HP printer driver installation and it is not required.
Also with HP printers or most printers in the registry HKLM\System\CurrentControlSet\Control\Print\Printe rs you will see all your printers listed click one of the plus signs alongside to open the contents up and you may see a folder with the name Copy Files, backup your registry first then delete this folder with the name Copy Files and see how you go from there, I had the same trouble a while back and this is what I did from some post I found buried deep on a forum like this one.
Printer Reg before.jpg
Printer Reg after.jpg
Let me know how you get on
Thanks! I found that service, set to off and disabled but still crashing.
Also went in the registry but none of the printers there had a CopyFiles.
Finally after two days...
Solution is, if your printing gets as buggered up as mine did server-side, it's likely that the spooler and/or friends get butchered along with it all. Thing I did was stop the spooler service (REALLY turn it off so it can't start) and then get to work replacing the following folders:
%systemroot%\system32\spool\drivers\x64 (if 64bit install of Windows)
From a working server 2008 (or same as whatever OS you're on) machine. Then set the spooler service to auto start again and poof - all good now and re-adding printers.
Just putting that up for the benefit of any future Googlers or Edugeekers.
There are currently 1 users browsing this thread. (0 members and 1 guests)