Print Spooler refuses to turn on and stay on

I have seen a bad file cause this problem. With the spooler stopped, have you gone into the spooler folder and deleted all files and then tried to restart the spooler?

Thanks for your time to help.  Much apprectiated!!  
Yes I have, if it is the same location you are talking...

C:\Windows\System32\spool\printers

Unfortunately, i think it is a driver issue, but since the print spool is not running, I am unable to see the drivers/forms/ports/printers that are currently installed under the Print Management Console.  Therefore, I can not begin to remove printers or drivers either.

Can you try this tool from kyocera don't know if it will list all printer driver due spooler is not runing


http://www.kyoceramita.eu/index/service/dlc.html?initial=false&search=any&searchTerm=deleter%202.8&category=


Is there any additional printer intalled on the server with the normal printer setup program => just check under remove software

another tool that might help from ms


http://support.microsoft.com/gp/printing_problems

Here is an idea to find out what is causing it:
http://printprocessor.wordpress.com/2010/03/21/creating-a-full-user-mode-spooler-dump-with-the-hang-and-crash-switch/
 

Thanks!!  I appreciate your thoughts and ideas!  

I do not have any Kyocera printers on my network.  I don't think it will remove drivers from other companies.  

i also tried the Microsoft Fix-It program.  This program diagnosed the problem as the print spooler was not running and restarted the print spooler.  The program failed to tell me why the spooler was stopped and could not be restarted.

These are the printers/copiers that were functioning...

Ricoh MP5000
Ricoh MPC6000
HP LaserJet 5
Brother HL-2170W
Canon Pixma MP 620 Series
Lexmark Z2400 Series

All the printers were working fine for several months.  We purchase an additional Brother printer and added it to the network within the last week.  However, it was running fine.  The other Brother was on the network for over a year with no issues, and the new one for about 5 days.  I am assuming this one is the issue and have uninstalled all the software related to the Brother printer, but with no change.  All the printers above have software installed on the server in the programs menu.  They have all been working fine for several months.

I thought about unistalling all software associated with the printers, but do not know why it would all of the sudden make it not work, so I have yet to do that.  None of the recent MS updates were directed at updated drivers.  

I was thinking about removing the printer role from the server and then to re-add the role.

Any thoughts would be appreciated!  Thanks!

I ran the print processor program.  Here are the results...


ADPlus Engine Version: 7.01.002 02/27/2009
Command line arguments used were:
-crash -quiet -pn spoolsv.exe -o c:\temp
Output Directory: c:\temp
Output Dumps Directory: c:\temp\20100803_114742_Crash_Mode


==== ADPlus Engine Settings ====

ADPlus built-in key words:
   CUSTOMDUMP = /mdi
   CUSTOMDUMPOVER =
   DLLS = !dlls
   EVENTLOG = !elog_str
   FULLDUMP = /ma
   FULLDUMPOVER =
   HANDLE = !handle 0 0
   HEAP = !heap 0 -k
   LOADEDMODULES = lmv
   LOCKS = !locks
   LOG =
   MATCHINGSYMBOLS = lml
   MINIDUMP = /mdi
   MINIDUMPOVER =
   NOTIFY = !net_send
   STACK = kvn250
   STACKS =
   THREADTIME = .ttime
   THREADUSAGE = !runaway
   TIME = .time
   VOID =

Default Exception Behavior:
    Action1: Log;Time;Stack;MiniDump
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
Default Event Behavior:
    Action1: Log
    Return1: GN

Exceptions:
av-AccessViolation
    Default behavior
ch-InvalidHandle
    Default behavior
ii-IllegalInstruction
    Default behavior
dz-IntegerDivide
    Default behavior
c000008e-FloatingDivide
    Default behavior
iov-IntegerOverflow
    Default behavior
lsq-InvalidLockSequence
    Default behavior
sov-StackOverflow
    Default behavior
aph-Application_hang
    Default behavior
cce-Ctl_C_Console_app
    Default event behavior
