Fellow Chuggers,
Curious whether any other sites have experienced this issue:
Our DTS has changed the time on its internal clock twice in the past 3 months. The first time occurred back on August 3rd. This time the DTS went down last night (11/3) at 6:55pm (unexpected serious database error) and when it was restarted at 9am the DTS clock read 1:21pm.
GE had provided a script last time to correct the time change on the DTS, but we had a large batch of messages that were time stamped with the incorrect time (b/w 1:21pm and 1:36pm) and couldn't be transferred until this afternoon when that time.
GE says that they don't know how or why this happened (they suggested possible causes such as, solar flares and daylight savings time (seriously)) and have never seen it before. Yet they have a script to correct the issue on hand (suspicious).
Has anyone else experienced this? It seems like a quarterly occurrence. We would really like to get some answers from GE, but as you know that's difficult to do without pressure. Corroborating organizations would be a big help! Maybe Doc Brown and Marty McFly could get to the bottom of this!
Solar Flares, lol.
If it does turn out to be that please let me know so i can keep track of solar activity in the future.
Is your DTS virtual or physical? Where do your domain computers sync their time from? Are any other computers displaying an incorrect time? If you aren't sure of where your time sync comes from, you can go to your DTS and open an elevated command prompt. type w32tm /query /status
Yes P vs V question is a good one. In both cases you want to make sure all the time syncing is setup right especially in virtual environments as clock issues can cause all kinds of madness.
It is a virtual environment. Our server team is emphatic that it isn't due to the environment, but I will run that status prompt. Thanks!
With virtualization, it is most likely a product of the environment. Your virtual host could be over-taxed, your DTS could be under specs...etc.