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 Friday, April 03, 2015 1:09 PM 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 Friday, April 03, 2015 1:39 PM screenshot
• Proposed as answer by Andy DavidMVP Friday, April 03, 2015 1:44 PM
• Unproposed as answer by BriGy86 Friday, April 03, 2015 1:48 PM

This happened again after removing that Health API entry.

From Recovery Action Results:

Recovery Action Failed. (ActionId=RestartService, ResourceName=IMAP, Requester=ImapCTPRestartService, InstanceId=150414.111637.23822.001, ActualStartTime=2015-04-15T04:16:37.2382275Z, ActualEndTime=2015-04-15T04:16:37.5663405Z, ErrorMessage=Service IMAP was not found on computer '.'.)

Monitoring Log:

Imap is failing on ClientAccess server <SERVERNAME>.
Incident start time: 4/15/2015 4:12:36 AM

Last failed result:
Exception: System.InvalidOperationException: Unable to initialise TCP Network connection ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:993
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.Common.TcpConnection..ctor(EndPoint targetEndpoint)
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.Common.Imap4Connection..ctor(IPEndPoint endpoint)
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.PopImapProbeUtil.CreateImapSSLStateObject(IPEndPoint targetAddress, ProbeResult result)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.ImapCustomerTouchPointProbe.HandleSocketError(Exception e)
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.PopImapProbeBase.HandleConnectionExceptions(PopImapProbeStateObject probeTrackingObject)
   at Microsoft.Exchange.Monitoring.ActiveMonitoring.PopImap.Probes.ImapCustomerTouchPointProbe.DoWork(CancellationToken cancellationToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.Execute(CancellationToken joinedToken)
   at Microsoft.Office.Datacenter.WorkerTaskFramework.WorkItem.<>c__DisplayClass2.<StartExecuting>b__0()
   at System.Threading.Tasks.Task.Execute()

Diagnostic command: Invoke-MonitoringProbe -Identity:"IMAP\ImapCTPProbe" -Server:<SERVERNAME> | fl

• Edited by BriGy86 18 hours 20 minutes ago Formatting

I got similar errors for the pop service as well.  Do I need to add the loop back address here?