Splunk Enterprise

Scripted input throws "FormatMessage was unable to decode error (193), (0xc1)"

rksplunk7
Engager

Splunk universal forwarder Scripted input cannot run perl script. whereas if i try to execute the same script with "Splunk cmd" it works perfectly.

Below is the error message noticed in the Splunk var log:

05-14-2018 23:05:44.994 -0700 ERROR ExecProcessor - Couldn't start command ""C:\Program Files\SplunkUniversalforwarder\etc\apps\search\bin\Test.pl"" FormatMessage was unable to decode error (193), (0xc1)

Any comments/help on this.

Tags (1)
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...

Build and Launch AI Agents from Your Splunk Workflows

  Register We’ve all been there: juggling alerts, runbooks, and endless manual searches. What if you could ...

Splunk Cloud Application Management in Terraform

Register   On Tuesday, August 4 at 11AM PDT / 2PM EDT, we’re diving into how you can bring Infrastructure as ...