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.

asked 2 days ago

Macbrun's gravatar image

Macbrun
433
accept rate: 0%


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.

link

answered 2 days ago

Doug's gravatar image

Doug ♦♦
10.2k122138
accept rate: 21%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×80
×10
×3

Asked: 2 days ago

Seen: 28 times

Last updated: 2 days ago