
Hi there,
I've just upgraded NPM to 10.2, APM to 4.2 and NTA to 3.8 from 10.1.2, 3.8, 3.7 respectively.
I added to Exchange 2010 Client Access Role Counter (Advanced) and the Exchange 2010 Client Role Services templates to 2 of my Exchange 2010 Client Access servers and both came up sweet.
However 12 hours later, the application monitors on 1 server went down. When I test the monitors, I get multiples of the following errors:
Testing on node <server name>: failed with 'Down' status
| Access to the registry key '17966' is denied. |
Is the remote registry service running on the monitored server? I've seen cases where the Remote Registry service is stopped for some reason and this causes the polling issues you describe.
Thank you aLTeReGo! We restarted Remote Registry Service on the Exchange server and things are back on track again! :)
Interestingly, the service was up and there were no errors in the event logs.
I was searching the forum on this issue as my exchange APM monitors were giving me the same registry type errors. I restarted the Remote Registry service and everything worked. Problem is after awhile everything goes red again and when I check info it is the registry denied error once again. Is that indicative of something else? Appreciate it.
If you open the Windows Event Log of the monitored host you should see the error that resulted in the service to stopping. It should provide some insight as to what caused the issue.
Thanks for the reply. I didn't explain this well, but the remote registry service is not stopped when this error happens. It never stops. I have to keep restarting it and the pollers show up fine, and then I'll check back later to see them red with the registry denied error. I check the target server and the service is still running fine. Appreciate any input you may have.
we have the same problem with 2008 R2 servers.
Basically we've jsut scheduled the remote registry service to restart every couple of hours.
not practical, I know. But there is so little information on the fault that we have to work around it until we find the fix.
Jonorowe,
Thanks for the reply and I may go that route as well. Thanks for the info.