I've had to do this a time or two in a development environment. Sometimes you can find it under System Operation > Processes and terminate the process. If that doesn't work, you can look at the process ID of the process and kill it at the OS level (the kill command in Linux, or taskkill in Windows). Just be aware that depending on what it's doing and how the task was written, you may end up with some weird stuff.
A handy way to find the process is to check your lock table. These processes will typically take out a lock based on the Task ID. This can be used to find the process, examine it and kill it if required.
It's also possible in some cases for the process to die and not update the task, and this can account for no processes matching this criteria
Hi Rochdi,
There's no built-in way to do this, but WRC can help you stop the process if needed.
I've had to do this a time or two in a development environment. Sometimes you can find it under System Operation > Processes and terminate the process. If that doesn't work, you can look at the process ID of the process and kill it at the OS level (the kill command in Linux, or taskkill in Windows). Just be aware that depending on what it's doing and how the task was written, you may end up with some weird stuff.
That's the strange thing, checked processes and can't find process ID for it !
Will restart ensemble, thanks guys
if you know the process id then $SYSTEM.Process.Terminate( . . .) should terminate it
A handy way to find the process is to check your lock table. These processes will typically take out a lock based on the Task ID. This can be used to find the process, examine it and kill it if required.
It's also possible in some cases for the process to die and not update the task, and this can account for no processes matching this criteria