windows scheduler: how to fix the problem: Status: Could not start

i used windows scheduler to start a c# executable. the status: Could not start.

jgordinAsked:
Who is Participating?
 
sramesh2kCommented:
Open Scheduled Tasks folder. From the "Advanced" menu, click "View Log"

See if there are any additional info available in the log.

Example: You'll see something like these:
      Result: The task completed with an exit code of (0).
      Result: The task completed with an exit code of (1).
0
 
Kiran Paul VJComputer EngineerCommented:
try some other exe
0
 
Éric MoreauSenior .Net ConsultantCommented:
it maybe related to credentials, path, ... do you have other hints?
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
imateyelectronicsCommented:
Check to make sure that you have Administrative access and that you are putting in the correct password.  Also make sure that the program isn't being used by another application or has already been started.
0
 
jgordinAuthor Commented:
it turned out that i put *.exe. the Run: expected *.exe.config  <--- browse directory. Now i think the the sheduler trying to run program  (i see last run time updated) but nothing happens.
0
 
Éric MoreauSenior .Net ConsultantCommented:
are there any arguments to provide? have you set the initial folder? can you add trace to your application so that you can know where it stops?
0
 
jgordinAuthor Commented:
thanks. i will check.
0
 
jgordinAuthor Commented:
i checked the log. this is what i get:

Started 8/17/2007 9:15:00 AM
Started indirectly, through a shortcut; task finish will not be logged.

how do i fix that problem? thanks.
0
 
sramesh2kCommented:
>> Started indirectly, through a shortcut; task finish will not be logged.

Did you configure a .lnk (shortcut) to run (instead of mentioning the direct .exe file name) per chance? If so, try deleting the task and creating a new one, pointing directly to the .exe file.
0
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.

All Courses

From novice to tech pro — start learning today.