Task Scheduler Won't Run Tasks: Objsct Already Exists
Dave Kruger
When I create a task in Windows XP Pro, I get the following error message:
The new task has been created, but it may not run because the account
information has not been set.
The specific error is:
0x8009000f: Object already exists.
Needless to say, the task doesn't run. The detailed view of the Tasks
folder says "Could not run" in the Status column.
I've looked in Microsoft's Knowledge Base, to no avail. There was some
mention about tasks not running when the account has no password. However,
the account that I am running the task under _does_ have a password.
Any ideas?
All help will be really appreciated.
Cheers,
Dave Kruger
dak1...@bigpond.com
Joe Hagen
These errors are usually due to a problem with
the Protected Storage Service.
Is this service running on your system? If not,
try to start it and see if that helps.
A quick way to start it is to open a command prompt
(CMD..EXE) and type:
net start "protected storage"
Joe
"Dave Kruger" <dak1...@bigpond.com> wrote in message
news:SRcx8.47564$uR5.1...@newsfeeds.bigpond.com...
Fei Lo
critical update from microsoft I rebooted to find my registry was
corupt. After restoreing my registry useing the recovery console my
machine came back up with the Task Scheduler produceing this error and
I can no longer connect via remote desktop.
There is a KB article releated to win2000 and this error message,
Q246183
but it is useless for XP. That article also mentions possible problems
with a corupt crypto system, can anyone translate the reg key to XP. I
found one similar in XP but it did something very bad when I deleted
it.
"Joe Hagen" <jdh...@chorus.net> wrote in message news:<Z8gx8.3099$fH5.4...@kent.svc.tds.net>...
Gerhard Bader
> I recently started haveing this problem as well. After installing a
> critical update from microsoft I rebooted to find my registry was
> corupt. After restoreing my registry useing the recovery console my
> machine came back up with the Task Scheduler produceing this error and
> I can no longer connect via remote desktop.
>
> There is a KB article releated to win2000 and this error message,
> Q246183
>
> but it is useless for XP. That article also mentions possible problems
> with a corupt crypto system, can anyone translate the reg key to XP. I
> found one similar in XP but it did something very bad when I deleted
> it.
Yes I have translated it into XP. It cost me hours and hours but I've
just solved it.
Run regedit as Administrator. Key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography
Compare the value for the string "MachineGuid" with other ones
appearing on other places in the registry, it might differ from the
others (do a search for "MachineGuid").
If it is different, make a backup of the Cryptography key for safety.
I took the value from
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
Windows NT\CurrentVersion\SystemRestore\Cfg
and pasted it into the Cryptography MachineGuid.
Save it and reboot
Everything's working fine again!
Gerhard, Munich
PS: probably there are different causes for this fault to occur...
mine appeared after a system restore on my XP home.