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!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...