Windows 2000 Task Scheduler Not running after I logoff


I am trying to run an executable file every morning using Windows 2000 Task Scheduler.  It runs fine when I am logged in to the system. But it never runs ineractively when I logoff from the system.
The task scheduler status shows the following Last result message: 0xe0434f4d

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kneaAuthor Commented:
Well I have already looked at these answers... I think my problem is different... The computer I am trying to run the scheduler on is on a domain...I wonder if you need to be a domain administrator to run a schedule task while you are logged out the computer.


If you need to run a scheduled tasks even you're not logged in to that computer, you need to assign an account to it. You will need to use an admin account if the apps that you'll be running needs it.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Also, you can install 3rd party software, FireDaemon. with this tools, you can install your executable so run as service with system account. And also, this software offers much more options for configurion your executable just the way you want it to work..
RindbaekSenior ConsultantCommented:
You dont need to use an administrator account to run a job under scheduled task. As long as the account has the user right to "logon as a batch job" that can be checked in the "local security settings" -> "local Policies" -> "User right assignments" (its under administrative tools)

But does the message shows unable to start or something like that or does it not have access to the file in question then it could be aquestion of user rights.

So my guess is that your problem will be solved by assigning your account to be the one the task uses for log on and check if you have the user right to log on as a batch job.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.