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
Splunk Employee
Splunk Employee

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

0 Karma

sloshburch
Splunk Employee
Splunk Employee

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

0 Karma
Get Updates on the Splunk Community!

Technical Workshop Series: Splunk Data Management and SPL2 | Register here!

Hey, Splunk Community! Ready to take your data management skills to the next level? Join us for a 3-part ...

Spotting Financial Fraud in the Haystack: A Guide to Behavioral Analytics with Splunk

In today's digital financial ecosystem, security teams face an unprecedented challenge. The sheer volume of ...

Solve Problems Faster with New, Smarter AI and Integrations in Splunk Observability

Solve Problems Faster with New, Smarter AI and Integrations in Splunk Observability As businesses scale ...