Yashy
asked on
Print spooler stops constantly on print server.....
hey peeps,
I've got a Windows 2008 R2 server on a tin machine and one of its services is acting as a print server. It was fine until two days ago.
The print spooler keeps stopping. I restart it. Then it stops again.
I've installed updates/patches, and rebooted. I even removed the entire print services and added it again to no avail. I'm wondering whether this could be to do with a driver it doesn't like?
This is one of the only errors I receive:
Faulting application name: spoolsv.exe, version: 6.1.7600.16661, time stamp: 0x4c6f61fe
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec4b137
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ae2
Faulting process id: 0x590
Faulting application start time: 0x01cd1eee746d17ee
Faulting application path: C:\Windows\System32\spools v.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll. dll
Report Id: b2d6e26f-8ae1-11e1-9355-00 2655cfcb5f
Any clues as to what it might be or what one should do from here?
Thanks a lot
Yashy
I've got a Windows 2008 R2 server on a tin machine and one of its services is acting as a print server. It was fine until two days ago.
The print spooler keeps stopping. I restart it. Then it stops again.
I've installed updates/patches, and rebooted. I even removed the entire print services and added it again to no avail. I'm wondering whether this could be to do with a driver it doesn't like?
This is one of the only errors I receive:
Faulting application name: spoolsv.exe, version: 6.1.7600.16661, time stamp: 0x4c6f61fe
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec4b137
Exception code: 0xc0000374
Fault offset: 0x00000000000c6ae2
Faulting process id: 0x590
Faulting application start time: 0x01cd1eee746d17ee
Faulting application path: C:\Windows\System32\spools
Faulting module path: C:\Windows\SYSTEM32\ntdll.
Report Id: b2d6e26f-8ae1-11e1-9355-00
Any clues as to what it might be or what one should do from here?
Thanks a lot
Yashy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
have you tried changing the recovering for the printer spooler?
ASKER
gcoltharp - that completely did the trick! You genius.
FYI, the problem was occuring prior to any updates; I carried out the updates afterwards.
Thanks so much
Y
FYI, the problem was occuring prior to any updates; I carried out the updates afterwards.
Thanks so much
Y
You are most welcome. Glad to help.
Would have appreciated the points...but oh well.
The points assigned to me, but you used the gcoltharp's advice. D'oh! :)
ASKER
I did this all by mistake....so sorry. Can we revoke that? I clicked the wrong one by mistake guys!!
ASKER
If the points can't be reappointed, then Gcolthart...I'll repost question and you just copy/paste the answer here and I'll assign points to you this time.
You can try contacting an admin here. I don't know what the process is. You don't need to repost though. If the points can be reassigned, awesome....if not, no worries.
Mistakes happen. :)
Mistakes happen. :)
ASKER
I've sent their team an email and will wait for their feedback. Apologies to both of you here, including you Celazkon for the confusion, but seeing as the advice used was the one from Gcolthartp it's fair I appoint those to him.
sure. No problemo.
gcoltharp's solution below fixed the print spool problem on a WIndows Server 2012 Essentials installation as well.
I 'm adding the comment to help make finding this solution easier here on EE.
by: gcoltharpPosted on 2012-04-20 at 06:44:23ID: 37871154
I had this problem with a bad user mode driver that wasnt compatable with an update to .NET... but before we go there, you can just remove all of the jobs in the spool folder.
Stop the Print Spooler service... navigate to %systemroot%\system32\spoo l\printers
If any files are there, hard delete them (shift + delete).
If that doesnt cure it, look at the first possibility.... sort your updates to look at what updates were applied when you started having trouble.
I 'm adding the comment to help make finding this solution easier here on EE.
by: gcoltharpPosted on 2012-04-20 at 06:44:23ID: 37871154
I had this problem with a bad user mode driver that wasnt compatable with an update to .NET... but before we go there, you can just remove all of the jobs in the spool folder.
Stop the Print Spooler service... navigate to %systemroot%\system32\spoo
If any files are there, hard delete them (shift + delete).
If that doesnt cure it, look at the first possibility.... sort your updates to look at what updates were applied when you started having trouble.
Stop the Print Spooler service... navigate to %systemroot%\system32\spoo
If any files are there, hard delete them (shift + delete).
If that doesnt cure it, look at the first possibility.... sort your updates to look at what updates were applied when you started having trouble.
Hope this helps.