I am trying to write a task that will stop a running process. The command I am trying is:
wait pathname of client folder of site “BESSupport” & “\taskkill.exe /f /im pddm.exe”
When I run this in the Fixlet Debugger I get “Unknown action command”. I tried putting:
pathname of client folder of site “BESSupport”
in my relevance debugger and I get “Singular expression refers to nonexistent object”. I have seen lots of posts about people using this to stop running processes so I believe it should work in my environment. I checked and we are subscribed to the BES Support site and I have tried other sites as well and get the same error message in the relevance debugger. I have tried the command on multiple computers with the same error.
I tried that command and it did not work. In the client log it says “Command failed (Relevance substitution failed)”. I tested the relevance statement:
pathname of client folder of site “BESSupport”
and I get “Singular expression refers to nonexistent object”. I tried a different site “Actionsite” and got the same response. It seems as if it cannot pull up its list of sites. I am able to push out fixlets and other tasks but this relevance does not work.
pathname of client folder of site “BESSupport” & “\taskkill.exe”
in the Fixlet Debugger and get “Singular expression refers to nonexistent object.” If I double click on the taskkill.exe I get a window that opens and then closes so I know the executable works. What object is it not able to find?
I don’t think that expression will work in the Fixlet Debugger b/c it requires client context. Basically, the debugger has no idea which sites exist. If you evaluate the expression as part of a running action, it should work. To test it out, you can write the result to a file and look at the result:
appendfile {pathname of client folder of site “BESSupport” & “\taskkill.exe”}
After the action runs, look in your operator site if you’re a non master operator or the action site if you’re a master operator, and you’ll find a file called __appendfile. The result of the expression will be in there.
I tried that comamnd and the resulting command looked correct. I then ran the command in an action script and it did kill the application that was running. I just assumed that I could test the script without havign to actually running it but now I know that the command works.