dm-Data_misaligned
    Default behavior
gp-Guard_page_violation
    Default behavior
ip-In_page_IO_error
    Default behavior
isc-Invalid_system_call
    Default behavior
sbo-Stack_buffer_overflow
    Default behavior
eh-CPlusPlusEH
    Action1: Log;Time;Stack
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
*-UnknownException
    Action1: Log;Time;Stack
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
clr-NET_CLR
    Action1: VOID
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
bpe-CONTRL_C_OR_Debug_Break
    Action1: Log;Time;Stacks;MiniDump
    Return1: VOID
wkd-Wake_Debugger
    Action1: Log;Time;Stacks;MiniDump
    Return1: GN
ld-DLL_Load
    Default event behavior
ud-DLL_UnLoad
    Default event behavior
epr-Process_Shut_Down
    Action1: Log;Time;EventLog;Stacks;FullDump;ThreadUsage
    Return1: Q

Last script command:
Debugger: cdb.exe


==== Additional Settings ====

Quiet mode = True

==== End of settings output ====

!!!ERROR - Some selected processes are not running:
Missing Processes: SPOOLSV
!!!ERROR - ADPlus failed to run


I also ran it in the -hang mode, results are the same!!

I also ran the program in the -pmn mode.  This mode will monitor the process while it is running.  I ran the script, started the spooler, once the spooler failed, I stopped the script.  Here are the results...

ADPlus Engine Version: 7.01.002 02/27/2009
Command line arguments used were:
-crash -quiet -pmn spool.exe -o c:\temp
Output Directory: c:\temp
Output Dumps Directory: c:\temp\20100803_120144_Crash_Mode


==== ADPlus Engine Settings ====

ADPlus built-in key words:
   CUSTOMDUMP = /mdi
   CUSTOMDUMPOVER =
   DLLS = !dlls
   EVENTLOG = !elog_str
   FULLDUMP = /ma
   FULLDUMPOVER =
   HANDLE = !handle 0 0
   HEAP = !heap 0 -k
   LOADEDMODULES = lmv
   LOCKS = !locks
   LOG =
   MATCHINGSYMBOLS = lml
   MINIDUMP = /mdi
   MINIDUMPOVER =
   NOTIFY = !net_send
   STACK = kvn250
   STACKS =
   THREADTIME = .ttime
   THREADUSAGE = !runaway
   TIME = .time
   VOID =

Default Exception Behavior:
    Action1: Log;Time;Stack;MiniDump
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
Default Event Behavior:
    Action1: Log
    Return1: GN

Exceptions:
av-AccessViolation
    Default behavior
ch-InvalidHandle
    Default behavior
ii-IllegalInstruction
    Default behavior
dz-IntegerDivide
    Default behavior
c000008e-FloatingDivide
    Default behavior
iov-IntegerOverflow
    Default behavior
lsq-InvalidLockSequence
    Default behavior
sov-StackOverflow
    Default behavior
aph-Application_hang
    Default behavior
cce-Ctl_C_Console_app
    Default event behavior
dm-Data_misaligned
    Default behavior
gp-Guard_page_violation
    Default behavior
ip-In_page_IO_error
    Default behavior
isc-Invalid_system_call
    Default behavior
sbo-Stack_buffer_overflow
    Default behavior
eh-CPlusPlusEH
    Action1: Log;Time;Stack
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
*-UnknownException
    Action1: Log;Time;Stack
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
clr-NET_CLR
    Action1: VOID
    Return1: GN
    Action2: Log;Time;Stack;FullDump;EventLog
    Return2: GN
bpe-CONTRL_C_OR_Debug_Break
    Action1: Log;Time;Stacks;MiniDump
    Return1: VOID
wkd-Wake_Debugger
    Action1: Log;Time;Stacks;MiniDump
    Return1: GN
ld-DLL_Load
    Default event behavior
ud-DLL_UnLoad
    Default event behavior
