This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Calendar Attendant Requests Failed

tyler1 over 8 years ago

I have a critical error for "Calendar Attendant Request Failed" from Oct 22nd. I can't find any reference to what this was, why, it just shows 1 and doesn't reset. How can I see more information (maybe what request), or clear this message? I can't seem where to find any info where looking at the counters but would like to know more about where to see more info.

Parents

0 aLTeReGo over 8 years ago

What you are describing sounds like a bug. This metric should count the statistic as difference between polls rather than continuing to count upward. Rebooting the Exchange server this counter should return to zero, but that's far from ideal. I've logged this for investigation internally under SAM-2426, but I would ask that you please open a case with support so we can investigate this issue further.
Cancel
Vote Up 0 Vote Down

Cancel
0 ibageek over 5 years ago in reply to aLTeReGo

Wondering if this has been fixed as well. We are seeing what looks to be the same thing with the latest version of Solarwinds SAM and Exchange 2016 CU9
Cancel
Vote Up 0 Vote Down

Cancel
0 amaiman over 5 years ago in reply to ibageek

I can confirm that this issue still exists. Exchange 2013 CU21 and latest Solarwinds SAM.
Not willing to waste time on a support ticket to be told "we'll fix it someday", but it would be nice if a fix was released. For now I edited the thresholds to make the alert go away (and thanks to SolarWinds not allowing me to edit the template [it just does nothing when 'Submit' is clicked], I had to do it manually on each Exchange server's node) since this counter doesn't correspond with any user-facing issues.
Anecdotally, the counter went to 1 around when I moved two mailboxes to different mailbox databases (may be coincidental timing).
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 amaiman over 5 years ago in reply to ibageek

I can confirm that this issue still exists. Exchange 2013 CU21 and latest Solarwinds SAM.
Not willing to waste time on a support ticket to be told "we'll fix it someday", but it would be nice if a fix was released. For now I edited the thresholds to make the alert go away (and thanks to SolarWinds not allowing me to edit the template [it just does nothing when 'Submit' is clicked], I had to do it manually on each Exchange server's node) since this counter doesn't correspond with any user-facing issues.
Anecdotally, the counter went to 1 around when I moved two mailboxes to different mailbox databases (may be coincidental timing).
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Khenikandza over 3 years ago in reply to amaiman

Same with me. Latest SAM and 2016 Exchange server. Has anyone fixed that issue w/o rebooting server?
Cancel
Vote Up 0 Vote Down

Cancel
0 davisstandard over 3 years ago in reply to Khenikandza

Did rebooting the server even help?
Cancel
Vote Up 0 Vote Down

Cancel