|
| endprogram does not kill process |
| Iniciado por guest, 24,may. 2017 08:16 - 2 respuestas |
| |
| | | |
|
| |
| Publicado el 24,mayo 2017 - 08:16 |
Hi All
I have this small program which is being run by a scheduler.
all is ok but the command endprogram does not remove the job from the task manager and it stays there consuming cpu time untill the next call where it is terminated by the scheduler and started again.
On the development computer the program terminates normally.
Does anybody have an idewa of why this happens?
Thanks
Noel |
| |
| |
| | | |
|
| | |
| |
| Publicado el 24,mayo 2017 - 15:54 |
Hi Noel,
This problem could be related to any number of issues, but the first thing I would do is grab a utility like WinSpy or ProcessExplorer to see if there are any hidden GPF or other windows being thrown up.
If that method doesn't yield an answer, I would log the Process ID out to a file and then write a small utility that would run either as a service or a scheduled task. This utility would read the Process ID's out of the file and see if they are still running and kill them if they are. You can add additional conditions as to when to kill or ignore them.
Also make sure the user you are lunching the scheduled task under has enough rights to perform whatever it is that you're doing in the exe, otherwise, that will be the cause of the hang.
Cheers!
Ken |
| |
| |
| | | |
|
| | |
| |
| Publicado el 25,mayo 2017 - 06:46 |
Hi ken
thanks. will try winspy and check.
Regards
Noel |
| |
| |
| | | |
|
| | | | |
| | |
|