epr-Process_Shut_Down
    Action1: Log;Time;EventLog;Stacks;FullDump;ThreadUsage
    Return1: Q

Last script command:
Debugger: cdb.exe


==== Additional Settings ====

Quiet mode = True

==== End of settings output ====

Starting to monitor the following processes:
   SPOOL.EXE

Have you looked at the service dependencies and verified those needed are also running. This would possibly be things like DCOM and RPC, etc?

yes, those services are running!

Also, you could disable DEP to see if that really allows your print services to keep running. On the command line, issue the following:
Turn it off: bcdedit.exe /set {current} nx AlwaysOff
Turn it on: bcdedit.exe /set {current} nx AlwaysOn
The reboot.

the kyocera tool will remove all printers and drivers and left reg entries etc that's why I posted it :)

stupid questions you did restart the service since then => you just mentioned the service.

Any Antivirus software on the server?

another thought would be that some files got corrupted due to the power failure

you could run sfc  /scannow to check the system files are ok

it should read server since then

I tried running the kyocera tool but it requires the spooler to  be running.
I have restarted a few different times.  None in the last 4-5 hours though since it is still in use.  the AD, file, and DNS services are still up and running so the staff is still using the server, just not printing.  
No antivirus running.

I have not run the scan disk or tried to turn of the DEP yet.  I am assuming it will not work since I tried this...

I tried to turn of the DEP in the System, Advance System Settings, Advance, Performance, Settings, DEP tab, and I try to turn it off.  I receive this error...

This program must run with DEP enabled.  You can not turn DEP off for this program.  

I will try those items later this evening when everyone has cleared out and I can restart the server w/o disturbing anyone.  I will let you know the results in few hours once everyone has left.

Thanks again for all your help!!!

I ran the run sfc  /scannow to check to see if the system files are ok.  Is there a place to view the report??  Following it being run, the cmd box went away.

I disable DEP to see if that really allows your print services to keep running. On the command line, issue the following:

Turn it off: bcdedit.exe /set {current} nx AlwaysOff

The spooler still did not run.

I unistalled all associated printer software through Control Panel, Programs and Features.
Some of the software did not like that the print spooler was running.  I don't think all the software uninstalled quite correctly.  However, it is all out of the programs menu.  I erased the rest from the Programs folder also.

Are there any other location(s) that I may need to erase to get rid of all the printer information, beside hunting through the registry which I don't want to do??

Under C:\Windows\System32\spool, several folders still exist:
drivers (shared) - 4 folders
PRINTERS - this folder is empty
prtprocs - 2 folders (IA64 & w32x86)
SERVERS - empty
tools - 2 folders, 3 application files
SpoolerETW.etl - created today and unable to move to the recycling bin

Are these normal?

Thanks again for all y our help!  I wish this was an easier fix!  It's kill'n me!

Is that HKEY_LOCAL_MACHINE, SYSTEM??

Then, can I safely delete all the folders under PRINTERS??

Thanks!

What about under....

HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers

There are a number of "extra" print folders.  
An example is this...

RICOH Aficio MP 5000 PLC6 on "server" (redirected 1)
RICOH Aficio MP 5000 PLC6 on "server" (redirected 2)
RICOH Aficio MP 5000 PLC6 on "server" (redirected 3)

I'm assuming that is NOT normal!?!    For each of my printers, I have most of them redirected three time.  Interesting.  Somehow that got messed up!!!

Thanks!

ah, got the HKLM - took me a few times to get that short cut!

Removed all the printers under the HKLM-SYSTEM-CURRENTCONTROLSET-CONTROL-PRINT-PRINTERS.  

Restarted.  Still, no luck on getting the spooler to stay started!

Here are two more ideas. First, run msconfig and select any additional programs that you feel you can not load at startup. Reboot and try to start the print spooler. If that doesn't work, try uninstalling the print service role and reinstalling it.

Removed the printer servcie.  This was the result...

