Micros - Time Change issue - closed sales mid-day

[brewermoe]

Hello !

We had one of our servers, MS Serv03R2, not shift the time with the Daylight Savings, it wasn't noticed for a couple of days. When it was noticed, the time was reset back one hour at the start of the business day, no sales had yet been committed to the system. The Micros system was then restarted and the time confirmed with the Server, the POS and the real time. The next day the server's time was 12hrs and a few mins ahead of the real time and the Micros was 14hrs and 13mins ahead of the server. This caused the current day to closed and the next day to start during the same shift. Did the initial time change earlier the previous day incur this? If not what may have caused this? Is there a known issues with Serv03 and Daylight Savings? ... ?

 

[hosehead78]

What is your version of Micros?

 

[brewermoe]

Micros Version 4.6 (Build 4.6.4.2070)
POS 3700 Version 4.9.4 3103

 

[pmegan]

There isn't anything that I know of with Win2003 and DST. I've got 15 Micros 4.x servers running on it and haven't had DST issues in years.

 

[hosehead78]

Same here. I don't even know of any area of the Micros DB that would store time like this.

 

[brewermoe]

Micros Support is looking into correcting the DST issue, but would the manual change back one hour cause the time quirk later in the day? (See 1st post)

 

[brewermoe]

Just to clarify, DST is not set to auto, there is an issue with this Serv03r2 so wuauclt has not been ran in quite some time, hence the change in DST is not being updated and the time change is being done manually. We are upgrading this server in the near future.

 

[pmegan]

No, changing the time manually at the start of the day wouldn't cause it jump back 12 hours later on. Micros relies on the server for the date/time and has no way to change those settings. The only DST problems I've ever seen with Micros were ages ago, when everything was stamped with the local time. At that point 24 hour businesses would have funky issues like checks that were already opened when the clocks changed being closed before they were open, and check sequence number being out of sync with the time.

Since you're running on Win03 I'm assuming the server is on the old side. It might be your BIOS battery starting to die and losing track of time.

 

[brewermoe]

So what may have caused the Micros to be 14+ hours out?

 

[pmegan]

No idea, it would be something with Windows on your server. I've had random time changes a few times on our Micros servers. Once it was the BIOS battery dying. The rest I couldn't figure out, but they mysteriously stopped as soon as I disallowed changing the system time for the local power users group, which is the security setting for all of our managers.