Has anyone seen an issue before where checks are being created with a timestamp one hour into the future despite the time, and timezone being correct on the server, workstations, and even KDS?
It is happening for all orders, both through the API and manually. The workstations are CE devices, but it also happens on orders input from the back office which is obviously Win32. There is a single Win32 workstation acting as the backup server; this workstation also has the same problem (the store isn't in backup mode, its just a ready-to-go backup server).
Very strange, does the 3700d log or print journals log in the correct time? Might try incrementing the time on the server to a minute forward and back.
Yup. The times are correct in the logs. It is very strange. And if I manually insert a row into DBISQL using NOW() as the datetime it is inserting correctly.
Try turning off the DST setting on all the computers, the server and backup server. Set the time on the server to the correct time. Make sure it gets changed by a minute at least. If all is good re-enable DST just on the server.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.