Print Services
Delete printers Yes
Print Server
Print Services: Restart Pending

 <Warning>: You must restart this server to finish the removal process.

 <Warning>: Deleting network printers failed with error 1722. The RPC server is unavailable No printers or ports were deleted. Please delete your network printers manually using Printers in Control Panel.

Event ID: 1621 was logged in the Windows Setup Log.

I also attached the log that was created when the Print Service was finished being removed as a role.  


FYI - Prior to the crash in my Application Event Log, I get this information log...

Fault bucket 1343154201, type 1
Event Name: APPCRASH
Response: None
Cab Id: 0

Problem signature:
P1: spoolsv.exe
P2: 6.0.6002.18005
P3: 49e02592
P4: StackHash_e52f
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: 00000000
P9:
P10:

Attached files:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fa18593\WER7A1E.tmp.version.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fa18593\WER7A2F.tmp.appcompat.txt
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fa18593\WER7A3F.tmp.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Report0fa18593\WER8558.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Report0c9ddfe2
ServerManager.log

The HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers\ is still full of printers.  Is it save to delete all these printer folders and directories??

Thanks!

New Error -

System Log
Source:  Service Control Manager
Event ID: 7034
Level: Error

- System
- Provider
   [ Name]  Service Control Manager
   [ Guid]  {555908D1-A6D7-4695-8E1E-26931D2012F4}
   [ EventSourceName]  Service Control Manager

  - EventID 7034
   [ Qualifiers]  49152
   Version 0
   Level 2
   Task 0
   Opcode 0
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2010-08-04T14:24:30.000Z
    EventRecordID 104887
    Correlation
   - Execution
   [ ProcessID]  0
   [ ThreadID]  0
    Channel System
    Computer "Server"
    Security
 
- EventData
  param1 Print Spooler
  param2 3

I am looking at the server log you attached. I will see if I can find anything.

MUCH, MUCH, APPRECIATED!!!  Let me know if you find anything!  

Thanks again!!

As far as  your new error. I did find this:
Event ID 7034 — Service Stop Operations
Updated: December 11, 2007

Applies To: Windows Server 2008

Service Control Manager (SCM) stops services and driver services. It also reports when services terminate unexpectedly or fail to restart after it takes corrective action. Event Details Product: Windows Operating System ID: 7034 Source: Service Control Manager Version: 6.0 Symbolic Name: EVENT_SERVICE_CRASH_NO_ACTION Message: The %1 service terminated unexpectedly. It has done this %2 time(s). Resolve Change the recovery actions

To resolve this issue, change the recovery actions that the Service Control Manager (SCM) will take when a service fails.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To change the recovery actions for a service: Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.
Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.
In the details pane of the Services snap-in, right-click on the name of the service you want to stop and select Properties.
Click the Recovery tab and specify the recovery actions for the service (for example, restart the service or the computer, take no action, or run a program).
Verify
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To verify that a service has stopped: Open the Services snap-in by clicking the Start button, Control Panel, and Administrative Tools, then double-clicking Services.
Note: For Windows Vista, use the Classic View display option in Control Panel to see the Administration Tools.
In the details pane of the Services snap-in, locate the name of the service and verify that the Status column shows a blank status.
 

You know, I read that too.  I have the print spool service set as follows for recovery:

First Failure:  Restart the service
Second Failure:  Restart the service
Subsequent Failures:  Take no action
Reset fail count after:   1 day
Restart service after:  1 minute

I thought about changing the subsequent failures to restart the service, but I'm afraid it will just keep restarting and keep failing and keep taking up CPU resources.

You suggested that I change the msconfig to start only necessary funtions.  
Under the boot tab, if I hide all Microsoft services, none are left.  
Under the Startup Tab, i have 3 items, all Intel items.  I believe these are pretty standard system32 files (igfxtray.exe, hkcmd.exe, igfxpers.exe)  
Under the Services Tab, I'm just not sure what I could disable and what I MUST keep enabled so I have yet to do this and don't feel comfortable doing it either.  So i probably will not.

