Vista - 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.

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:

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:

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?

I doubt it is that (unless these are two separate issues). My password is
only 8 characters, so that indicates that it is not a length issue.

"mattie" wrote:

It is the same issue (as far as I know) so we can rule out that the number of
characters have anything to do with it. Thanks for the quick response. I am
windering if we should open a call with Microsoft? Has anyone else tried
paying for a call?

"jgrenz" wrote:

"Run only when logged on" worked for me. Fortunately it didn't matter to what I was doing in my job.

I'm sure MS would not consider this behavior a bug, but a security feature.