May 06 2021 06:01 PM - edited May 09 2021 06:32 PM
I have been trying to create a Teams Live Event for 2 days now on multiple machines (Windows & Mac) and keep running into the same error.
When trying to create a Live Event after 12pm, with the finish time after this time, for example, 12:30pm - 1:30pm, I consistently get the error
May 09 2021 07:54 PM
May 09 2021 08:44 PM
Hi @Nick-D ,
My company is having the same issue in Australia but only when using the local client on Windows. When using MS Teams from the browser we do not have this issue. Have you had any luck resolving this?
Cheers.
May 09 2021 09:05 PM
May 12 2021 04:39 PM
UPDATE: Currently all live events entered after 12pm appear to create successfully but on closer inspection the times change from pm to am. So scheduling a live event for 6pm - 7pm actually creates an event for 6am - 7am.
The workaround using the web app is still the only solution to schedule live events after 12pm.
May 13 2021 03:16 PM - edited May 13 2021 03:17 PM
Hi @Nick-D I escalated to our internal PM, who was unable to reproduce the bug (he thinks it's related to your specific time zone), so he's reached out to the worldwide team for further assistance. Not the immediate answer you're looking for but if/when we can figure out a workaround we'll let you know.
May 13 2021 06:46 PM
May 13 2021 08:20 PM
Solution@Nick-D another work around for those that need to use the local client is to change their local PC's time settings to 24hr time. While not ideal this has been the preferred resolution for some of my users.
Jun 15 2021 12:16 AM - edited Jun 15 2021 12:23 AM
@Nick-D Try changing your app language in Teams. Go to Settings>General>Change app language to English(Australia) if you are in Australia. It should fix this issue. Cheers
Nov 04 2021 10:32 PM
I hit the same bug today - the app language change fix from Baljinderbally worked. (Am in Australia - it was set to English United Kingdom)
May 13 2021 08:20 PM
Solution@Nick-D another work around for those that need to use the local client is to change their local PC's time settings to 24hr time. While not ideal this has been the preferred resolution for some of my users.