Domino Time - System time out of Sync - Now / SetNow

Hi all.

This is our problem:

We have moved our Domino server to vmWare server, and now system time and Notes Time are out of sync, or so it seems:

The problems we’re having is comparing time from LotusScript Now function, and the time form the NotesDateTime.SetNow function. These times are sometimes not the same, so it seems, that one of them is getting data from system, and the other from Domino server. Is that correct?

Since there are MANY agents, that have used the mixture of Now and SetNow for years, I don’t feel line going through all of them and start changing things - so is there any way to make Domino use system time all the time :), and not use its own?

Thanks in advance, Miha Vitorovic

Subject: Domino Time - System time out of Sync - Now / SetNow

I know that Domino time vs OS time issues were supposed to be fixed, but this does seem to ring bells with older versions.

With R4, there was a trick where you opened the Notes client on the server, selected File, Mobile, Edit Current Date/Time, then cleared out what was in the current date/time field and hit OK. This would force the server to re-read the OS time. I’ve no idea if that would still work on an R6 server, but it might be worth a try…

Subject: Server date format - changes from DMY to MDY

Thanks for your post, Geoff.

Our problem is that the date format on our ND6 servers changes from the desired DMY format to MDY. The servers start up with the DMY format, based on the .Default user registry settings, but then change to MDY after a random period of time, as recorded in their Notes logs. We think the problem may be due to OS Locale settings on a time sync server, but currently this is unproved.

In any case, previously the only way to reset the date format was to reboot the Domino servers. However, having read your post, I tried running nlnotes.exe on the servers and selecting File → Mobile → Edit Current Time/Phone. I found that by simply doing this without making any changes to the field settings, was good enough to force the servers back to the desired DMY date format.

So there you have it, an R4 workaround that works with ND6.

Regards,

Robert Fairhead

robertf@rocher.com.au