Task Scheduler losing saved credentials

Hello,

I have a task that runs an executable every 15 minutes. It is set to run
regardless of if i am logged in or not. It asks for credentials and seems to
be fine. I run the task to check it and it completes. Now the problem. It
will run ok for a few hours both when I am logged in and when I am not.
However, after a few hours (anywhere from 2-15 hours) it seems to begin
complaining about the username and password being invalid. After this I tried
starting the task manually without changing the credentials and I get the
same error. I then open the task properties and click ok immediately after.
Re-enter my credentials and test the task again. It succeeds. Again it will
run for a few hours then complain again about the username and password being
invalid. I have to run the same procedure to resave the credentials again.
What am I doing wrong? I should note that I am running Windows Vista Service
Pack 1 RC1 however, it does this without the SP1 RC1 installed (I have tried
uninstalling SP1 RC1 and resaving the credentials but the same issue
persists). I have since reinstalled SP1 RC1.

I have the exact same issue and haven't found a fix or admission of
guilt on MS's part. All I've found is mention of "Run with highest
privilege" which doesn't help.


--
RonAuger

It seems very flakey since I have 4 other tasks which do not do this at all.
At the moment it has been working for 3 days straight without a problem. I
didn't change anything just kept resetting the credentials. Not sure. It's
just a nusence. I prefer this over the XP task scheduler by far. Even with
this glitch the additions outweigh the glitch.

"RonAuger" wrote:

>
> I have the exact same issue and haven't found a fix or admission of
> guilt on MS's part. All I've found is mention of "Run with highest
> privilege" which doesn't help.
>
>
> --
> RonAuger
>

Just to give more feedback to some results. I have determined on my system
that it can remember the credentials up until I restart the system. Based on
the system Event Logs and the task logs the issue begins when the system
comes back up from a restart, either one I initiated or an automatic one from
an installation or Microsoft Update. It seems that it will not occur until
this restart happens. Not sure if that helps anyone at Microsoft or not but
there you go.

"Quilnux" wrote:

> It seems very flakey since I have 4 other tasks which do not do this at all.
> At the moment it has been working for 3 days straight without a problem. I
> didn't change anything just kept resetting the credentials. Not sure. It's
> just a nusence. I prefer this over the XP task scheduler by far. Even with
> this glitch the additions outweigh the glitch.
>
> "RonAuger" wrote:
>
> >
> > I have the exact same issue and haven't found a fix or admission of
> > guilt on MS's part. All I've found is mention of "Run with highest
> > privilege" which doesn't help.
> >
> >
> > --
> > RonAuger
> >

Quilnux

You might want to inclde the Event errors and Task Logs that pertain to this
problem. This might give someone an indication about what is happening.

If the problem occurs after a restart, when does it start working again???

--

Ronnie Vernon
Microsoft MVP
Windows Shell/User


"Quilnux" <> wrote in message
news:C5005B16-93DA-45B7-8E66-...
> Just to give more feedback to some results. I have determined on my system
> that it can remember the credentials up until I restart the system. Based
> on
> the system Event Logs and the task logs the issue begins when the system
> comes back up from a restart, either one I initiated or an automatic one
> from
> an installation or Microsoft Update. It seems that it will not occur until
> this restart happens. Not sure if that helps anyone at Microsoft or not
> but
> there you go.
>
> "Quilnux" wrote:
>
>> It seems very flakey since I have 4 other tasks which do not do this at
>> all.
>> At the moment it has been working for 3 days straight without a problem.
>> I
>> didn't change anything just kept resetting the credentials. Not sure.
>> It's
>> just a nusence. I prefer this over the XP task scheduler by far. Even
>> with
>> this glitch the additions outweigh the glitch.
>>
>> "RonAuger" wrote:
>>
>> >
>> > I have the exact same issue and haven't found a fix or admission of
>> > guilt on MS's part. All I've found is mention of "Run with highest
>> > privilege" which doesn't help.
>> >
>> >
>> > --
>> > RonAuger
>> >

No problem. I have two logs to provide. The first is the log from the Task
itself.

Error 12/22/2007 03:00:00 101 Task Start Failed Launch
Failure 00000000-0000-0000-0000-000000000000 "Task Scheduler failed to start
""\Quilnet Solutions Schedules\SQL Server Express Replication (PULL)"" task
for user ""philsdesktop\Phillip"". Additional Data: Error Value: 2147943726."


Information 12/22/2007 02:59:59 107 Task triggered on
scheduler Info 36f04699-ddc2-4aaf-a2ab-e2e269977794 "Task Scheduler launched
""{36F04699-DDC2-4AAF-A2AB-E2E269977794}"" instance of task ""\Quilnet
Solutions Schedules\SQL Server Express Replication (PULL)"" due to a time
trigger condition."


