Good day, We are getting the subject error message regularly (daily). The administrator for the server with the affected share doesn't see anything wrong and I can't find an issue on the Server Monitor side. Any ideas for things to check? FYI: the affected share is on the same server and uses the same credentials as other shares that Server Monitor has no issue accessing.
6 Answers
For situations like this we recommend taking PA Server Monitor out of the picture and trying a test.
So for example, let's assume PA Server Monitor is installed on server MON1 and it is trying to access the share \SERVE1myshare. Further, the PA Server Monitor service is running as DOMAINsvcacct.
We would recommend that you login to MON1 as DOMAINsvcacct. Then see if you can use Windows Explorer to access \SERVE1myshare. If you have server-specific credentials set in PA Server Monitor for SERVE1, then you could use them here when trying to access the share.
This normally exposes whatever underlying issue is blocking the monitor since you are doing essentially the same thing as what the monitor is doing.
I logged into the file server as our service account. Access and permissions are the same on all ten shares on that server. However, only one of those ten is giving me that error message.
"Monitor [fileserver.xxxx.xxx] [fileserver.xxxx.xxx - ProblemShare Directory Quota Monitor (Tu, Th, Sa @ 1am)] failed to run. The reason given:
No files can be found in \ fileserver.xxxx.xxxC$SHARES ProblemShare for monitor fileserver.xxxx.xxx - ProblemShare Directory Quota Monitor (Tu, Th, Sa @ 1am)
Restarting the service, or checking access rights, may help in some situations.
Status=msCANTMONITOR, Version=9.5.0 (Build 133)
Sent from PA Server Monitor on PAMONITOR (111.111.111.111) - 24 Jan 02:32 PM
Ver 9.5.0 (Build 133)
System Alert Rule: Error: Monitor failed to run or can't monitor resource”
Please log in to the monitoring server PAMONITOR as the service account, and then try to access \\fileserver.xxx.xxx\C\$SHARES\ProblemShare from there.
Followed those instructions and I can mount and browse all the shares but the problemshare. This has to be an issue on the fileserver, right?
Yes, if Windows Explorer won't let you browseaccess the share either then there is something going on, probably on the share side.
One gotcha to look out for is a typo, such as a lower case L and an upper case I looking the same in some fonts. I've been tripped up by something like that myself.
It might also be possible that a share has a zero-width character in the name (unlikely, but possible). In this case and the above case it would help to copy the share name to a text editor that can show all characters (Notepad++ for example).
Related