Sign in with
Sign up | Sign in
Your question

Service Control Manager

Last response: in Windows XP
Share
September 3, 2004 6:45:03 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Everytime a user logs on to an XP computer, they are unable to print and the
printers disappear. I found many posts that addressed the issue of cleaning
up the printer drivers and making sure that the correct drivers are used.
But, this is still an issue. I have also done a sfc /scannow, which also did
not address the issue.

When logged on as an administrator, this is easily dealt with by adding a
batch file to the startup, which will start the spooler service when the user
logs on. But, for normal users this isn't a viable solution.

The Event Viewer message (shown below) indicates that the service control
manager (SCM) stops the spooler at start up, which, according to the event
id, is correct. On some computers I found that the service is then started
immediately after it was stopped, with the same event id.

My question is: How can I stop the SCM from stopping the spooler in the
first place or, if it is necessary for the spooler to be stopped at startup,
how can I get the SCM to start the spooler again on behalf of a normal user?

Any help will be much appreciated.

I added some more details below.

Assumptions:
XP Professional SP1 or 2
Logged on as any user (local or domain)
Any permissions - from users to domain admins

When logging on to the computer, the following event occurs:

Event Type: Information
Event Source: Service Control Manager
Event Category: None
Event ID: 7035
Date: 03/09/2004
Time: 08:36:04
User: NT AUTHORITY\SYSTEM
Computer: DELL
Description:
The Print Spooler service was successfully sent a stop control.

The Help and Support Centre responds to this with:

"A control code was correctly sent to the service. This message is logged
for informational purposes only."
September 6, 2004 8:11:02 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

Just an update:

When I tried to look at the dependencies of the service I got the following
error message:

Win32: The RPC server is unavailable.

Andre

"Andre" wrote:

> Everytime a user logs on to an XP computer, they are unable to print and the
> printers disappear. I found many posts that addressed the issue of cleaning
> up the printer drivers and making sure that the correct drivers are used.
> But, this is still an issue. I have also done a sfc /scannow, which also did
> not address the issue.
>
> When logged on as an administrator, this is easily dealt with by adding a
> batch file to the startup, which will start the spooler service when the user
> logs on. But, for normal users this isn't a viable solution.
>
> The Event Viewer message (shown below) indicates that the service control
> manager (SCM) stops the spooler at start up, which, according to the event
> id, is correct. On some computers I found that the service is then started
> immediately after it was stopped, with the same event id.
>
> My question is: How can I stop the SCM from stopping the spooler in the
> first place or, if it is necessary for the spooler to be stopped at startup,
> how can I get the SCM to start the spooler again on behalf of a normal user?
>
> Any help will be much appreciated.
>
> I added some more details below.
>
> Assumptions:
> XP Professional SP1 or 2
> Logged on as any user (local or domain)
> Any permissions - from users to domain admins
>
> When logging on to the computer, the following event occurs:
>
> Event Type: Information
> Event Source: Service Control Manager
> Event Category: None
> Event ID: 7035
> Date: 03/09/2004
> Time: 08:36:04
> User: NT AUTHORITY\SYSTEM
> Computer: DELL
> Description:
> The Print Spooler service was successfully sent a stop control.
>
> The Help and Support Centre responds to this with:
>
> "A control code was correctly sent to the service. This message is logged
> for informational purposes only."
>
>
>
>
>
September 29, 2004 4:29:04 AM

Archived from groups: microsoft.public.windowsxp.print_fax (More info?)

I found the problem! It turns out that the spooler is stopped by the client
side of the remote control software, which we use.

We make use of third party remote control software, which consist of a
client installation and a control installation. In order for the controller
to make use of the client's printer, it makes use of printer mapping, which
is controlled by a .dll in the client installation.

The solution was as simple as renaming the relevant .dll (injlib.dll in this
case), which will stop the spooler from shutting down in the first place.

If you make use of any remote control software and are experiencing
difficulties, ty uninstalling the software first before trying to fix your
printer.

Andre

"Andre" wrote:

> Just an update:
>
> When I tried to look at the dependencies of the service I got the following
> error message:
>
> Win32: The RPC server is unavailable.
>
> Andre
>
> "Andre" wrote:
>
> > Everytime a user logs on to an XP computer, they are unable to print and the
> > printers disappear. I found many posts that addressed the issue of cleaning
> > up the printer drivers and making sure that the correct drivers are used.
> > But, this is still an issue. I have also done a sfc /scannow, which also did
> > not address the issue.
> >
> > When logged on as an administrator, this is easily dealt with by adding a
> > batch file to the startup, which will start the spooler service when the user
> > logs on. But, for normal users this isn't a viable solution.
> >
> > The Event Viewer message (shown below) indicates that the service control
> > manager (SCM) stops the spooler at start up, which, according to the event
> > id, is correct. On some computers I found that the service is then started
> > immediately after it was stopped, with the same event id.
> >
> > My question is: How can I stop the SCM from stopping the spooler in the
> > first place or, if it is necessary for the spooler to be stopped at startup,
> > how can I get the SCM to start the spooler again on behalf of a normal user?
> >
> > Any help will be much appreciated.
> >
> > I added some more details below.
> >
> > Assumptions:
> > XP Professional SP1 or 2
> > Logged on as any user (local or domain)
> > Any permissions - from users to domain admins
> >
> > When logging on to the computer, the following event occurs:
> >
> > Event Type: Information
> > Event Source: Service Control Manager
> > Event Category: None
> > Event ID: 7035
> > Date: 03/09/2004
> > Time: 08:36:04
> > User: NT AUTHORITY\SYSTEM
> > Computer: DELL
> > Description:
> > The Print Spooler service was successfully sent a stop control.
> >
> > The Help and Support Centre responds to this with:
> >
> > "A control code was correctly sent to the service. This message is logged
> > for informational purposes only."
> >
> >
> >
> >
> >
!