I have a new Exchange 2013 server on premisses.  Twice in the last week some of the server components have been marked as inactive.  Is there a way ti figure out why this is happening?

This is randomly stopping mail flow from our ticket tracking software because it uses POP3

These are the commands I had to run before.  I will correct this IMAP proxy one in just a bit;

Set-ServerComponentState -Identity lo-exch2 -Component imapproxy -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component forwardsyncdaemon -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component PopProxy -Requester HealthAPI -State Active

Set-ServerComponentState -Identity lo-exch2 -Component provisioningrps -Requester HealthAPI -State Active

• Edited by BriGy86 18 hours 14 minutes ago Added new screenshot

The only thing I have seen to check when these go inactive is this.  But it doesn't explain why.

• Edited by BriGy86 17 hours 44 minutes ago screenshot
• Proposed as answer by Andy DavidMVP 17 hours 39 minutes ago
• Unproposed as answer by BriGy86 17 hours 35 minutes ago

The only thing I have seen to check when these go inactive is this.  But it doesn't explain why.

Yes, delete any entries below the key ( Health or Maint API) etc.. for the specific component and it should go active again

Like these? But why does this keep breaking?

Like these? But why does this keep breaking?

Yes, delete the HealthAPI and then see if goes inactive again. Typically it does not. If it continues, then check the Managed Availiblity logs in the event logs