Why Splunk could not get the description for this event?

hrawat — Mon, 06 Feb 2023 17:53:47 GMT

Issue happens after windows server is restarted. Restarting splunk universal forwarder fixes the issue.

Either the component that raises this event is not installed

Re: Splunk could not get the description for this event. Either the component that raises this event is not installed

hrawat — Mon, 06 Feb 2023 14:22:25 GMT

There are two workarounds.

1. Use 'Delayed Start' for the Splunk Forwarder service. (https://community.splunk.com/t5/Getting-Data-In/Why-quot-FormatMessage-error-quot-appears-in-indexed-message-for/m-p/139981/highlight/true#M28764). However it's hard to configure thousands of DCs.

2. Configure interval as cron schedule instead.

interval = [<decimal>|<cron schedule>]

[WinEventLog] interval=* * * * *

By default wineventlog interval is 60 sec. That means as soon as splunk is restarted, wineventlog (or any modinput) is immediately started. Subsequently every 60( configured interval) splunk checks if modinput is still running. If not, re-launch modinput.
Instead of setting interval 60 sec, if we use cron schedule to run every minute, then splunk is not going to launch modinput immediately. So essentially the idea is to convert interval setting from decimal to cron schedule to introduce a delay.

Re: Why Splunk could not get the description for this event?

hrawat — Mon, 17 Feb 2025 15:09:40 GMT

Also another workaround https://community.splunk.com/t5/Knowledge-Management/Solutions-quot-Splunk-could-not-get-the-description-for-this/td-p/694752

topic Re: Splunk could not get the description for this event. Either the component that raises this event is not installed in Getting Data In

Why Splunk could not get the description for this event?

Re: Splunk could not get the description for this event. Either the component that raises this event is not installed

Re: Why Splunk could not get the description for this event?