No heartbeat

by Jan 8, 2016

Even though we have restarted the server and the services compliance manager has not had a heartbeat since November 29. This is when we changed domains.
We also have had a problem with the trace log running amok. This filed the C: drive of our production server with the message “Unable to update the database IDs for (Monitored Server) Error: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it (Our IP):5201″

The trace file has stopped outputting, which confuses me, and no data is being collected.

So how do I find or fix the heartbeat problem and set things to working again?

Thank you,