The service restart was for the last error you posted on the Service Control Manager. As far as the logs, it looks like you made a configuration change around 5:30pm on 8/2. I can tell for one that Power Shell was configured. Did you do anything else? I asked, because about 4 hours later is when you posted this question.

Nevermind my last comment. That is another way of stating GMT.

It had a power failure on 8/1/10 at 5:04:04PM according to a log i found.  I turned the server back on at roughly 7:24AM on 8/2/10.  I was working on solving the problem from 7:30 to until i posted.  I'm guessing that the update sneaked in by accident.  It looks like it was a powershell update that came through MS Windows update.  I must have authorized it!!

I suppose I could remove the powershell all together and see what happens.  I guess it is a worth a try!

Also - The HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers\ is still full of printers.  Is it save to delete all these printer folders and directories??  My guess would be that it is safe since it in a current config folder and all the printers have been erases.  But I don't know the registry that well to take my chances?

Thanks for asking and for all your help!!

Yes, it is safe to delete those folders. I have done it many times. You mention a power failure, but those dates and times seem more in line with the 8/2 to 8/3 time frame. Have you verified the date and time on the server? Be sure to scroll to the bottom an note the last line.
Here is what I see.

3476: 2010-08-02 18:26:30.121 [CrimsonEvents]             Done processing query
3476: 2010-08-02 18:26:31.463 [FeatureType]               Loading event view file: C:\ProgramData\Microsoft\Event Viewer\Views\ServerRoles\PrintServices.Events.xml
3476: 2010-08-02 18:26:31.463 [CrimsonEvents]             Query: <QueryList><Query Id="0"><Select Path="Application">*[System[Provider[@Name='Print']]]</Select><Suppress Path="Application">*[System[(Level=5)]] or */System/TimeCreated[timediff(@SystemTime)>86400000]</Suppress><Select Path="Application">*[System[Provider[@Name='Microsoft-Windows-PrintBRM']]]</Select><Select Path="Application">*[System[Provider[@Name='Microsoft-Windows-PrintSpooler']]]</Select><Select Path="Application">*[System[Provider[@Name='Microsoft-Windows-Spooler-LPDSVC']]]</Select><Select Path="Application">*[System[Provider[@Name='Microsoft-Windows-SpoolerTCPMon']]]</Select><Select Path="Application">*[System[Provider[@Name='Microsoft-Windows-SpoolerSpoolss']]]</Select><Select Path="System">*[System[Provider[@Name='Print']]]</Select><Suppress Path="System">*[System[(Level=5)]] or */System/TimeCreated[timediff(@SystemTime)>86400000]</Suppress><Select Path="System">*[System[Provider[@Name='Microsoft-Windows-PrintBRM']]]</Select><Select Path="System">*[System[Provider[@Name='Microsoft-Windows-PrintSpooler']]]</Select><Select Path="System">*[System[Provider[@Name='Microsoft-Windows-Spooler-LPDSVC']]]</Select><Select Path="System">*[System[Provider[@Name='Microsoft-Windows-SpoolerTCPMon']]]</Select><Select Path="System">*[System[Provider[@Name='Microsoft-Windows-SpoolerSpoolss']]]</Select></Query></QueryList>
3476: 2010-08-02 18:26:32.445 [CrimsonEvents]             Done processing query
1208: 2010-08-03 07:44:10.032 [Extensibility]             Sku extension path: None
1208: 2010-08-03 07:44:10.095 [Extensibility]             No sku extension detected
1208: 2010-08-03 07:44:16.319 [LoadExtensionAssemblies]   No extension assemblies registered.
1208: 2010-08-03 07:44:16.475 [OobOptionalComponentInfo]  Loading OCs from registry.
1208: 2010-08-03 07:44:17.583 [CBS]                       LastModified CBS Time (UTC): 08/03/2010 14:21:07
1208: 2010-08-03 07:44:17.598 [CBS]                       Cache Last Write Time (UTC): 08/03/2010 00:30:23
1208: 2010-08-03 07:44:17.598 [CBS]                       IsCacheStillGood: False.
1208: 2010-08-03 07:44:17.598 [CBS]                       CreateSessionAndPackage: begin
1208: 2010-08-03 07:44:25.180 [CBS]                       CreateSessionAndPackage: done
1208: 2010-08-03 07:44:25.180 [CBS]                       >>>GetUpdateInfo--------------------------------------------------
3768: 2010-08-03 07:44:45.757 [LoadExtensionAssemblies]   No extension assemblies registered.
3768: 2010-08-03 07:44:45.788 [OobOptionalComponentInfo]  Loading OCs from registry.
3768: 2010-08-03 07:44:46.256 [CBS]                       LastModified CBS Time (UTC): 08/03/2010 14:21:07
3768: 2010-08-03 07:44:46.256 [CBS]                       Cache Last Write Time (UTC): 08/03/2010 00:30:23
3768: 2010-08-03 07:44:46.256 [CBS]                       IsCacheStillGood: False.
3768: 2010-08-03 07:44:46.256 [CBS]                       CreateSessionAndPackage: begin
3768: 2010-08-03 07:44:46.287 [CBS]                       CreateSessionAndPackage: done
3768: 2010-08-03 07:44:46.287 [CBS]                       >>>GetUpdateInfo--------------------------------------------------
3768: 2010-08-03 07:44:53.182 [CBS]                       GetUpdateInfo: total: 169 updates

