Fixing Non-Connecting Windows OS Servers

Overview

This article is for users who have issues with the Sensage AP Windows Retriever component when it isn't pulling any new logs into the spool directory after configuration and upon starting it.

 

Affected Versions

Sensage AP all versions

 

Root Cause

Misconfiguration in filterids setting.

 

Resolution

  1. In the collector review the Windows Retriever agentless.prop configuration file and check the uncommented configurations in search of a non-empty filterids setting.
  2. If this setting has event IDs that will never be received or invalid strings in the setting, comment it out as this is the cause of all event IDs to be discarded and none written.
     

Validation

The fix should work if users restart the collector and events are received as normal.

 

Course Author: Miguel Molina

Comments

0 comments

Please sign in to leave a comment.