Portal Home > Knowledgebase > Windows Server > Spooler Services Automatically Stopped


Spooler Services Automatically Stopped




That would be a Yes. See below.

1)This error can be caused by a problem with the print driver.The file is located here: The file is located in C:\Window\System32 folder.
Location should be verified as malware can 'assume' just about any process name.

2)A common cause of this error can be when the printer spooler folder (buffer) is filled up with unwanted files. You can fix this problem by following the steps listed below:


  • [1] Go to Start> Run> type in services.msc.
    [2] Right-click on Print Spooler and then select Stop.
    [3] After you have stopped this process, leave the Service window open. 
    [4}Now open My Computer and navigate to the following folder using Windows Explorer:
    Right click on Start> Explore> Windows> System 32>
  • c:\windows\system32\spool\PRINTERS - in Windows Vista, XP, 98/95/ME
    or
  • c:\winnt\system32\spool\PRINTERS - in Windows NT\2000
    [5] Delete all the files in the Printers folder. 
    [6] Go back to Services window> right-click on Print Spooler> set Startup Type to Automatic> Start the Service.


spoolsv.exe starts the Print Spooler Service. This Service should be set to Automatic. It has one Dependency, which should also be set to Automatic: RPC- Remote Procedure Call (not the RPC Locator, just the RPC)

If the Print buffer is full, you may notice the spoolsv.exe running hot (hi CPU) in the Task Manager.

 

 

 

 


 

You need to stop using refresh and find out what the problem is! Next time the printer doesn't connect, don't do refresh- look at the computer cloce, then go to event Viewer:

Start> Run> type in eventvwr

Do this on each the System and the Applications logs:


  • [1]. Click to open the log> 
    [2]. Look for the Error>
    [3] .Right click on the Error> Properties> 
    [4]. Click on Copy button, top right, below the down arrow >
    [5]. Paste here (Ctrl V)
    [6].NOTES
  • You can ignore Warnings and Information Events.
  • If you have a recurring Error with same ID#, same Source and same Description, only one copy is needed.
  • You don't need to include the lines of code in the box below the Description, if any.
  • Please do not copy the entire Event log.


Errors are time coded. Check the computer clock at time of failed connect.

 

 

 


 

Events 1030 and 1058 can be handled together:

Conservative (easiest) approach- try this first:
Start> Run> cmd> run the following command:

netsh winsock reset

You must reboot the server to complete the reset of the TCP/IP stack.

If that doesn't resolve the problem, do this:
1) Change the binding order of the network adapters (ncpa.cpl-advanced-advanced settings), so that the adapter that is listed at the top of the Connections list has File and Printer Sharing bound to it.
2) Make sure File and Printer Sharing for Microsoft Networks checkbox is enabled on the interface.
3) Disable unplugged network adapters if you have more than one adapters in the computers.
4) Run the gpupdate /force command and check the eventlog to see if the errors are gone. You should find an 1704 info about security policy in the GPO applied successfully.
Refresh Group Policy settings with GPUpdate.exe: http://technet.microsoft.com/en-us/library/cc739112(WS.10).aspx
Soource: EventID.net

Event 58

By default, when a printer is created, the Everyone group is granted Print access. If this permission is removed and the printer is published, Print access must be granted for the Domain Controllers group on the printer. Otherwise, Printer Pruner cannot do its job and Active Directory will contain stale PrintQueue objects.

To resolve:
Make sure that the Everyone group or the Domain Controllers group has access to all printers that are published in Active Directory.

Details here: http://support.microsoft.com/default.aspx?scid=kb;en-us;246174

 

 



Was this answer helpful?

Add to Favourites Add to Favourites    Print this Article Print this Article


Powered by WHMCompleteSolution