Windows

General discussion

Locked

Windows 2000 Task Scheduler wont start

By robw ·
I am unable to start the task scheduler on one of my servers.
Win 2000 Server SP4

Error message:
-----
Could not start the task scheduler service on local computer.
Error 2147500037: Unspecified error
------
Event:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event I 7023
Date: 2/14/2004
Time: 10:29:22 AM
User: N/A
Computer: OWIVAN01
Description:
The Task Scheduler service terminated with the following error:
Unspecified error

_
Any suggestions?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by Curacao_Dejavu In reply to

specificly this post patch.
http://tinyurl.com/h5l9

but do install all security postpatches.

Collapse -

by robw In reply to

Tried this one as well thanks

Collapse -

by Joseph Moore In reply to Windows 2000 Task Schedul ...

Here is the Registry dump of the Task Scheduler service, every entry and value. Make sure yours looks like this:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule]
"Description"="Enables a user to configure and schedule automated tasks on this computer. If this service is stopped, these tasks will not be run at their scheduled times. If this service is disabled, any services that explicitly depend on it will fail to start."
"Type"=dword:00000120
"Start"=dword:00000002
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
6b,00,20,00,6e,00,65,00,74,00,73,00,76,00,63,00,73,00,00,00
"DisplayName"="Task Scheduler"
"Group"="SchedulerGroup"
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00
"DependOnGroup"=hex(7):00,00
"ObjectName"="LocalSystem"
"NextAtJobId"=dword:00000002
"AtTaskMaxHours"=dword:00000048

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Parameters]
"ServiceDll"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,\
00,74,00,25,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,\
73,00,63,00,68,00,65,00,64,00,73,00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,\
00
"ServiceMain"="SchedServiceMain"

Collapse -

by Joseph Moore In reply to

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Security]
"Security"=hex:01,00,14,80,90,00,00,00,9c,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,60,00,04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,\
05,0b,00,00,00,00,00,18,00,9d,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,\
23,02,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,\
02,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,\
00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule\Enum]
"0"="Root\\LEGACY_SCHEDULE\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

Collapse -

by Joseph Moore In reply to

As you can tell, I have WinXP, but that shouldn't make a difference for Task Scheduler.

Ok, I would make sure your values for the entries in your Registry settings match.
Also, one thing that is interesting is the ServiceDLL entry under the Parameters key. When you look at it in Regedit, it equals "%SystemRoot%\system32\schedsvc.dll" but in the Regedit export, it is all in hex. That is due to the fact that it is a Reg_Expand_SZ type.

hope this helps

Collapse -

by robw In reply to
Collapse -

by robw In reply to Windows 2000 Task Schedul ...

Other Services were blocking the start of the service. Thanks for everyones help

Collapse -

by pcounsell In reply to Windows 2000 Task Schedul ...

Look at Task Scheduler?s log file, %systemroot%\schedlgu.txt. If you see the message 0x8004130f: No account information could be found in the Task Scheduler security database for the task indicated, you can eliminate the problem by rescheduling the jobs with the correct username and password.

Collapse -

by robw In reply to

Poster rated this answer.

Collapse -

by robw In reply to Windows 2000 Task Schedul ...

This question was closed by the author

Related Discussions

Related Forums