From: DAP on 20 Sep 2005 12:37 I have received the following error messages in the event log. I have to manunally restart the print server because restarting the print spooler does not fix the issue. Anyone have any insight on this kind of issue. Thanks Event Type: Information Event Source: Application Error Event Category: (100) Event ID: 1004 Date: 9/20/2005 Time: 11:50:44 AM User: N/A Computer: USPAPRTSRV2 Description: Reporting queued error: faulting application spoolsv.exe, version 5.2.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x000327f9. Event Type: Error Event Source: Application Error Event Category: (100) Event ID: 1000 Date: 9/20/2005 Time: 11:47:43 AM User: N/A Computer: USPAPRTSRV2 Description: Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault address 0x000327f9. Event Type: Error Event Source: Service Control Manager Event Category: None Event ID: 7031 Date: 9/20/2005 Time: 11:47:43 AM User: N/A Computer: USPAPRTSRV2 Description: The Print Spooler service terminated unexpectedly. It has done this 2 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.
From: Bryce on 27 Sep 2005 15:19 You are not alone. I receive the event ID 1000 error about once a week but not consistent enough to know if there is a particular cause such as a certain printer or user. Yesterday I actually had to reboot twice before the Spooler service would restart. I tried creating a new Spool folder but that didn't seem to make a difference. We are using Windows 2003 Standard Server and have 4 printers installed, all different brands except for 2. 2 of them are multifunction printer/copier/faxes. Sorry I don't have any advice but if I come across a solution I will let you know. Thanks Bryce DAP wrote: > I have received the following error messages in the event log. I have to > manunally restart the print server because restarting the print spooler does > not fix the issue. Anyone have any insight on this kind of issue. Thanks > > Event Type: Information > Event Source: Application Error > Event Category: (100) > Event ID: 1004 > Date: 9/20/2005 > Time: 11:50:44 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > Reporting queued error: faulting application spoolsv.exe, version > 5.2.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault > address 0x000327f9. > > > Event Type: Error > Event Source: Application Error > Event Category: (100) > Event ID: 1000 > Date: 9/20/2005 > Time: 11:47:43 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module > ntdll.dll, version 5.2.3790.1830, fault address 0x000327f9. > > Event Type: Error > Event Source: Service Control Manager > Event Category: None > Event ID: 7031 > Date: 9/20/2005 > Time: 11:47:43 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > The Print Spooler service terminated unexpectedly. It has done this 2 > time(s). The following corrective action will be taken in 60000 > milliseconds: Restart the service.
From: Bryce on 27 Sep 2005 15:20 You are not alone. I receive the event ID 1000 error about once a week but not consistent enough to know if there is a particular cause such as a certain printer or user. Yesterday I actually had to reboot twice before the Spooler service would restart. I tried creating a new Spool folder but that didn't seem to make a difference. We are using Windows 2003 Standard Server and have 4 printers installed, all different brands except for 2. 2 of them are multifunction printer/copier/faxes. Sorry I don't have any advice but if I come across a solution I will let you know. Thanks Bryce DAP wrote: > I have received the following error messages in the event log. I have to > manunally restart the print server because restarting the print spooler does > not fix the issue. Anyone have any insight on this kind of issue. Thanks > > Event Type: Information > Event Source: Application Error > Event Category: (100) > Event ID: 1004 > Date: 9/20/2005 > Time: 11:50:44 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > Reporting queued error: faulting application spoolsv.exe, version > 5.2.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault > address 0x000327f9. > > > Event Type: Error > Event Source: Application Error > Event Category: (100) > Event ID: 1000 > Date: 9/20/2005 > Time: 11:47:43 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module > ntdll.dll, version 5.2.3790.1830, fault address 0x000327f9. > > Event Type: Error > Event Source: Service Control Manager > Event Category: None > Event ID: 7031 > Date: 9/20/2005 > Time: 11:47:43 AM > User: N/A > Computer: USPAPRTSRV2 > Description: > The Print Spooler service terminated unexpectedly. It has done this 2 > time(s). The following corrective action will be taken in 60000 > milliseconds: Restart the service.
From: DAP on 28 Sep 2005 14:06 Thanks. I actually reinstalled all the drivers for all the printers on the server and so far the issue has not re-surfaced. I have read other posts where people have tried reinstalling the drivers and it did not fix the issue. I have about 30 print queues on the server. There is range of different brands from hp to zebra. Well if I hear anything else I will post. Good luck. "Bryce" wrote: > You are not alone. I receive the event ID 1000 error about once a week > but not consistent enough to know if there is a particular cause such > as a certain printer or user. Yesterday I actually had to reboot twice > before the Spooler service would restart. I tried creating a new Spool > folder but that didn't seem to make a difference. We are using Windows > 2003 Standard Server and have 4 printers installed, all different > brands except for 2. 2 of them are multifunction printer/copier/faxes. > Sorry I don't have any advice but if I come across a solution I will > let you know. Thanks > > Bryce > > DAP wrote: > > I have received the following error messages in the event log. I have to > > manunally restart the print server because restarting the print spooler does > > not fix the issue. Anyone have any insight on this kind of issue. Thanks > > > > Event Type: Information > > Event Source: Application Error > > Event Category: (100) > > Event ID: 1004 > > Date: 9/20/2005 > > Time: 11:50:44 AM > > User: N/A > > Computer: USPAPRTSRV2 > > Description: > > Reporting queued error: faulting application spoolsv.exe, version > > 5.2.3790.1830, faulting module ntdll.dll, version 5.2.3790.1830, fault > > address 0x000327f9. > > > > > > Event Type: Error > > Event Source: Application Error > > Event Category: (100) > > Event ID: 1000 > > Date: 9/20/2005 > > Time: 11:47:43 AM > > User: N/A > > Computer: USPAPRTSRV2 > > Description: > > Faulting application spoolsv.exe, version 5.2.3790.1830, faulting module > > ntdll.dll, version 5.2.3790.1830, fault address 0x000327f9. > > > > Event Type: Error > > Event Source: Service Control Manager > > Event Category: None > > Event ID: 7031 > > Date: 9/20/2005 > > Time: 11:47:43 AM > > User: N/A > > Computer: USPAPRTSRV2 > > Description: > > The Print Spooler service terminated unexpectedly. It has done this 2 > > time(s). The following corrective action will be taken in 60000 > > milliseconds: Restart the service. > >
|
Pages: 1 Prev: W32time synch problems Next: Try to activate, it says already activated |