We’re having sporadic ‘problems’ in DWA after applying all the server-side DST patches are recommended by IBM. Some users are still receiving the message:
“Your timezone setting is different from your operating system’s current one. You can change your timezone setting by going to the Calendar section in the Preferences dialog.”
This seems to appear regardless of whether the client OS has the patched applied or not. The OS on their PC and DWA is correctly set to the proper time zone. Has anyone else ran into this?
A. Error: “Your timezone setting is different from your operating system’s current one…”
The following error message may occur if the operating system’s DST rules and DWA Forms DST rules are not in synch.
“Your timezone setting is different from your operating system’s current one. You can change your timezone setting by going to the Calendar section in the Preferences dialog.”
This error is an intended warning so that users are aware there is a mismatch between the OS DST rules and the Forms DST rules.
Note: The error may also occur in cases where the client OS and Forms have both been updated. In this case, have the user reselect their time zone setting in DWA under Tools > Preferences > Calendar.
Thanks for the response guys. I did install the forms6.nsf file provided by IBM on our server and replicated it to all the Domino servers.
I’ve spent some more time on it and it only happens on PC’s that have either KB931836 or KB928388 installed. PC’s with no time zone update are fine. The servers all have KB931836 installed.
In the standard Domino client with either of the KB’s installed, I have two different options for Mexico City, Monterry time. One says old and the other says new. My XP OS has the same options, so Notes is obviously pulling that data from the OS.
DWA doesn’t have two different choices for Mexico City, Monterry, just one. Is it just getting it’s timezone info from that forms6.nsf file?
We were able to figure out the problem. The forms6.nsf database that we downloaded from IBM seemed to become corrupt as it replicated throughout our system. Manually replacing the file on each server fixed the problem.