Re: Scheduled tasks "Could not start"



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



"querylous" <querylous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C1081BBC-3497-46A1-B69E-20A0CC04380E@xxxxxxxxxxxxxxxx
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


.



Relevant Pages

  • Re: Scheduled tasks "Could not start"
    ... Protected storage is not well documented [which means I don't know much more ... to believe that the account credentials probably are stored in it. ... When you attempt to schedule a task using the Scheduled Task tool in Control ... the other scheduled tasks under other logins continued to run ...
    (microsoft.public.windows.server.security)
  • RE: cannot log on to user account following password change
    ... cannot log on to user account following password change ... I changed the username on the account in ... | on the sbs box. ...
    (microsoft.public.windows.server.sbs)
  • Re: logon failure
    ... MSSQLServer service after you change the username of administrator account. ... username for the SQL Server startup service account or the SQL Server Agent ... Microsoft SQL Server service account on the SQL Server host computer. ...
    (microsoft.public.windows.server.sbs)
  • RE: cannot log on to user account following password change
    ... home box with an existing local profile in conjunction with the sbs account. ... a local profile on the xp home box called Fiona Bavester had a username ...
    (microsoft.public.windows.server.sbs)
  • Re: Is it decnet problem or Thruway problem ?
    ... >> enable me to simulate the other user id's less priv. ... > the USERNAME and the PASSWORD. ... > Identifiers, Default Directory, and Login procedures as the user having ... > Owner Username UIC Account Privs Pri Directory ...
    (comp.os.vms)

Quantcast