ID 7023 - Corruption was detected in the Task Scheduler

Discuss Windows Event Log events. What they mean, what they tell you about your machine's security ... and whatever questions else you have.

Moderator: alorbach

ID 7023 - Corruption was detected in the Task Scheduler

Postby M.vanVuuren on Fri Apr 02, 2004 9:15 am

After you have installed W2KSP4 on a Windows 2000 server the Task Scheduler Service is stopped and can not be started. The following message will appear:
“Error 2147750673: Corruption was detected in the Task Scheduler security database; the database has been reset”

The only solution to this problem what I have found is to uninstall W2KSP4 reboot the server and install W2KSP4 again. Reboot the server after installation, now the Task Scheduler Service starts normally.

Is this the only solution?
M.vanVuuren
 

Postby alorbach on Fri Apr 02, 2004 3:37 pm

It's at least the most easiest solution ;)
Whatever went wrong during the first time (caused by wathever), the SP4 Installation fixed it. Possible some older scheduled task were corrupt.
User avatar
alorbach
Site Admin
 
Posts: 820
Joined: Thu Feb 13, 2003 11:55 am

Re-installation SP4 does not work all the time

Postby P. van Dorp on Wed Apr 14, 2004 7:23 am

Actually, we've succeeded resolving this problem by re-installing SP4 only once. In the other cases to problem remains.

So we definitely need another solution.

Strangely enough, a solution to this problem is not found on the internet.

Does anyone have any suggestions?

Greetz,

P.
P. van Dorp
 

Removing 841873 fixed my problem.

Postby Peter_S on Fri Aug 20, 2004 2:17 pm

I had same problem. I tried installing SP4, twice. After reviewing the Windows Event Log, it was fairly obvious that the problem started immediately after applying a series of security updates from Microsoft. Removing 841873 fixed my problem.

By the date of previous posts, this isn't going to everyone's solution.
Peter_S
 

Removing 841873 fixed my problem

Postby Josh on Thu Jul 14, 2005 7:07 pm

In hopes of not having to keep the server down long enough to remove and reinstall SP4, I tried removing 841873 as well -- one reboot, and it worked great.
Josh
 

Google Ads



Return to Windows Events

Who is online

Users browsing this forum: Yahoo [Bot] and 0 guests

cron