Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Cannot locate a file using File Existence Monitor

Cannot locate a file using File Existence Monitor

Table of contents

Updated June 8, 2018

Overview

In most circumstances, File Existence Monitor can locate a file if the queried file is on the polling engine. However, the * wildcard may not work correctly and the queried file may not be found on a monitored node.

Environment

  • All SAM versions of SAM

Detail

Ensure that the file path specification contains the variable for the IP address. When using this specification, you can use the * wildcard to check if the file exists.

 

For example, if you check the path D:\XLFRE_PRD\logs\java_pid4341.hprof , 4341 could be any number. 

 

The correct file path specification to enter into the monitor would be:

\\${IP}\D$\XLFRE_PRD\logs\java_pid*.hprof

 

When you test the monitor to check if a file exists, make sure you are using the entire file name and the extension is NOT hidden from view in File Explorer.

 

 

 

Last modified

Tags

Classifications

Public