Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI Companion2023-10-25 07:26 AM
Hey, I've been having issue creating Zoom meeting in Outlook Calendar via the Zoom add-in.
Whenever i click on the Meeting i get a 500 Internal Server Error.
If i click on the Addon Settings, and from there create a meeting, it works.
Let me know if you have a solution for this. Thanks
Solved! Go to Solution.
2023-10-27 11:32 AM
Resolution - on the Zoom add-in (within outlook), go to "Settings" from the drop down (instead of new zoom meeting) and then sign out/sign in from the settings tab. Once you sign back in, the issue is resolved (at least with my Outlook O365/Mac). Hope that helps
2023-10-25 07:10 PM
Encountering the same problem.
2023-10-26 09:53 AM
Also having this issue. "500 internal server error" every time I try to create an invite with a Zoom link. Please help!
2023-10-26 10:16 AM
We are seeing this problem across our environment also. If you have the user sign out and sign back in it goes away. Is there an issue with the version of add-in?
2023-10-27 08:48 AM
I am also having this issue both 26 and 27/October on the west coast (USA). Outlook O365 on Mac
2023-10-27 11:32 AM
Resolution - on the Zoom add-in (within outlook), go to "Settings" from the drop down (instead of new zoom meeting) and then sign out/sign in from the settings tab. Once you sign back in, the issue is resolved (at least with my Outlook O365/Mac). Hope that helps
2023-11-09 10:55 AM
On my side after 2-3 days, the option was working without any work done on the end-user pc. Maybe it was fixed in a Office 365 update... weird.