Getting "Service Control Manager" entries in System event log

I am getting quite a few Service Control Manager entries in the System event
log. Also, my print spooler is stopping on occassion and one of these
entries are also listed. Event ids 7031, 7035, and 7036

7031
The Print Spooler service terminated unexpectedly. It has done this 1
time(s). The following corrective action will be taken in 60000
milliseconds: Restart the service.

7036

The Print Spooler service entered the running state.

7036

The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
state.

12503

The WinHTTP Web Proxy Auto-Discovery Service has been idle for 15 minutes,
it will be shut down.

12517

The WinHTTP Web Proxy Auto-Discovery Service suspended operation.

These may or may not be related but any ideas?

Rick

That web proxy auto discovery turns itself on and off as needed - those are
blue informational messages rather than errors, right?

As for the Print Spooler service, that should just run all the time, so
you've got something going on there. The first thing I'd do is to look at
the spool folder, which by default is C:\WINDOWS\System32\spool\PRINTERS.
That directory should be completely empty unless there are jobs in the print
queue. If there are any files in there while no jobs are queued, delete
them. If the system won't let you delete the files, shut down the Print
Spooler service, delete the files, and restart the service.

The next thing to do would be to look in Printers and Faxes to see if there
are any printers stuck in there from remote sessions - for example, you log
into the server over RDP from your desktop PC with printer redirection
enabled. Your desktop printer installs on the server for the duration of
the remote session. It's supposed to get deleted when you log out, but if
it doesn't, it can cause the spooler to crash. So if you have any printers
that show as being from a remote machine, delete those.

After that, I'd probably look at drivers. If you've added any printers
recently, those would be the ones to start with. It doesn't seem like a
driver would suddenly start causing problems, so IMO it's probably not a
driver, but that's something else to check if you don't get results from the
first two things.

"Rick B" <someone@gmail.com> wrote in message
news:%233H66PxFIHA.3848@TK2MSFTNGP05.phx.gbl...
>I am getting quite a few Service Control Manager entries in the System
>event log. Also, my print spooler is stopping on occassion and one of
>these entries are also listed. Event ids 7031, 7035, and 7036
>
> 7031
> The Print Spooler service terminated unexpectedly. It has done this 1
> time(s). The following corrective action will be taken in 60000
> milliseconds: Restart the service.
>
> 7036
>
> The Print Spooler service entered the running state.
>
> 7036
>
> The WinHTTP Web Proxy Auto-Discovery Service service entered the stopped
> state.
>
> 12503
>
> The WinHTTP Web Proxy Auto-Discovery Service has been idle for 15 minutes,
> it will be shut down.
>
> 12517
>
> The WinHTTP Web Proxy Auto-Discovery Service suspended operation.
>
> These may or may not be related but any ideas?
>
> Rick
>
>
>
>

Hi Dave,

Thank you on the Web Proxy auto discovery. They are informational messages,
yes.

-Nothing in my spooler folder.
-I'm not seeing any unnecessary printers in printers and faxes.

I am getting errors in the System event log regarding TermServDevices and
driver ... "unknown" though I'm not sure if that has anything to do with
the spoolsvc.exe terminating. The time of the service going down doesn't
correspond with the time of the termserv error.

I haven't installed a new driver lately.

I'll keep digging. Thank you.

This KB is the only other thing I found. As for those TermServDevices
errors, that means the server doesn't have a driver it can use to print to
the remote printer. Unless you need to print to the remote PC's locally
connected printer while logged into the SBS over RDP, you can just turn off
redirection before connecting to the SBS (in the initial RDP screen, click
Options and un-check Printers on the Local Resources tab), or ignore the
errors.

The Print Spooler service stops responding and Event ID 7031 is logged into
Windows 2000 or in Windows Server 2003
http://support.microsoft.com/default...b;en-us;890642


"Rick B" <someone@gmail.com> wrote in message
news:uj9xqi0FIHA.4880@TK2MSFTNGP03.phx.gbl...
> Hi Dave,
>
> Thank you on the Web Proxy auto discovery. They are informational
> messages, yes.
>
> -Nothing in my spooler folder.
> -I'm not seeing any unnecessary printers in printers and faxes.
>
> I am getting errors in the System event log regarding TermServDevices and
> driver ... "unknown" though I'm not sure if that has anything to do with
> the spoolsvc.exe terminating. The time of the service going down doesn't
> correspond with the time of the termserv error.
>
> I haven't installed a new driver lately.
>
> I'll keep digging. Thank you.
>