Terr0r
asked on
Windows 2003 Printspool Crashes Constantly
Hello,
I have a Win2k3 Domain and 2 print servers. Print server 1 serves 19 HP LaserJet Printers running JetDirects, updated with the lateset firmware. Print server 2 serves 7 HP LaserJet Printers also running JetDirects with the latest firmware.
Over the past few weeks, the printspool will crash every couple of days on both printservers. Normally a restart of the print spooler will restart the services. As of yesterday, this is no longer the case on print server 2, as the spooler will not restart due to failing. I can not find in the event log enough information to track this problem to it's source. The error message in the event log is as follows:
Faulting application spoolsv.exe, version 5.2.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0001d61b.
Reporting queued error: faulting application spoolsv.exe, version 5.2.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0001d61b.
Last night I deleted .SHD and .SPL files from %system%\system32\spool\PR
I was using the HP Network Installation Wizard software, most recent version, to install the printers weeks ago. I uninstalled the software from both servers thinking maybe that could be the problem.
I also came across a similiar problem posted here last night while searching the site from home, but could not find the post this morning here at work, hence why I am now asking for help.
Anyone have any ideas as to what could be causing this problem?
I have a Win2k3 Domain and 2 print servers. Print server 1 serves 19 HP LaserJet Printers running JetDirects, updated with the lateset firmware. Print server 2 serves 7 HP LaserJet Printers also running JetDirects with the latest firmware.
Over the past few weeks, the printspool will crash every couple of days on both printservers. Normally a restart of the print spooler will restart the services. As of yesterday, this is no longer the case on print server 2, as the spooler will not restart due to failing. I can not find in the event log enough information to track this problem to it's source. The error message in the event log is as follows:
Faulting application spoolsv.exe, version 5.2.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0001d61b.
Reporting queued error: faulting application spoolsv.exe, version 5.2.3790.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x0001d61b.
Last night I deleted .SHD and .SPL files from %system%\system32\spool\PR
I was using the HP Network Installation Wizard software, most recent version, to install the printers weeks ago. I uninstalled the software from both servers thinking maybe that could be the problem.
I also came across a similiar problem posted here last night while searching the site from home, but could not find the post this morning here at work, hence why I am now asking for help.
Anyone have any ideas as to what could be causing this problem?
ASKER
-exx
I have searched the KB extensively and have found nothing relating to my problem. Most everything I find relating to the ntdll.dll (the faulting module) brings up explorer instances and nothing about printing or the spool failing. I have come across the print troubleshooting guide in the KB, but that was no help.
I have searched the KB extensively and have found nothing relating to my problem. Most everything I find relating to the ntdll.dll (the faulting module) brings up explorer instances and nothing about printing or the spool failing. I have come across the print troubleshooting guide in the KB, but that was no help.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
-exx
I reveiwed the KB article. I don't think the problem is stemming from the problem described in the article. Thank you for trying to help, it is much apprectiated.
I have contacted M$ support and they are working a finding a solution for the problem.
I reveiwed the KB article. I don't think the problem is stemming from the problem described in the article. Thank you for trying to help, it is much apprectiated.
I have contacted M$ support and they are working a finding a solution for the problem.
Let me know what the solution was..
Sorry couldn't be of more help..
-exx
Sorry couldn't be of more help..
-exx
ASKER
Will do. I am curious what the problem is myself.
-exx