All Apps and Add-ons

ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\SA-Splice\bin\taxii.py"" '\xef\xbb\xbf\n'

AOkey43
New Member

I have received this error message multiple times now and have no clue what it means. Has anyone else seen this/know what to do about it?

Tags (1)
0 Karma

borgy95
Path Finder

The second error message is saying there is an error in the spli.conf file... which specifies the connection instructions to mongodb, so id check you have that correct. the pdf doc that comes with splice explains the format you should be using.

Also What OS are you using, if it is linux check you have a /etc/sysconfig/clock file. If not see the following thread for what you need to create: http://answers.splunk.com/answers/223679/splice-error-execprocessor-message-from-python-opt.html

0 Karma

AOkey43
New Member

Sorry about the late response.

It is a fresh install, and no, I do not have such a directory. This error message pops up very frequently, along with the following messages:

alt text

0 Karma

borgy95
Path Finder

Need a bit more information here...

Has splice worked previously or is this a fresh install?

Do you have a directory called: \ xef \ xbb \ xfn \ n

0 Karma
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!

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Federated Search for Dynamic Data Self Storage Is Now Generally Available on Splunk ...

 Splunk is excited to announce the General Availability of Federated Search for Dynamic Data Self Storage ...

Index This | What has many keys but can’t unlock a door?

July 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...