C&S broken depending on how you create a meeting

We have several (Australian) users that create meetings in different time zones (e.g. NZ).

Depending on HOW they create those meetings, the Notes client behaves very differently…

  • If they open their calendar and click the ‘New’ action button to create a meeting, the issue does not appear
  • If they simply double-click on a time slot, the following issue appears…

A New Zealand meeting is created with a start time (1:00PM) and an end time (2:00PM).

The time zone is then switched from ‘Local’ to ‘GMT+12’ (Auckland), and the Local times are then displayed on the right hand side (11:00AM - 12:00PM).

That all works perfectly.

However, when the ‘Save & Send invitations’ action button is clicked, the meeting times are converted to 3:00PM - 4:00PM (in the NZ time zone) with the local meeting time updated to 1:00PM - 2:00PM.

It seems the time zone switcher may be causing the issue, as I performed a subsequent test…

A New Zealand meeting is created with a start time (1:00PM) and an end time (2:00PM).

The time zone is then switched from ‘Local’ to ‘GMT+12’ (Auckland), and the Local times are then displayed on the right hand side (11:00AM - 12:00PM).

The meeting times are then changed to something else and then RE-SELECTED to make them the original 1:00PM and 2:00PM values

When the ‘Save & Send invitations’ action button is clicked, the meeting times remain exactly as they should be.

Is this the expected behaviour?

Must users select the start/end times AFTER selecting the time zone to ensure the facility works properly?

Thanks so much for any/all feedback!

Subject: Thanks NG

Please feel free to contact me regarding your license requirements… https://www.linkedin.com/in/tsboyd/ https://www.linkedin.com/in/tsboyd/

Subject: Yep… it was the NOTES.INI settings

Thanks Ng… I should’ve known!

I thought that those settings would’ve resulted in the observed issue irrespective of the method with which the calendar entry was created.

What got me was the fact that it would work fine one way but not the other.

I removed the following parameters from my NOTES.INI file…

Timezone=-10
DSTLAW=10,1,1,4,1,1
DST=1

… and the issue disappeared.

Funnily enough, however, all of those settings re-appeared in my NOTES.INI after re-starting the Notes client.

There are no policy settings that establish those parameters, so I’m a little confused.

Even though the settings have re-appeared, the issue no longer presents itself… strange!!!

Cheers!

Subject: windows?

Not sure if those ini are used anymore. I had this issue in the past and found out the pc(s) where not patched of when the dst started and ended.

use the windows command w32tm /tz Windows 10 Tip: Where to Check and Set Time Zone on My Computer - NEXTOFWINDOWS.COM https://www.nextofwindows.com/windows-10-tip-where-to-check-and-set-time-zone-on-my-computer

Subject: RE: Yep… it was the NOTES.INI settings

G’Day Terry

Glad I could help.

I have not had any issue with Day Light Saving with Dom. since I was in Sydney for the 2K Olympics, but I wrote a lot of C API code around DST 2001-5 so when I read your issue DST just jumped into my head.

Have I now earned enough Kudos for you to sell me a license for Dom. X so I can test my “dom. extension manager addin” ???

Thanks

Subject: RE: C&S broken depending on how you create a meeting

G’Day Terry

Has this only stated happening recently ???

What are the values for these 2 x .ini setting on clients & servers ???

Timezone=
DSTLAW=

When I read you issue all I could think of was DST … :slight_smile:

HTH

NG