Calendar event showing up the wrong timezone

Anonymous
2015-03-16T12:28:08+00:00

Hi there, I refer to the screenshots below. The user, Pamela, sends out a calendar invite to both Jeff and Kok Guan, specifying the correct timezone UTC +0800. However, what Jeff views this event on his Mac running on Yosemite 10.10.2 is the UTC +0000 timezone, Monrovia, Reykjavik. The time indicated is displayed 6am instead of the actual 2pm, despite showing a notification that the event will commence at 2pm on Jeff's Mac. How do i go about correcting/removing the UTC +0000, Monrovia, Reykjavik, timezone stamp. Appreciate some help with this. Thanks!

Regards

Kenny

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-05-27T18:59:07+00:00

Unfortunately, the server update won't fix existing meetings automatically.  However, users MAY be able to fix it themselves if they find the original meeting invitation (could be in Deleted Items) and re-accept the meeting(s) with the "UTC" time zones.  (Let us know if that works.)

If that doesn't work, they will have to ask the organizer to re-send the invitation.  (Organizer just has to open the meeting on his/her calendar and click "Send Update." Make sure to "Edit Series" if it is a recurring meeting.)

Was this answer helpful?

60+ people found this answer helpful.
0 comments No comments

104 additional answers

Sort by: Newest
  1. Anonymous
    2015-07-20T18:51:17+00:00

    Daniel,

    It looks like the issue here is that Lotus Notes says the meeting is in the GMT time zone, which technically does not have Daylight Savings Time, rather than "(UTC) London..." which does adjust for British Summer Time.  We're going to have to evaluate this further to see if there is a workable solution.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-07-18T07:04:13+00:00

    I double clicked the appointment in my calendar.  There was a .ics attachment in there, so I dragged that to my desktop.  I then opened it in Mac TextEdit and redacted the e-mail addresses, taking care not to change anything else.  When I open this .ics file in Outlook it displays alongside the original appointment, with the incorrect time.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-07-17T23:10:13+00:00

    Daniel, how did you produce this .ics file? It doesn't look the same as one created by dragging a meeting from the calendar to Mac desktop.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-07-16T12:18:58+00:00

    I've just experienced a similar 'timezone' related problem today.

    My timezone is set correctly in Outlook 2016 for Mac (15.11.2) - (UTC) Dublin, Edinburgh, Lisbon London and on my Mac - British Summer Time.  It's also set correctly in Office 365. (E3 edition)

    I received the appointment below for 11am to 12noon today.  It shows as 12 noon to 1pm in my calendar, so I was an hour late for my meeting. Thankfully I arrived early so the impact was minimal.  If I open the appointment in Outlook it says it's from a different timezone - (UTC) Monrovia, Reykjavik. 

    The calendar appointment originated from Lotus Notes.  When I open it in Apple Calendar it shows the correct time.  I have redacted the sender details and the other people invited.  Otherwise it's the same appointment I received.

    BEGIN:VCALENDAR

    X-LOTUS-CHARSET:UTF-8

    VERSION:2.0

    PRODID:-//Lotus Development Corporation//NONSGML Notes 8.5.3//EN_C

    METHOD:REQUEST

    BEGIN:VTIMEZONE

    TZID:GMT

    BEGIN:STANDARD

    DTSTART:19501029T020000

    TZOFFSETFROM:+0100

    TZOFFSETTO:+0000

    RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=10

    END:STANDARD

    BEGIN:DAYLIGHT

    DTSTART:19500326T020000

    TZOFFSETFROM:+0000

    TZOFFSETTO:+0100

    RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=-1SU;BYMONTH=3

    END:DAYLIGHT

    END:VTIMEZONE

    BEGIN:VEVENT

    DTSTART;TZID="GMT":20150716T110000

    DTEND;TZID="GMT":20150716T120000

    TRANSP:OPAQUE

    DTSTAMP:20150714T160527Z

    SEQUENCE:0

    ATTACH:CID:1__=0FBBF411DFCBB6808f9e8a93df938690918c0FB@

    ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN=“REDACTED”

     ;RSVP=FALSE:mailto:******@redacted.com

    ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE

     :mailto:******@brightconsult.co.uk

    ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION

     ;CN=“Redacted”;RSVP=TRUE:mailto:******@redacted.com

    ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION

     ;CN=“Redacted”;RSVP=TRUE

     :mailto:******@redacted.com

    ATTENDEE;CUTYPE=ROOM;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION

     ;CN="Room 9";RSVP=TRUE

     :mailto:Room_******@redacted.com

    CLASS:PUBLIC

    DESCRIPTION;ALTREP="CID:<FFFF__=0FBBF411DFCBB6808f9e8a93df938690918c0FB@>":

    SUMMARY:Meet with Dan Simms from Bright IT Consultancy Ltd

    LOCATION:Redated

    ORGANIZER;CN=“Redacted”;SENT-BY="mailto

     :@redacted.com":mailto:@redacted.com

    UID:8B849CA497D903DB80257E8200583010-Lotus_Notes_Generated

    X-LOTUS-BROADCAST:FALSE

    X-LOTUS-UPDATE-SEQ:1

    X-LOTUS-UPDATE-WISL:$S:1;$L:1;$B:1;$R:1;$E:1;$W:1;$O:1;$M:1;RequiredAttendees:1;INetRequiredNames:1;AltRequiredNames:1;StorageRequiredNames:1;OptionalAttendees:1;INetOptionalNames:1;AltOptionalNames:1;StorageOptionalNames:1

    X-LOTUS-NOTESVERSION:2

    X-LOTUS-NOTICETYPE:I

    X-LOTUS-APPTTYPE:3

    X-LOTUS-CHILD-UID:8B849CA497D903DB80257E8200583010

    END:VEVENT

    END:VCALENDAR

    The sender hasn't experienced any problems previously.  Equally, I haven't experienced any problems previously either.  The difference seems to be that I've started using Outlook 2016 for Mac and I believe that's where the bug is.  Any thoughts?

    Kind regards

    Dan Simms

    Bright IT Consultancy Limited

    Was this answer helpful?

    0 comments No comments