Hello @BenBa ,
Thanks for reaching out.
Here are some possible cause which I could think at this point, but this would require more data collection such services.msc insight and system debugs (Like Memory, CPU etc..,) to figure out actual cause.
Possible causes:
- Verify the allocated RAM memory for Sync server and make sure if there any other services are utilizing more memory/making any memory leaks by any chance? If the agent has 4GB of memory, then try upgrading to 8GB+ of memory would alleviate this issue. Hardware requirements for Azure AD Connect
- If the first option is not viable/preferred, edit the config to allow higher memory usage for this Sync Health agent. We cap the amount of memory/cpu usage to prevent the agent from ever bringing down the machine due to memory leaks or other scenarios (would be a bit counterintuitive for a health agent). You can edit this file (path may be slightly different if installed in a non-default location):
<add key="MaxPercentageMemoryUsage" value="10"/>
Edit the value to a higher percentage (Based on trends, I recommend 18-20). This will allow the agent to use more memory without restarting constantly. This is not as preferred because you will need to reapply this fix every time the agent is upgraded, but would be a temporary fix.
If non of above fix the issue then I would recommend you to reaching out Support team for active troubleshooting. Hope this helps.
Regards,
Siva Kumar Selvaraj
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.