Getting Data In

Powershell script is throwing off error message, what does it mean?

rsimmons
Splunk Employee
Splunk Employee

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)

Tags (1)
1 Solution

Leo
Splunk Employee
Splunk Employee

Running powershell scripts with Splunk might seem a little tricky. Here's what my setup looks like:

  • default\inputs.conf
[script://.\bin\myscript.path]
  • bin\myscript.path
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& '$SPLUNK_HOME\etc\apps\myapp\bin\myscript.ps1' -myarg1 -myarg2"

View solution in original post

Leo
Splunk Employee
Splunk Employee

Running powershell scripts with Splunk might seem a little tricky. Here's what my setup looks like:

  • default\inputs.conf
[script://.\bin\myscript.path]
  • bin\myscript.path
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "& '$SPLUNK_HOME\etc\apps\myapp\bin\myscript.ps1' -myarg1 -myarg2"

sloshburch
Ultra Champion

.path wouldn't load environment variables like $SPLUNK_HOME so I had to go with .bat

0 Karma

sloshburch
Ultra Champion

Anyone know why the .path vs .bat? Pros/Cons between the two?

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk, and empower your SOC to reach new heights! Duration: 1 hour  Prepare to ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...