Okay, here’s a strange one. The server clock is right, the user’s clocks are right but when a document is created in databases (including mail) the Modified date of the documents are being marked in the year 2020.
We had some trouble with a server’s clock changing about 2 years ago but it was replaced.
I have looked at some of the responses to the time change and the solution seems to be to create replica copies and replace the existing database.
The weird thing is that this is happening NOT just for 1 user in 1 database but seemily across all databases. And it just started… no one, or the server, put their clock that far in the future. How can this be done for everyone and all databases?
Subject: Documents being marked modified 16 years in the future
There have been other reports of clocks changing intermittently, but I do not remember seeing any solutions. I can imagine that some badly-written software might change the system clock for its own crazy purposes from time to time, then put it back. I can also imagine a flaky clock chip delivering the wrong date occasionally. But these scenarios are just my imagination. I wonder what you would find if you run an application that checks the year every second or so, writing to a log if it is not 2004?