Thread: XP scheduled tasks don't run
August 8th, 2004, 12:29 AM #1
XP scheduled tasks don't run
I need some help troubleshooting a problem on WinXP. The scheduled tasks simply don't run.
If I right click on a task and select run, it does, so the task itself is fine. But never ever will it run as a SCHEDULED task.
I found some info on various sites (including MS') while trying to troubleshoot this, such as being sure to enter the right password for the task's account (in this particular case, the same account that is already logged in and has admin rights), checking that the service is started and has right to interact with desktop, etc...
I guess what I need is input from someone who actually had to fight with this.
August 8th, 2004, 01:39 AM #2
I managed to get it running with a good old command line (at).
According to the scheduled tasks log, it couldn't connect to the user's account (???)
Using an old AT command, it's run under the SYSTEM account.
What is wrong with this ? The exact same scheduled task under Win2K doesn't need to be entered via command line to work.
August 8th, 2004, 10:21 AM #3
August 9th, 2004, 04:19 PM #4
I hope you don't think I'm hijacking your thread, but if you do I'll start another one. I have basically the same problem though, I think.
Actually, not basically the same, but similar. One of my scheduled tasks (Symantec netdetect) runs just fine, every five minutes as a matter of fact. The other one, "scan my computer" with NAV 2003 does not work. It's scheduled to run every week, but the last run time was on 6/13/2003, the month I built my computer. I tried to look at the log, but apparently it only has entries for netdetect which is not helpful, since as I already noted netdetect works just fine. I don't even know where to begin with this...
I'm running XP SP1, with only one account. Thus, I don't see how permissions could be a problem...Nerd
August 9th, 2004, 04:30 PM #5
- Join Date
- Oct 2001
is this on a domain, and does the script access a drive mapped via login script?
If it does, use UNC naming, or call a batch file that maps the drive for you as the scheduled task doesn't get the login script when it accesses the network.Helicopters don't fly; they vibrate so much and make so much noise that the earth rejects them.
August 9th, 2004, 04:34 PM #6
Be sure that:
1) the user account info includes the domain if it applies. ie: myDomain\user1 not just user1 or it would have to be a local user account
2) the related user account is not requiring a password change at next logon
3) the user account is not disabled or locked
August 9th, 2004, 09:15 PM #7
Well in my case, all conditions stated by DVNT1 are met.
I'm not on a domain. Instead of the domain name, the system adds computername\ if I only put in my username.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
By Quidam in forum Applications and Operating SystemsReplies: 4Last Post: July 19th, 2004, 11:53 AM
By Jack Hannibal in forum Applications and Operating SystemsReplies: 21Last Post: October 10th, 2003, 05:30 PM
By operative x in forum General Tech DiscussionReplies: 22Last Post: August 11th, 2003, 11:48 PM
By Chooco in forum Applications and Operating SystemsReplies: 39Last Post: March 26th, 2002, 08:57 PM