[sdw2003] Task Scheduler Service - Access Denied 5

[Matt Dolan]

Comes back with this:
Could not start the Task Scheduler service on Local Computer.  Error 1079:
The account specified for this service is different from the account
specified for other services running in the same process. 
 

-----Original Message-----
From: sdw2003-bounces at mattware.com [mailto:sdw2003-bounces at mattware.com] On
Behalf Of James Eitzen
Sent: Friday, April 25, 2008 11:26 AM
To: mdolan at mattware.com; San Diego Windows 2003 User Group
Subject: Re: [sdw2003] Task Scheduler Service - Access Denied 5

Try changing it to an account with local admin rights. See if that works.
On Fri, Apr 25, 2008 at 11:23 AM, Matt Dolan <mdolan at mattware.com> wrote:

> It's running under the local system account.
>
> -----Original Message-----
> From: sdw2003-bounces at mattware.com 
> [mailto:sdw2003-bounces at mattware.com]
> On
> Behalf Of James Eitzen
> Sent: Friday, April 25, 2008 11:18 AM
> To: San Diego Windows 2003 User Group
> Subject: Re: [sdw2003] Task Scheduler Service - Access Denied 5
>
> Is the service running with the default config? You haven't changed it 
> to use some other logon account have you?
>
>
> On Fri, Apr 25, 2008 at 11:06 AM, Matt Dolan <MDolan at t-tape.com> wrote:
>
> > I applied some security updates to a Windows 2003 Standard SP2 server.
> > They all worked on my other server no problem. This server rebooted 
> > and will not start the Task Scheduler service. I get the event error
> > 7023 'Could not start the Task Scheduler service on Local Computer.
>  Error
> 5:
> > Access is denied.'
> >
> > I removed the updates, but that did not resolve the problem. Any 
> > ideas how to reset the security setting to make the Task Scheduler 
> > service work again? I'm pulling my hair out trying to find anything 
> > that works in Google.
> >
> > Matt
> >
> >
> > ================
> > Matt Dolan
> >
> > When solving problems, dig at the roots instead of just hacking at 
> > the leaves.
> > --Anthony J. D'Angelo