Script monitor just stopped working
I have configured a simple Script Monitor which was working perfectly for weeks. It executes a batch file (which does nothing - it is called doNothing.bat). Then it reads the contents of a log file and reads a numeric value. It has been working fine for a while now, polling every 10 minutes, 24/7. Then today, it just stopped working - it says:
Health Resource is down.
Health is critical as the resource is not available
It is still reading the log file which is good, but it seems to be having trouble with executing the batch file.
I have tried several things to resolve the issue: deleting the monitor and creating a new one; executing different batch files and VBS scripts; checking the security on the batch file; stopping and starting the ManageEngine App Manager service. Nothing has worked - it still reports that the Resource is down.
Why would it suddenly stop working - nothing on the server was changed.
As a side issue, when I deleted the monitor I lost all the data that has been collected for the past couple of months. Fortunately I have a log file with all the data - is it possible to import the data into the App Manager database?
As a further aside - is there a better way to read the contents of the log file? I don't actually care about executing a batch file - I have just configured it this way because it is a mandatory field. All I really want to do is read the contents of a log file every 10 minutes. If App Manager can do this using a different monitor then I don't care about fixing the Script Monitor which seems to be broken.
New to ADSelfService Plus?