Exe Execution using Task Scheduler

Question

1.00/5 (2 votes)

See more:

I am having two exe, One exe will internally call other exe from the server

I am facing issue while execution the Exe using Task scheduler
while executing exe using task scheduler the second exe gets triggered and then goes in hang state

Please help me on this

Is that any environment issue or the Cmd.exe issue?

Posted 14-Jan-15 1:36am

Neha89

Add a Solution

Comments

Richard MacCutchan 14-Jan-15 7:39am

Well since we cannot see your screen, and have no idea what your code does, it is impossible to make any sort of guess. Please edit your question and add some proper details.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Answer 1 · 2015-01-14T04:30:00

If you run a program using cmd.exe or to run a batch script it may seem hanging if the command was not parsed correctly. The cmd.exe program is just active in the background waiting for commands to enter (but as it is not visible this can take forever). cms.exe from the taskmanager is started with the current directory to "c:\windows\system32". You might want to add the path to your exe or bat script to the environment path or just specify the absolute path to your program (between quotes if there are spaces involved).
My advice would be to simply test it by simply copying your exe or bat to "c:\test" and then in the task something like "c:\test\test.bat" or "c:\test\test.exe".

Good luck!

ps. in case of a bat file, you might also need to terminate it by putting EXIT explicitly at the end.