-------

The second log is from the TaskScheduler Operational Log from the Event
Viewer.

Error 12/22/2007 03:00:00 Microsoft-Windows-TaskScheduler 101 Task Start
Failed "Task Scheduler failed to start ""\Quilnet Solutions Schedules\SQL
Server Express Replication (PULL)"" task for user ""philsdesktop\Phillip"".
Additional Data: Error Value: 2147943726."

Error 12/22/2007 03:00:00 Microsoft-Windows-TaskScheduler 311 Task Engine
failed to start "Task Scheduler failed to start Task Engine """" process due
to an error occurring in ""LUAIsElevatedToken"" . Command=""taskeng.exe"" .
Additional Data: Error Value: 2147943726."

Error 12/22/2007 03:00:00 Microsoft-Windows-TaskScheduler 104 Logon
failure "Task Scheduler failed to log on
""TaskScheduler:Task:{A0BF04B9-0C48-4FC6-B764-80F8A3D7DE8B}"" . Failure
occurred in ""LogonUser"" . User Action: Ensure the credentials for the task
are correctly specified. Additional Data: Error Value: 1326."

Information 12/22/2007 02:59:59 Microsoft-Windows-TaskScheduler 107 Task
triggered on scheduler "Task Scheduler launched
""{36F04699-DDC2-4AAF-A2AB-E2E269977794}"" instance of task ""\Quilnet
Solutions Schedules\SQL Server Express Replication (PULL)"" due to a time
trigger condition."


------------

There were no relavant log entries for the Application, System, or security
logs for this failure. The only way I have found to get the task working
again is to re-enter the credentials for the task. Once I do that it seems to
be just fine until the system gets a restart. after the restart it fails
again until credentials are re-entered. If you need anything else just let me
know. I hope this helps.

(EDIT: Just so there is clarity when you are reading the logs above, this
system runs as a workgroup not in a business domain).


"Ronnie Vernon MVP" wrote:

> Quilnux
>
> You might want to inclde the Event errors and Task Logs that pertain to this
> problem. This might give someone an indication about what is happening.
>
> If the problem occurs after a restart, when does it start working again???
>
> --
>
> Ronnie Vernon
> Microsoft MVP
> Windows Shell/User
>
>
> "Quilnux" <> wrote in message
> news:C5005B16-93DA-45B7-8E66-...
> > Just to give more feedback to some results. I have determined on my system
> > that it can remember the credentials up until I restart the system. Based
> > on
> > the system Event Logs and the task logs the issue begins when the system
> > comes back up from a restart, either one I initiated or an automatic one
> > from
> > an installation or Microsoft Update. It seems that it will not occur until
> > this restart happens. Not sure if that helps anyone at Microsoft or not
> > but
> > there you go.
> >
> > "Quilnux" wrote:
> >
> >> It seems very flakey since I have 4 other tasks which do not do this at
> >> all.
> >> At the moment it has been working for 3 days straight without a problem.
> >> I
> >> didn't change anything just kept resetting the credentials. Not sure.
> >> It's
> >> just a nusence. I prefer this over the XP task scheduler by far. Even
> >> with
> >> this glitch the additions outweigh the glitch.
> >>
> >> "RonAuger" wrote:
> >>
> >> >
> >> > I have the exact same issue and haven't found a fix or admission of
> >> > guilt on MS's part. All I've found is mention of "Run with highest
> >> > privilege" which doesn't help.
> >> >
> >> >
> >> > --
> >> > RonAuger
> >> >
>

If it helps, I am having the exact same problem (hence it can be reproduced
on a different system). I too am running Vista (Home Premium).

Sounds like a bug...

Would the nature of your task permit you to select the option "Run only when
user is logged on"? If yes, that might provide a workaround...

rgds
Faisal

"jgrenz" wrote:

> If it helps, I am having the exact same problem (hence it can be reproduced
> on a different system). I too am running Vista (Home Premium).
>
> Sounds like a bug...

The task is for an automated download of TV show information overnight (xmltv).

Given that MS hasn't fixed this bug, I will try it your way. Really
annoying to have to change how I run things because the OS doesn't work the
way that it is supposed to.

Thanks for the idea.

Josh

"Faisal" wrote:

>
> Would the nature of your task permit you to select the option "Run only when
> user is logged on"? If yes, that might provide a workaround...
>
> rgds
> Faisal
>
> "jgrenz" wrote:
>
> > If it helps, I am having the exact same problem (hence it can be reproduced
> > on a different system). I too am running Vista (Home Premium).
> >
> > Sounds like a bug...

Same issue happening on our Windows 2003 R2 Servers... Just one thought, the
password I am using is 15 characters long... Do you think it could cut out
characters that are like over 14 long?