I am getting the following error message: 04-21-2010 12:52:07.753 ERROR ExecProcessor - Couldn't start command ""C:\Program Files\Splunk\etc\apps\search\bin\scripts\test1.path"": FormatMessage was unable to decode error (193), (0xc1)
Running powershell scripts with Splunk might seem a little tricky. Here's what my setup looks like:
[script://.\bin\myscript.path]
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& '$SPLUNK_HOME\etc\apps\myapp\bin\myscript.ps1' -myarg1 -myarg2"
Running powershell scripts with Splunk might seem a little tricky. Here's what my setup looks like:
[script://.\bin\myscript.path]
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& '$SPLUNK_HOME\etc\apps\myapp\bin\myscript.ps1' -myarg1 -myarg2"
.path wouldn't load environment variables like $SPLUNK_HOME so I had to go with .bat
Anyone know why the .path vs .bat? Pros/Cons between the two?