Hi all,
I have a Python script that is triggered via alert actions. I was able to get it to work in a lab environment, but when moving to our production machine I keep getting "Execute program failed with exit code 1" despite a lot of troubleshooting.
I am able to log in as the service account the actions use and run the script successfully on the command line. The credentials test in the UI also passes.
The network paths I am providing the actions have the following format:
C:\Program Files\Python312\python.exe "C:\<path to Python script>" "${N=SwisEntity;M=NodeID}" "<Custom Property>"
It is also approved in Database Manager. (If it was not, I would be getting a different error anyway.)
I tried looking through logs like ActionsExecution.log and ActionsExecutionAlert.log and did not gain any more information other than SolarWinds seems to be making the expected request. (I used Log Adjuster to try to log as much as possible.)
The first thing my script does is generate a log file, in this case no log file is getting generated. This means the script is not being ran, or it fails before it even gets to create the log file.
In Windows' Event Viewer, I can see the service account logging in and attempting to execute python.exe. I feel like it should be successful in doing so since I am able to log in as that user and run the script directly. (It is also successful when using the "runas" command.)
Does anyone have suggestions on how to troubleshoot this further?
