Task Scheduler DB corrupt after Win2K SP4 Install

  • Thread starter Thread starter Jeff Richman
  • Start date Start date
J

Jeff Richman

Hello -

Apologies if this is already addressed somewhere, but
I've been unable to find another discussion about this
problem.

After installing SP4 on a Win2K Pro workstation, the Task
Scheduler fails to start, and the following error is in
the event log on every boot:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7023
Date: 8/12/2003
Time: 7:09:00 PM
User: N/A
Computer: PROD-AUDIO-EDIT
Description:
The Task Scheduler service terminated with the
following error:
Corruption was detected in the Task Scheduler
security database; the database has been reset.

When I remove SP4, the Task Scheduler starts fine, but
the error returns when I re-apply SP4. I've tried
removing all scheduled tasks, and installing SP4 both
while the Task Scheduler is running and while it's
stopped.

Any suggestions or ideas? Thanks a lot.

- Jeff Richman
 
I am have the same problem. If you get an answer Please
forward it to me.
Thanks,
Alan
 
We have this same issue on one server immediately after installing Win2K
SP4. If anyone has found a fix for this please reply to this post. The
only reference I can find on Microsoft's support site talks about how SP4
changes how security information is stored for the scheduled tasks, so if
you revert back to SP3 then the tasks stop working. Based on this,
something in the SP4 conversion corrupted the database and it isn't able
to fix itself.
 
Back
Top