When I use the File Content Sensor from PRTG, asking it to search a local file for any search string, it always returns 0 matches and not found.

If I go to command prompt on the probe, navigate to the Sensor System folder and run the LogFileReader with required switches, it finds matches and output everytime.

Why is this? I am not specifying a user when I manually run it, so I assume it is running as my user.

Article Comments

Hello,

it's probably the difference of accounts here, if the Probe Service is still running under LOCAL SYSTEM-Account.

best regards.


Mar, 2013 - Permalink

Correct it is running under local system account. I've even moved the log file to the local system the Probe is running on and it still doesn't return known matches.

I don't see anyway to run the File Content Sensor under different credentials as is. I know that running the EXE the sensor uses I can define different creds there.


Mar, 2013 - Permalink

Then please try running the Probe Service under your account instead of the Local System.


Mar, 2013 - Permalink

Check the encoding of the file you will monitor.PRTG will get the wrong result if it does not support the file encoding.I tested the UTF-8 is ok.And the best way is that check the encoding of an existing file with right monitor result.


Sep, 2017 - Permalink