maybe it was 8-2 to 8-3.  The days are starting to blurrrrrr!!

Thanks!  I will delete those folders in the registry.

I am seeing a power shell install error in the System Log -
Windows Servicing identified that package KB2286198 (Security Update) is not applicable for this system.  I found it in the programs and features menu and uninstalled it.  Waiting on a restart.

 

Except this case was logged on 8/2 around 9pm.

No dice!!

What about:   HKEY_CURRENT_USER\Printers
Printers are still listed.  Can I remove them?

I'm starting to wonder if it is not a printer issue, but another underlying cause causing the print spool service to quit.

Found the System Event that I found about the enexpected shut down ~

System Log:
ID 6008
8/2/2010 7:24:11 AM

The previous system shutdown at 5:04:04 PM on 8/1/2010 was unexpected.

Also seeing this error.  Can not remember if I posted this one?!?

Source:  Application Error
Event ID:  1000
Faulting application spoolsv.exe, version 6.0.6002.18005, time stamp 0x49e02592, faulting module ntdll.dll, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000005, fault offset 0x00041e57, process id 0x4b4, application start time 0x01cb3415426fe32b.

Assuming ntdll.dll is causing the error, a file that ntdll.dll is trying to run is causing the error.

What about a registry fixer program?  Might it fix it?  Is there a place I could download and replace the file from the internet?

Thanks!

http://support.microsoft.com/kb/928228 for the log


don't you have a recent bacup of that system befor the crash if so just restore the system state and all registry settings will be fixed

maybe the problem will be solved as well

you know, I WISH I did.

I am not sure about copying it from the Internet. It may be on the server cd and maybe booting to the RC, but I am not were I can research that right now. At this point, with out a BU, and if this server is critical, do you think it would be best to contact MS support? Is that an option?

I thought about the server CD.  unfortunately, I would probably have to do a repair at the boot option (if available on 2008 CD).  Which would probably make me reinstall the SPs and updates.  I have not looked into that one much either, just thought about it.

I don't think MS support is an option.  Depends on cost.  Have not looked into it.

I'm thinking along the lines of a good registry cleaner that might be able to take care of it.  Any recommendations?  

Otherwise I might be looking at calling a service to come in and clean up the problem.

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

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

