Last Updated on
KB Article # 9823
Ephesoft Version: 4x
Issue: [com.ephesoft.dcma.core.service.ServerHeartBeatMonitor] – Fatal transport error
Heartbeat service is responsible for checking whether the servers registered in the database are still active. This is important for service failover assignments. If this error log is reported it could mean a server is down. If you know that this is not the case and the reported server is active, the heartbeat service may be blocked or there may be issues with your network infrastructure.
To test your server for heartbeat accessibility, two tests can be run on the server recording the error:
- Ping the remote server by computer name recorded in server_registry table.
– If the server responds with an ipv4 scheme, this is appropriate.
– If the server responds with an ipv6 scheme, disable ipv6 via Microsoft’s solution.
– If the server does not respond, the server may be down, there is a firewall or network infrastructure issue.
- Open a chrome or firefox browser and go to the following url
– If the message states – “Server is up.”, accessibility is correct.
– If the page is unreachable, the server may be down, there is a firewall or network infrastructure issue.