We are getting this 'time difference between idisp.exe on terminal e.g. HPD130 and the dtabase server exceeds the tolerance setting". But when we look at the server time and terminal time every 17min around the time of the error, they are never out more than a fraction. We are stumped.
We are getting "The clocks on the local and database server machines differ by more than the allowed tolerance" in Dispatcher.
We just upgraded to 9.2 MR5 and have been getting this error in Dispatcher machines ever since. We use Presentense on the workstations and servers to synchronize to Spectracom GPS clock with Windows Time Service disabled. Whenever we check the times, as you mentioned, they are only off by a fraction of a second except one time we saw 3 seconds. This is still within the allowed tolerances. Most of our errors are from the w3wp.exe IIS process for Netviewer on the comm/interface server.
As far as I know this has not been reported on our calltaker workstations.
I am starting to think that it may not really be a time synchronization problem.
What version of CAD (dispatcher) are you using? Is this an issue that just started with a certain version?
We were seeing some cases where the time difference was one hour causing us to think this was a Daylight savings time issue
Our previous CAD Technical administrator and Project Leader was back on contract as a consultant and investigated, delivering the attached report. Our thought, based on this is that our problem would have gone away, or reduced in November when we returned to Standard time.
Based on this the Intergraph Support Personnel were able to find an updated "is_dst_now function" that their development team provided. I have altered the function in our development system and will test. Once I have added it to production I will report back.
Brett, thank you for the update. We too had seen this in the caddacerr logs and our times are all via the same to a domain controller; we'll be taking a look at the information in your attachment. Much appreciated.
I implemented this function change in production yesterday and have not had one message in ESMD regarding time out of sync. Normally in this time span I would have had a few from Dispatcher and Calltaker workstations and a dozen from w3wp.exe on the comm server.