To resolve this issue, remove printers and printer drivers, and then delete the items that are under certain keys in the registry. Follow these steps:

   1. If possible, remove any printers that are listed in the Printers window.

      To remove a printer, right-click the printer in the Printers window, click Delete, and then click Yes to confirm the deletion.
   2. In the Printers window, on the File menu, click Server Properties.
   3. On the Drivers tab, remove all of the installed printer drivers.

      To remove a printer driver, click the driver, click Remove, and then click Yes to confirm.
   4. Start Registry Editor (Regedit.exe).
   5. Export the following registry keys:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print
   6. Delete any items that are listed under the following keys (do not delete the keys themselves):
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-2
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows NT x86\Drivers\Version-2
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows NT x86\Drivers\Version-3
   7. Delete any non-default items that are listed under the following keys:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors
      The list of Default monitors includes:

          * AppleTalk Printing Devices (When Services for Macintosh is installed)
          * BJ Language Monitor
          * Local Port
          * PJL Language Monitor
          * Standard TCP/IP Port
          * USB Monitor
          * Windows NT Fax Monitor (When a Fax Modem is installed)

      For additional information about which items are not default, click the article number below to view the article in the Microsoft Knowledge Base:
      260142  (http://support.microsoft.com/kb/260142/EN-US/ ) How to Troubleshoot Windows Printing Problems
   8. Delete any items that are listed under the following keys:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Printers
   9. Quit Registry Editor.
  10. Restart your computer, and then reinstall the necessary printers.

I think it works now!!!  At least it did after a restart!!!!!!  YAHOOOOO!!  Print Server is installed and running.  The Spooler stayed running and even allowed me to add printers and view items installed.  

I guess there was a faulty print driver in there somewhere in the registry.  Now to install the printers one by one with a restart to see if I can find the one that caused the problem!!!!  

I'll keep you posted on the progress!!

Thanks for all your help!!!  I APPRECIATE IT!!!!

How many dc's do you have in your domain?

if you have 2 and if there are no other special Software on this server installed I would transfer all files to the other DC unsing robocopy (will copy all settings etc) then demote this DC (all FSMO's will be transfered) then do a clean install of that server

before you start you should do a backup of this server especially system state. If you haven't done this jet I would get a company to take care of it.

I wouldn't use any registry cleaner on a server due this one is a DC, then you might screw your AD

I have 1 DC!!

I am working on doing a complete system state backup to a network computer through Windows Backup Server!   Once this is complete, I can finish the rest.  This is beign done over night, should be started in about 5 min.  I still have a few errors that popped up since the print server started functioning.  I hope those won't be too bad.

We are stating in online backup (complete system state and data) starting within the next week or two.  Why did this have to happen now??  Anyways, have to start the backup!

The KB you mentioned, that basically shows the same registry path I gave you. I thought you had already deleted those entries, or did you skip that part?

1. deleted:  HKLM-SYSTEM-CURRENTCONTROLSET-CONTROL-PRINT-PRINTERS

2. deleted:  HKEY_CURRENT_CONFIG\System\CurrentControlSet\Control\Print\Printers\

3. deleted:  HKEY_CURRENT_USER\Printers

4. deleted:  HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print

5. Delete any items that are listed under the following keys (do not delete the keys themselves):
          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Environments\Windows NT x86\Drivers\Version-3

6. Delete any non-default items that are listed under the following keys:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Monitors
      The list of Default monitors includes:

          * AppleTalk Printing Devices (When Services for Macintosh is installed)
          * BJ Language Monitor
          * Local Port
          * PJL Language Monitor
          * Standard TCP/IP Port
          * USB Monitor
          * Windows NT Fax Monitor (When a Fax Modem is installed)

7. Delete any items that are listed under the following keys:
      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers
      HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Print\Printers

I think I did delete some of them from the registry.  However, I know I never deleted any items from ControlSet001, nor the monitor keys, or under the NTx86 keys.

Anyways, the print server works, but i have a few more application errors to work through now!!  The fun continues!!!  At least i will have a CURRENT whole system backup!!

Thanks again for all your help.  i'll keep you posted until all is good (at least on the print side of things :)

Remove all printers from all the registry locations.  controllset 001, monitors, etc.