|
Posted by Steven L Umbach on May 2, 2006, 9:22 pm
Please log in for more thread options Protected storage is not well documented [which means I don't know much more
than it exists] but it is used to store some credentials on the computer
that are not stored in the local sam. Information in the link below leads me
to believe that the account credentials probably are stored in it. I can't
give you any special advice on how to prevent it from happening again if
that is indeed what happened as it probably was just one of those things. If
subsequent restarts do not show the same problem I would not worry too much
about it. Roger may have a better explanation though you indicate that is
not a possibility so I can't think of anything else. --- Steve
http://support.microsoft.com/?id=246183
When you attempt to schedule a task using the Scheduled Task tool in Control
Panel, you may receive either of the following error messages:
. The new task has been created, but may not run because the account
information could not be set. The specific error is:
0x80090016: Keyset does not exist.
. The new task has been created, but may not run because the account
information could not be set. The specific error is:
0x8009000f: Object already exists.
CAUSE
This behavior occurs because the Protected Storage service is not started or
running on the Windows 2000-based computer
> Thanks Steven; what is protected storage, and, what could cause this
> problem,
> esp. after a reboot? I am just concerned that it might happen again...
>
> Thanks,
>
> Chris
>
> "Steven L Umbach" wrote:
>
>> My guess is that the username/password for that account became corrupted
>> in
>> protected storage and that changing it fixed the problem. The password
>> for
>> that account obviously was not changed in the local sam since you could
>> still logon to the computer with that logon/password. --- Steve
>>
>>
>>
>> > We have several (20 or so) scheduled tasks which run windows scripts
>> > (.js
>> > and
>> > .wsf) which have been running reliably for years on W2K server, well
>> > protected i.e. viruses very unlikely. They run under various logins,
>> > all
>> > of
>> > which are members of administrators group. This AM, all the ones
>> > running
>> > under "Administrator" username [that's right, THE Administrator],
>> > showed
>> > "Could not start". Sched Task logs showed invalid username or pw (we
>> > did
>> > not
>> > change anything about the Administrator account and in fact continued
>> > to
>> > login in with the Administrator username and pw from terminal
>> > services).
>> > When
>> > we first noticed the problem, we restarted the server but the error
>> > recurred.
>> > But, the other scheduled tasks under other logins continued to run
>> > without
>> > difficulty! If we tried to run the tasks manually (from scheduled
>> > tasks),
>> > they could not start. BUT- when we reset the password on just ONE of
>> > these
>> > tasks (to the same password), it started working- along with all the
>> > other
>> > tasks (i.e. we updated only one task with the SAME password, and they
>> > ALL
>> > started working!)! What could POSSIBLY cause this? There are no errors
>> > in
>> > the
>> > event logs other than the failed login attempts from the scheduled
>> > tasks
>> > [so
>> > the error was definitely bad username or pw].
>> >
>> > I did last PM run a script from csript from the command line, but, did
>> > not
>> > for example make cscript the default host. I do not think this could
>> > possibly
>> > be related, but, it's the only unusual thing done on this server since
>> > last
>> > PM.
>> >
>> > This is of course concerning,
>> >
>> > Thanks for any ideas,
>> >
>> > Chris
>>
>>
>>
| 
XML Sitemap