Forum Discussion
vincent_oliviers
May 20, 2020Copper Contributor
We couldn't schedule the meeting. Please try again later
Hi,
One of my coworkers keeps getting the following error when trying to schedule a Teams meeting in outlook: "We couldn't schedule the meeting. Please try again later."
I'm aware there are a lot of posts about this allready, but none of them gave me a solution for my problem.
He's signed in to the same account in teams as his office account selected in the outlook settings.
Anyone have an idea on how to fix this?
Thanks in advance!
I have solved the issue by the following steps
- Turned of the teams add on
- Restart outlook
- Turn on the teams add on
- Restart outlook.
- MERIL1830Copper Contributor
Hello, I just wanted to let you know that I tried uninstalling and reinstalling MS Teams, and it appears to have resolved the issue for me.
- adsouza1979Copper ContributorGo to Profile icon (the top right circle) or the ... menu
Go to check for updates
Wait for update
When it gives you the thumbs up for updates successful
Edit meeting if saved on the calendar
delete the location
set the slider once again and it the meeting will prompt you for "Send Update"
Wait for it ... and then boom! the meeting will give its link ... It solved my problem ... if it doesnt then go through the uninstall process - LeeCrossfuzeCopper Contributor
vincent_oliviers
This just worked for me for someone having this issue:
close OutlookTeams > Settings > Turn off the run in the background/run after closing teams
Logout Teams then close the login window
Login to Teams
Open Outlook
Scheduling Teams meetings in Outlook works without the error now
- -Tops-9017351Copper Contributor
1. Quit Microsoft Teams.
2. Cut and paste the following location into File Explorer:
%AppData%\Microsoft\Teams
3. Delete contents of the entire folder.
4. Restart Microsoft Teams.
5. Open Microsoft Outlook and Create a new meeting and click Teams Meeting on top
- MeleaglinCopper ContributorMine was the same, but I discovered since I have multiple calendars if I choose the one for “this computer” it works perfectly.
- Shujin_LiCopper Contributor
I also encounter such problems. If you use a proxy server, you can use the following solutions:
Add the following in Microsoft.Teams.MeetingAddin.dll.config , and then restart outlook.
<system.net>
<defaultProxy useDefaultCredentials="true"> </defaultProxy>
</system.net>
Path:C:\Users\%username%\AppData\Local\Microsoft\TeamsMeetingAddin\1.0.21161.4\x86\
- brianobrianCopper ContributorShujin_Li
Do you know if there is a way to do this with office customization tool, GPO, or anything programmatically?
Thanks!
- Damien_DassenCopper Contributor
I have solved the issue by the following steps
- Turned of the teams add on
- Restart outlook
- Turn on the teams add on
- Restart outlook.
- jen5280Copper Contributor
I tried many of the solutions with no success. I was able to narrow it down to only not working in the desktop version itself. I did notice that in 'My Calendars' I had also selected the 'United States holidays', when I unchecked it...all began working.
- SWDenverCopper Contributorthis worked for me - thank you!
- balajir87Copper ContributorIt worked!... after registering add on seems a new plugin version got loaded with Setting option while scheduling the meeting. Thank you @damien
- PaladuguCopper ContributorI just restarted my outlook and never got this popup again 🙂
- Audrey LinCopper ContributorWe encountered the same error msg in Outlook on desktop. The error went away after we whitelisted this address "api.scheduler.teams.microsoft.com" in our firewall.
- MarkMessingerCopper Contributor
Still no resolution to this problem?
Like others in this thread, the very un-informative error "We couldn't schedule the meeting. Please try again later." remains, despite installing Teams again.
- Deleted
Please make sure that you’ve signed into Outlook and Teams with the same account. And you go to Teams admin center to check if the required options are selected:
In addition, you can also ask the 2 users to repair the Office 365 suite to check if the issue persists.
- ChrisBedfordCopper Contributor
OK, soooo... something I must have missed in the literature (ha ha who has time for instruction manuals, right?) is that it WONT'T WORK IF YOU ARE NOT ON AN EXCHANGE SERVER.
So much time wasted. Why does Microsoft still, FORTY YEARS AFTER DOS 1.0, write cryptic, unhelpful error messages?