Obvious dumb question: you've supplied the domain credentials in the scheduling GUI for this task?
-sc -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Wednesday, November 04, 2009 8:01 PM To: NT System Admin Issues Subject: Something glaringly obvious, I'm sure... All, I've created a domain account as a service account for a copy job from an application server to our file server, but it's giving me fits trying to schedule it. Both servers are Win2k3 R2, with patches, in our Win2k3 domain. I can log into the console on the file server as the service account and launch the batch file, with no problems. However, the scheduled task will not start - it just says in the status column "Could not start" with a last result code of 0x0, though one time I found a 0x2. I have no idea what that code means, even after much googling, and I only found it once, while adjusting permissions, so it might be a red herring. The scheduled task for this is a multiple schedule item, occurring three times a day, if that makes a difference. I don't find anything interesting in the event logs, either - just a 528/538 combo in the security log at the scheduled time. Any thoughts on where I should start looking? Thanks, Kurt ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
