Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3469
  • Last Modified:

Windows 2000 Task Scheduler Not running after I logoff

Hi!

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

Knea
0
knea
Asked:
knea
1 Solution
 
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.

Knea
0
 
cyborgstechCommented:
Knea,

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.

Cheers
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
ancoCommented:
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..
0
 
ancoCommented:
0
 
RindbaekCommented:
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.

Henning
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now