Vista Task Scheduler can't run OK *.BAT file

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Pretty straight up situation.

I have a batch file:

"C:\TclStuff\Batch Files\PlaySomething.bat" Annie

This runs on a command line just fine. It won't run from the Task Scheduler:

Task Scheduler failed to start instance
"{DA573AEA-805C-4477-8152-53B595EF95C9}" of "\Wake for Annie" task for user
"a-PC\Ron A. Zajac" . Additional Data: Error Value: 2147942667.

What gives?
 
Ron

In the Task Scheduler for this task, do you have the "Run with highest
privileges" option enabled in the General Tab?
 
Ronnie,

Thanks for the suggestion.

No, this option wasn't enabled. I enabled it, then issued a "Run" order
again to test it. It didn't work. Here's the formatted ("friendly") Details
ouput:

- System

- Provider

[ Name] Microsoft-Windows-TaskScheduler
[ Guid] {de7b24ea-73c8-4a09-985d-5bdadcfa9017}

EventID 203

Version 0

Level 2

Task 203

Opcode 101

Keywords 0x8000000000000000

- TimeCreated

[ SystemTime] 2007-07-16T10:56:30.270Z

EventRecordID 2891

- Correlation

[ ActivityID] {E60BD601-7B36-4973-9586-316BC088C6A9}

- Execution

[ ProcessID] 4916
[ ThreadID] 7592

Channel Microsoft-Windows-TaskScheduler/Operational

Computer a-PC

- Security

[ UserID] S-1-5-21-1865275644-502863341-2745678560-1001


- EventData

TaskName \Wake for Annie
TaskInstanceId {E60BD601-7B36-4973-9586-316BC088C6A9}
ActionName C:\Windows\SYSTEM32\cmd.exe
ResultCode 2147942667


I could mention the fact that the *.BAT has a header that runs another
interpreter (tclsh). However, I feel this is likely a non-issue; if I can
run it from a command line, why shouldn't the Scheduler be able to run it?
On the off-chance it had something to do with the $path$, I quickly modified
that header to invoke the tclsh using the full path (c:\Tcl\bin\tclsh); no
dice.

Again, thanks for your kind ministrations! If another angle occurs to
you, please keep me posted!

-raz (Ron A. Zajac)
 
TaskName \Wake for Annie
TaskInstanceId {E60BD601-7B36-4973-9586-316BC088C6A9}
ActionName C:\Windows\SYSTEM32\cmd.exe
ResultCode 2147942667
Click to expand...
</snip>

Hello,

If it helps at all, that result code translates into this Win32 error code:

Error # 267 (ERROR_DIRECTORY)
The directory name is invalid.

- JB
 
Jimmy,

I guess that tell me something: You're saying that the cmd.exe is
returning that error code? It still raises the question: Why would the
manual run of the script go OK, whereas running it under the auspices of the
Task Scheduler results in some kind of a directory path-related offense
against the cmd.exe? Shouldn't the Task Scheduler--running "as" me--have the
same environment as I do?

Oh: And a sincere thanks for your interest!

-raz
 
Ron said:
Jimmy,

I guess that tell me something: You're saying that the cmd.exe is
returning that error code? It still raises the question: Why would the
manual run of the script go OK, whereas running it under the auspices of the
Task Scheduler results in some kind of a directory path-related offense
against the cmd.exe? Shouldn't the Task Scheduler--running "as" me--have the
same environment as I do?

Oh: And a sincere thanks for your interest!
Click to expand...

I'm not really sure.

Is your account an administrator account, or do you run as a standard
user and elevate to a seperate admin account?

Can you export your task to an xml file and then post the contents of
that file so we can have a look?

- JB
 
</snip>

Hello,

If it helps at all, that result code translates into this Win32errorcode:

Error# 267 (ERROR_DIRECTORY)
The directory name is invalid.

- JB
Click to expand...

I had the same problem. I had to remove the quotation marks in the
Start in field.

Changed from "C.\Program Files\" to C.\Program Files\
 
Back
Top