Clock Drift monitoring service on N able N central, monitors if the clock is running at the correct time on the server or not. It basically matches the time on the server with an authoritative time such as a public NTP server or one of your choice.
However, sometimes the monitoring service comes up with errors when there is a problem with the configuration. This blog post is about one such error.
201 Cannot convert value “rror: 0x800705B” to type “System.Double”. Error: “Input string was not in a correct format.” At line:158 char:1 + $global:resultoffset = [double]$stat; + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) , RuntimeException + FullyQualifiedErrorId : InvalidCastFromStringToDoubleOrSingle
This is most probably because the firewall is blocking the connection from the device/ N Central Agent to the NTP server. In order to fix this, we need to allow this connection on the firewall.
Once the connection is allowed, you should be able to receive a ping response from the NTP server which means that the connection is working now.
In a few minutes, depending on the service scan interval, the service should be back to normal with the correct status as per the time on the device.
Also, if you find that RDP connections are not working on your N able N central platform, you can find its resolution here in this blog.
We upload blogs on our website every week. To be updated about it, keep an eye on it.