I know there are various articles about this failure. the solution that works for us is that I clear the cache, and then it stays away for 1..2 weeks. but it remains a reoccurring issue for our management servers (so maintenance mode is not an option)
but flushing the cache on your management server - especially the one with the RMS emulator role - is annoying and not really "professional"....
has there ever been determined if there is a root cause for it ?
is it a performance issue, overload, script error etc... ???
is there a permanent fix ? there is no information in the Health explorer, no failures for the nodes below this rollup monitor, so I don't know why it got triggered in the first place...