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: Oldest
  1. Anonymous
    2015-06-23T21:22:26+00:00

    Enclosed a meeting. Created on an iPhone. When sync with Exchange the appointment is set with a timezone set to Cheturnal. I have a Macbook Air with Yosemite 10.10.3. Timezone is set to Amsterdam and my client is Microsoft Outlook 15.11.

    BEGIN:VCALENDAR

    VERSION:2.0

    PRODID:-//Microsoft Corporation//Outlook for Mac MIMEDIR//EN

    METHOD:PUBLISH

    BEGIN:VTIMEZONE

    TZID:Chetumal

    X-ENTOURAGE-TZID:117

    BEGIN:STANDARD

    TZOFFSETFROM:-0500

    TZOFFSETTO:-0500

    DTSTART:16010101T000000

    END:STANDARD

    END:VTIMEZONE

    BEGIN:VEVENT

    UID:BDD1E12E69D6403CAC8C98FC0CE02BF10

    X-ENTOURAGE_UUID:43385FFE-1740-4D70-B65F-73D5DC3C2EE3

    DTSTAMP:20150623T181046Z

    DTSTART;TZID=Chetumal:20150624T013000

    DTEND;TZID=Chetumal:20150624T024500

    LAST-MODIFIED:20150623T181150Z

    SUMMARY:Bas bellen 

    DESCRIPTION: \n

    LOCATION:Anywhere

    ORGANIZER:MAILTO:XXX

    SEQUENCE:0

    X-MICROSOFT-CDO-BUSYSTATUS:BUSY

    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE

    X-MICROSOFT-DISALLOW-COUNTER:FALSE

    X-MICROSOFT-CDO-INSTTYPE:0

    BEGIN:VALARM

    ACTION:DISPLAY

    DESCRIPTION:REMINDER

    TRIGGER;RELATED=START:-PT00H00M00S

    END:VALARM

    END:VEVENT

    END:VCALENDAR

    Tom,

    Does the meeting still show up in the correct place in the Mac Outlook calendar (just with the "Chetumal" time zone name)?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-06-23T21:41:58+00:00

    When sync with Exchange it is displayed correct in the calendar. When opening the item it shows the timezone Chetumal. If i change the timezone to Amsterdam, then the time is adjusted to the timezone Chetumal. After this, i need to correct the time.

    I figured out that this only occurs when i create an item on an iOS device. Changing an item on iOS will not affect the timezone. So, Adding works not correct, changing is working correct. 

    I also checked the iOS option 'Time Zone Override'. Switching it on or off has no effect, new items are always created with the timezone on and set to Chetumal.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-06-24T16:17:42+00:00

    Thank you for the additional details.  I believe we've found the problem. This only happens with certain time zones. We are working on a fix now.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-06-29T19:18:08+00:00

    We have verified the fix for the "Chetumal" problem internally, and it should be publicly available in the next Outlook for Mac update.

    Was this answer helpful?

    0 comments No comments