SOLVED

We couldn't schedule the meeting. Please try again later

%3CLINGO-SUB%20id%3D%22lingo-sub-1405465%22%20slang%3D%22en-US%22%3EWe%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1405465%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%26nbsp%3B%3CBR%20%2F%3EOne%20of%20my%20coworkers%20keeps%20getting%20the%20following%20error%20when%20trying%20to%20schedule%20a%20Teams%20meeting%20in%20outlook%3A%20%22%3CSPAN%3EWe%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later.%22%3CBR%20%2F%3EI'm%20aware%20there%20are%20a%20lot%20of%20posts%20about%20this%20allready%2C%20but%20none%20of%20them%20gave%20me%20a%20solution%20for%20my%20problem.%26nbsp%3B%3CBR%20%2F%3EHe's%20signed%20in%20to%20the%20same%20account%20in%20teams%20as%20his%20office%20account%20selected%20in%20the%20outlook%20settings.%26nbsp%3B%3CBR%20%2F%3EAnyone%20have%20an%20idea%20on%20how%20to%20fix%20this%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20in%20advance!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1405465%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1413338%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1413338%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F674132%22%20target%3D%22_blank%22%3E%40vincent_oliviers%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20suggest%20to%20isolate%20further%20the%20issue%20by%20accessing%20the%20web%20counter-part%20by%20then%20you'll%20be%20able%20to%20figure%20it%20out%20if%20the%20issue%20reside%20on%20profile-level%20or%20desktop-level.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3ECreate%20meetings%20in%20Teams%20web%3CUL%3E%3CLI%3ETeams.microsoft.com%20%26gt%3B%20Calendar%20Icon%20%26gt%3B%20create%20a%20meeting%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3CLI%3ECreate%20meetings%20in%20Outlook%20on%20the%20web(formerly%20OWA)%3CUL%3E%3CLI%3Eoutlook.office365.com%26gt%3B%20Calendar%20Icon%20%26gt%3B%20create%20a%20meeting%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EPolite%20as%20usual%2C%3C%2FP%3E%3CP%3EBFN%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E----------------------------------------------------------------------------------------------------%3C%2FP%3E%3CP%3ENote%3A%20I%20do%20this%20on%20my%20free%20time%20to%20help%20foster%20the%20cloud%20community.%20Please%20also%20mark%20my%20response%20accordingly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1889299%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1889299%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F674132%22%20target%3D%22_blank%22%3E%40vincent_oliviers%3C%2FA%3E%26nbsp%3B%20have%20you%20find%20the%20way%20to%20fix%20it%2C%2C%20cause%20problem%20is%20happen%20to%20me%20too.%20thx.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1927688%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1927688%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F674132%22%20target%3D%22_blank%22%3E%40vincent_oliviers%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20fix%20Outlook's%20Calendar's%20new%20MS%20Teams%20meeting%20message%2C%20%22we%20couldn't%20schedule%20the%20meeting%22%3C%2FP%3E%3CP%3E1.%20Login%20as%20the%20user%20%26amp%3B%20do%20all%20the%20follower%20AS%20THE%20USER%3C%2FP%3E%3CP%3E2.%20Kill%2FQuit%20Outlook.%26nbsp%3B%20Kill%2FQuit%20MS%20Teams.%3CBR%20%2F%3E3.%20Again%20install%20MS%20Teams%20(there%20is%20no%20need%20to%20uninstall%20first)%20via%20MS%20website%3A%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fmicrosoft-teams%2Fdownload-app%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fmicrosoft-teams%2Fdownload-app%3C%2FA%3E%3CBR%20%2F%3E4.%20Launch%20Teams%2C%20at%20top-right%20click%20the%20MS%20Teams%20avatar%20%26gt%3B%20check%20for%20updates%20%26gt%3B%20..wait%20almost%202%20minutes%20and%20at%20top%20center%20of%20Teams%20screen%20it%20likely%20will%20state%2C%20%22We've%20updated%20the%20app.%20Please%20refresh%20now%22%20at%20which%20time%20please%20click%20that%20message%20to%20relaunch%20Teams.%3CBR%20%2F%3E5.%20After%20Teams%20FULLY%20opens%20up%20(which%20usually%20takes%2015%20seconds%20after%20the%20Teams%20app%20window%20opens)%2C%20then%20launch%20Outlook.%3CBR%20%2F%3E6.%20Wait%20about%2030%20seconds%20and%20go%20to%20the%20Calendar%20and%20then%20the%20Teams%20icon%20should%20be%20present%20%26amp%3B%20should%20function%20properly%20again.%3CBR%20%2F%3EJohn%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1935851%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1935851%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F880202%22%20target%3D%22_blank%22%3E%40johnneu%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3ESadly%2C%20that%20has%20not%20fixed%20the%20problem.%3CBR%20%2F%3EThe%20button%20is%20available%2C%20but%20the%20error%20%22We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%22%20still%20appears%20when%20clicking%20the%20teams%20meeting%20button%20%3A%5C%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1942417%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1942417%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F880202%22%20target%3D%22_blank%22%3E%40johnneu%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Edidn't%20work%20for%20me%20-%20still%20get%20same%20%22we%20couldn't%20schedule%20the%20meeting.%20try%20again%20later'%20nonsense%20-%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2150779%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2150779%22%20slang%3D%22en-US%22%3E%3CP%3EStill%20no%20resolution%20to%20this%20problem%3F%3C%2FP%3E%3CP%3ELike%20others%20in%20this%20thread%2C%20the%20very%20un-informative%20error%20%22We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later.%22%20remains%2C%20despite%20installing%20Teams%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2177440%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2177440%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972812%22%20target%3D%22_blank%22%3E%40MarkMessinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22%22%3EPlease%20make%20sure%20that%20you%E2%80%99ve%20signed%20into%20Outlook%20and%20Teams%20with%20the%20same%20account.%20And%20you%20go%20to%20Teams%20admin%20center%20to%20check%20if%20the%20required%20options%20are%20selected%3A%3C%2FP%3E%0A%3CDIV%20id%3D%22tinyMceEditorNkas0512_0%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CDIV%20id%3D%22tinyMceEditorNkas0512_1%22%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams.png%22%20style%3D%22width%3A%20433px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259655iFF9A1900D13F1AD8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teams.png%22%20alt%3D%22Teams.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%20class%3D%22%22%3EIn%20addition%2C%20you%20can%20also%20ask%20the%202%20users%20to%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Frepair-an-office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%20repair%20the%20Office%20365%20suite%3C%2FA%3E%20to%20check%20if%20the%20issue%20persists.%3C%2FP%3E%0A%3CP%20class%3D%22%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2181890%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2181890%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F622648%22%20target%3D%22_blank%22%3E%40BDBLUEBYRD0%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20version%20of%20Office%20are%20they%20using%3F%26nbsp%3B%3CBR%20%2F%3EOur%20employees%20are%20on%20Office%202016%20as%20a%20local%20PC%20install%20and%20also%20Terminal%20Server%20installations%20-%20both%20work.%3CBR%20%2F%3E%3CBR%20%2F%3EAlso%2C%20for%20testing%2C%20have%20the%20user%20log%20on%20via%20the%20web%20to%20Outlook.com%20as%20their%20Active%20Directory%20user%20ID%20and%20primary%20domain%20(i.e.%20ficticious%20bgates%40Microsoft.com).%26nbsp%3B%20Then%20have%20them%20go%20to%20the%20web's%20Calendar%20and%20try%20scheduling%20a%20%22New%20Event%22%20a%20Teams%20there%20(the%20%22Teams%22%20slider%20is%20located%20the%20center%20of%20the%20popup).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20us%20know%20how%20it%20goes.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2182410%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2182410%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%40Deleted%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972812%22%20target%3D%22_blank%22%3E%40MarkMessinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3EPlease%20make%20sure%20that%20you%E2%80%99ve%20signed%20into%20Outlook%20and%20Teams%20with%20the%20same%20account.%20And%20you%20go%20to%20Teams%20admin%20center%20to%20check%20if%20the%20required%20options%20are%20selected%3A%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Teams.png%22%20style%3D%22width%3A%20433px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F259655iFF9A1900D13F1AD8%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Teams.png%22%20alt%3D%22Teams.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22%22%3EIn%20addition%2C%20you%20can%20also%20ask%20the%202%20users%20to%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Frepair-an-office-application-7821d4b6-7c1d-4205-aa0e-a6b40c5bb88b%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Erepair%20the%20Office%20365%20suite%3C%2FA%3E%20to%20check%20if%20the%20issue%20persists.%3C%2FP%3E%3CP%20class%3D%22%22%3E%26nbsp%3B%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3EMine%20is%20a%20personal%20account.%20It%20appears%20I%20have%20no%20access%20to%20the%20Teams%20Administration%20Center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20Outlook%20account%20configured%20on%20the%20Outlook%20(desktop)%20application%20is%20an%20outlook.com%20account.%20It's%20the%20same%20account%20into%20which%20I%20log%20in%2C%20to%20access%20MS%20Teams.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20repaired%20Office%20365%3B%20not%20the%20%22quick%20repair%2C%22%20but%20the%20full%20repair.%20However%2C%20following%20the%20repair%20I%20find%20the%20problem%20still%20exists.%3C%2FP%3E%3CDIV%20class%3D%22ms-editor-squiggler%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2182976%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2182976%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972812%22%20target%3D%22_blank%22%3E%40MarkMessinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAhh%2C%20you%20are%20using%20a%20personal%20account...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%20thing%2C%20if%20the%20email%20used%20to%20sign%20in%20to%20%3CSTRONG%3ETeams%3C%2FSTRONG%3E%20is%20%3CSTRONG%3Enot%3C%2FSTRONG%3E%20a%20%3CSTRONG%3EMICROSOFT%3C%2FSTRONG%3E%26nbsp%3Baccount%20(%40hotmail%2C%20%40outlook%2C%20%40live%2C%20or%20%40%20a%20paid-subscription's%20email%20address)%2C%20then%20given%20the%20tests%20I%20just%20ran%2C%20it%20will%20not%20allow%20you%20to%20use%20Teams%20to%20schedule%2C%20nor%20to%20email.%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EFor%20instance%2C%20in%20my%20testing%2C%20I%20have%20an%20MS%20Teams%20account%20that%20logs%20in%20with%20an%20%40gmail.com%20email%20address.%26nbsp%3B%20I%20even%20have%20that%20%40gmail%20account%20invited%20as%20a%20Teams%20guest%20into%20my%20corporate%20account.%26nbsp%3B%20When%20I%20logon%20to%20Outlook.com%20web%20page%20with%20that%20%40gmail%20address%2C%20then%20any%20calendar%20item%20I%20set%20and%20any%20email%20I%20send%20via%20the%20web%20page%20are%20not%20received%20by%20the%20recipient%2C%20nor%20do%20I%20get%20an%20error%20message%20from%20MS%20in%20the%20web%20page's%20inbox%20(although%20the%20sent%20folder%20shows%20the%20items%20as%20sent%2C%20and%20the%20calendar%20appointment%20shows%20on%20the%20web%20page).%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20at%20this%20time%2C%20if%20your%20Teams%20account%20a%20%3CSTRONG%3Enon-paid%20subscription%3C%2FSTRONG%3E%20and%20does%20%3CSTRONG%3Enot%20use%20a%20Microsoft%20account%3C%2FSTRONG%3E%20like%20%40hotmail%2C%20%40outlook%2C%20%40live%20%2C%20then%20my%20tests%20currently%20show%20that%20you%20will%20be%20unable%20to%20schedule%20meetings%20via%20MS%20Teams%20or%20via%20the%20web%20or%20desktop%20apps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20%3CSTRONG%3Eare%20using%20a%20%22Teams%20Free%20(non-paid%20subscription)%22%20with%20a%20personal%20Microsoft%20account%3C%2FSTRONG%3E%26nbsp%3B(%40hotmail.com%2C%20%40outlook.com%2C%20%40live.com)%20to%20sign%20in%20to%20Teams%2C%26nbsp%3Bthen%20you%20can%20only%20schedule%20via%20the%20web%20page%20(outlook.com%20or%20hotmail.com)%20and%20it%20does%20so%20using%20%3CSTRONG%3ESkype.%26nbsp%3B%3C%2FSTRONG%3EThis%20means%20your%20corporate%20%3CSTRONG%3Einvitees%20will%20have%20to%20join%20the%20meeting%20with%20Skype.%26nbsp%3B%3C%2FSTRONG%3E%20I'll%20cover%20the%20%22easy%22%20method%20for%20invitees%20to%20join%20in%20a%20moment.%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3ESo%2C%20as%20a%20test%2C%20I%20used%20my%20personal%20Hotmail%20account%20and%20the%20MS%20Teams%20app%20lacked%20a%20calendar%20option%20altogether.%26nbsp%3B%20However%2C%26nbsp%3B%20my%20Hotmail.com%20(same%20as%20outlook.com%20%26amp%3B%20live.com)%20%3CSTRONG%3Eweb%20page%3C%2FSTRONG%3E%26nbsp%3Blogon's%20Calendar%20did%20allow%20me%20to%20properly%20send%20an%20invite%20to%20my%20corporate%20account%20as%20a%20%3CSTRONG%3ESkype%3C%2FSTRONG%3E%20meeting.%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-60px%22%3EI%20did%20this%20via%20the%20Hotmail%20web%20page%20at%26nbsp%3B%3CSPAN%3E%3CSTRONG%3Etop%20left%3C%2FSTRONG%3E%20clicking%20the%20%3CSTRONG%3Egrid%3C%2FSTRONG%3E%20(menu)%20%26gt%3B%20%3CSTRONG%3ECALENDAR%3C%2FSTRONG%3E%20%26gt%3B%20%3CSTRONG%3ENEW%20EVENT%3C%2FSTRONG%3E%20%26gt%3B%20in%20popup%20bottom%20right%20click%26nbsp%3B%3CSTRONG%3EMORE%20OPTIONS%3C%2FSTRONG%3E%26nbsp%3B%26gt%3B%20at%20center%20of%20that%20popup%20click%26nbsp%3B%3CSTRONG%3ESKYPE%20MEETING%3C%2FSTRONG%3E%26nbsp%3B(paid%20Office%20365%20subscribers%20instead%20see%20%22Teams%20Meeting%22).%3C%2FSPAN%3E%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EI%20was%20able%20to%20%3CSTRONG%3Estart%20the%20meeting%3C%2FSTRONG%3E%20with%20my%20Hotmail%20%3CSTRONG%3Eweb%3C%2FSTRONG%3E%20page's%20Calendar%20appointment.%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EIf%20the%20invitee%20has%20the%20paid%20subscription%20of%20Skype%20for%20Business%20then%20it%20should%20go%20smoothly%20for%20them.%26nbsp%3B%3C%2FP%3E%3CP%20class%3D%22lia-indent-padding-left-30px%22%3EOtherwise%2C%20when%20they%20click%20their%20calendar%20to%20join%20the%20meeting%2C%20then%20a%20webpage%20launches.%26nbsp%3B%20To%20make%20things%20easy%2C%20they%20can%20just%20join%20as%20a%20GUEST%20and%20will%20not%20have%20to%20install%20anything%20(it%20initiates%20as%20just%20a%20text%20chat%2C%20so%20at%20top%20right%20you%20can%20click%20the%20Camera%20or%20Microphone%20to%20start%20a%20%22call%22%20and%20then%20the%20other%20participants%20need%20to%20click%20at%20top%20right%20%22join%20call%22).%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhewh...%20That%20was%20a%20lot%20of%20testing.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EJohn!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2182997%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2182997%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3EWhewh...%20That%20was%20a%20lot%20of%20testing.%3CP%3E%3CBR%20%2F%3EJohn!%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F880202%22%20target%3D%22_blank%22%3E%40johnneu%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20that%20does%20sound%20like%20a%20great%20deal%20of%20testing.%20Your%20reply%20correctly%20anticipated%20the%20possibility%20I%20am%20using%20an%20outlook.com%20account.%20Thanks%20for%20that.%20Although%20I%20don't%20understand%20why%20this%20difference%20in%20Teams%20is%20necessary%2C%20now%20that%20you've%20explained%20the%20limitations%2C%20I%20can%20worth%20with%20those.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20greatly%20appreciate%20the%20time%20you%20spent%20on%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20I'm%20off%20to%20remove%20the%20useless%20Teams%20Meeting%20tool%2C%20from%20my%20Outlook%20(desktop)%20toolbar.%20.%20.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2193536%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2193536%22%20slang%3D%22en-US%22%3EWe%20encountered%20the%20same%20error%20msg%20in%20Outlook%20on%20desktop.%20The%20error%20went%20away%20after%20we%20whitelisted%20this%20address%20%22api.scheduler.teams.microsoft.com%22%20in%20our%20firewall.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2196967%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2196967%22%20slang%3D%22en-US%22%3EThe%20method%20outlined%20by%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F880202%22%20target%3D%22_blank%22%3E%40johnneu%3C%2FA%3E%20worked%20for%20my%20situation.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2282334%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2282334%22%20slang%3D%22en-US%22%3EI%20just%20restarted%20my%20outlook%20and%20never%20got%20this%20popup%20again%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2288993%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2288993%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E%26gt%3B%20Please%20make%20sure%20that%20you%E2%80%99ve%20signed%20into%20Outlook%20and%20Teams%20with%20the%20same%20account.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHeh...%20well%20that%20made%20the%20error%20message%20come%20up%20%3CEM%3Einstantly%3C%2FEM%3E%20instead%20of%20after%20a%205-10%20second%20delay%20%3Apouting_face%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%26gt%3B%26nbsp%3BAnd%20you%20go%20to%20Teams%20admin%20center%20to%20check%20if%20the%20required%20options%20are%20selected%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20no%20idea%20how%20to%20go%20into%20the%20%22admin%20centre%22%20of%20which%20you%20speak...%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAlso%20someone%20in%20an%20earlier%20post%20mentioned%20going%20to%20%22Teams%20Avatar%20at%20top%20right%22%20and%20checking%20settings%20there%20-%20also%20no%20idea%20what%20that%20refers%20to.%20In%20fact%20I%20find%20nowhere%20to%20make%20any%20meaningful%20administrative%20changes%20to%20Teams.%20What%20am%20I%20missing%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20am%20seeing%20this%20error%20message%20on%20a%20single%20PC%20in%20a%20company%20that%20has%20successfully%20been%20using%20Teams%20since%20shortly%20after%20COVID%20lockdown%20started%20-%20probably%2030%20people%20working%20just%20fine%2C%20just%20this%20one%20user%20having%20the%20issue.%20And%20I%20just%20spent%20an%20exciting%20weekend%20wiping%20the%20entire%20PC%20and%20reinstalling%2C%20only%20to%20get%20the%20exact%20same%20error.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDoes%20it%20require%20a%20particular%20version%20of%20Windows%3F%20This%20PC%20is%20running%20Windows%20Home%20Single%20Language%20whereas%20the%20rest%20probably%20have%20Pro%20or%20maybe%20the%20regular%20Home%20(Home%20Premium%3F)%20not%20SL%20-%20not%20verified%2C%20no%20way%20to%20do%20that%20in%20anything%20less%20than%20a%20long%2C%20long%20time.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2293966%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2293966%22%20slang%3D%22en-US%22%3E%3CP%3EOK%2C%20soooo...%20something%20I%20must%20have%20missed%20in%20the%20literature%20(ha%20ha%20who%20has%20time%20for%20instruction%20manuals%2C%20right%3F)%20is%20that%20it%20WONT'T%20WORK%20IF%20YOU%20ARE%20NOT%20ON%20AN%20EXCHANGE%20SERVER.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20much%20time%20wasted.%20Why%20does%20Microsoft%20still%2C%20FORTY%20YEARS%20AFTER%20DOS%201.0%2C%20write%20cryptic%2C%20unhelpful%20error%20messages%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2294019%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2294019%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1036372%22%20target%3D%22_blank%22%3E%40ChrisBedford%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20I%20suppose%20Outlook.com%20accounts%20aren't%20%22the%20correct%20kind%20of%20Exchange%20Server.%22%20My%20primary%20account%20is%20an%20Outlook.com%20account.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%222021-04-26%2011_09_33-Inbox%20-%20markmessinger%40outlook.com%20-%20Outlook.jpg%22%20style%3D%22width%3A%20864px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F275625iF3039BD309A56807%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%222021-04-26%2011_09_33-Inbox%20-%20markmessinger%40outlook.com%20-%20Outlook.jpg%22%20alt%3D%222021-04-26%2011_09_33-Inbox%20-%20markmessinger%40outlook.com%20-%20Outlook.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2308163%22%20slang%3D%22en-US%22%3ERe%3A%20We%20couldn't%20schedule%20the%20meeting.%20Please%20try%20again%20later%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2308163%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F972812%22%20target%3D%22_blank%22%3E%40MarkMessinger%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYeah%20I%20wouldn't%20know%20those%20details%20%3Asquinting_face_with_tongue%3A%20but%20I%20would%20imagine%20there%20is%20only%20one%20kind.%20Maybe%3F%3C%2FP%3E%3CP%3EI%20do%20know%20that%20the%20%22correct%22%20type%2C%20when%20you%20right-click%20the%20mailbox%20folder%20in%20the%20navigation%20pane%2C%20and%20select%20%22Properties%22%2C%20has%204%20tabs%2C%20the%20rightmost%20of%20which%20is%20%22Synchronisation%22%20(%3F%20something%20like%20that).%20When%20you%20select%20it%2C%20it%20shows%20how%20many%20mail%20items%20on%20the%20server%20and%20in%20the%20local%20copy.%20If%20you%20can%20see%20this%20information%20it%20seems%20to%20me%20you%20should%20be%20able%20to%20use%20the%20Teams%20Add-in%2C%20because%20%3CSTRONG%3E%3CEM%3Ewhy%20not%3C%2FEM%3E%3C%2FSTRONG%3E.%20That's%20all%20I've%20got%20%3A(%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

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!

18 Replies

@vincent_oliviers 

 

I'd suggest to isolate further the issue by accessing the web counter-part by then you'll be able to figure it out if the issue reside on profile-level or desktop-level.

 

  • Create meetings in Teams web
    • Teams.microsoft.com > Calendar Icon > create a meeting
  • Create meetings in Outlook on the web(formerly OWA)
    • outlook.office365.com> Calendar Icon > create a meeting

Polite as usual,

BFN

 

 

----------------------------------------------------------------------------------------------------

Note: I do this on my free time to help foster the cloud community. Please also mark my response accordingly.

@vincent_oliviers  have you find the way to fix it,, cause problem is happen to me too. thx.

best response confirmed by ThereseSolimeno (Microsoft)
Solution

@vincent_oliviers 

To fix Outlook's Calendar's new MS Teams meeting message, "we couldn't schedule the meeting"

1. Login as the user & do all the follower AS THE USER

2. Kill/Quit Outlook.  Kill/Quit MS Teams.
3. Again install MS Teams (there is no need to uninstall first) via MS website:          https://www.microsoft.com/en-us/microsoft-365/microsoft-teams/download-app
4. Launch Teams, at top-right click the MS Teams avatar > check for updates > ..wait almost 2 minutes and at top center of Teams screen it likely will state, "We've updated the app. Please refresh now" at which time please click that message to relaunch Teams.
5. After Teams FULLY opens up (which usually takes 15 seconds after the Teams app window opens), then launch Outlook.
6. Wait about 30 seconds and go to the Calendar and then the Teams icon should be present & should function properly again.
John

@johnneu 
Sadly, that has not fixed the problem.
The button is available, but the error "We couldn't schedule the meeting. Please try again later" still appears when clicking the teams meeting button :\

@johnneu 

 

didn't work for me - still get same "we couldn't schedule the meeting. try again later' nonsense - 

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.

@MarkMessinger 

 

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:

 
 

Teams.png

 

In addition, you can also ask the 2 users to repair the Office 365 suite to check if the issue persists.

 

@BDBLUEBYRD0 

What version of Office are they using? 
Our employees are on Office 2016 as a local PC install and also Terminal Server installations - both work.

Also, for testing, have the user log on via the web to Outlook.com as their Active Directory user ID and primary domain (i.e. ficticious bgates@Microsoft.com).  Then have them go to the web's Calendar and try scheduling a "New Event" a Teams there (the "Teams" slider is located the center of the popup).

 

Let us know how it goes.


@Deleted wrote:

@MarkMessinger 

 

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:

 
 

Teams.png

 

In addition, you can also ask the 2 users to repair the Office 365 suite to check if the issue persists.

 


Mine is a personal account. It appears I have no access to the Teams Administration Center.

 

My Outlook account configured on the Outlook (desktop) application is an outlook.com account. It's the same account into which I log in, to access MS Teams.

 

I repaired Office 365; not the "quick repair," but the full repair. However, following the repair I find the problem still exists.

 

@MarkMessinger 

Ahh, you are using a personal account...

 

First thing, if the email used to sign in to Teams is not a MICROSOFT account (@hotmail, @outlook, @live, or @ a paid-subscription's email address), then given the tests I just ran, it will not allow you to use Teams to schedule, nor to email.   

For instance, in my testing, I have an MS Teams account that logs in with an @gmail.com email address.  I even have that @gmail account invited as a Teams guest into my corporate account.  When I logon to Outlook.com web page with that @gmail address, then any calendar item I set and any email I send via the web page are not received by the recipient, nor do I get an error message from MS in the web page's inbox (although the sent folder shows the items as sent, and the calendar appointment shows on the web page).

 

So, at this time, if your Teams account a non-paid subscription and does not use a Microsoft account like @hotmail, @outlook, @live , then my tests currently show that you will be unable to schedule meetings via MS Teams or via the web or desktop apps.

 

If you are using a "Teams Free (non-paid subscription)" with a personal Microsoft account (@hotmail.com, @outlook.com, @live.com) to sign in to Teams, then you can only schedule via the web page (outlook.com or hotmail.com) and it does so using Skype. This means your corporate invitees will have to join the meeting with Skype.  I'll cover the "easy" method for invitees to join in a moment.

So, as a test, I used my personal Hotmail account and the MS Teams app lacked a calendar option altogether.  However,  my Hotmail.com (same as outlook.com & live.com) web page logon's Calendar did allow me to properly send an invite to my corporate account as a Skype meeting.

I did this via the Hotmail web page at top left clicking the grid (menu) > CALENDAR > NEW EVENT > in popup bottom right click MORE OPTIONS > at center of that popup click SKYPE MEETING (paid Office 365 subscribers instead see "Teams Meeting").

I was able to start the meeting with my Hotmail web page's Calendar appointment.

If the invitee has the paid subscription of Skype for Business then it should go smoothly for them. 

Otherwise, when they click their calendar to join the meeting, then a webpage launches.  To make things easy, they can just join as a GUEST and will not have to install anything (it initiates as just a text chat, so at top right you can click the Camera or Microphone to start a "call" and then the other participants need to click at top right "join call").


Whewh... That was a lot of testing.


John!

 


Whewh... That was a lot of testing.


John!


@johnneu 

 

Yes, that does sound like a great deal of testing. Your reply correctly anticipated the possibility I am using an outlook.com account. Thanks for that. Although I don't understand why this difference in Teams is necessary, now that you've explained the limitations, I can worth with those. 

 

I greatly appreciate the time you spent on this.

 

Now I'm off to remove the useless Teams Meeting tool, from my Outlook (desktop) toolbar. . .

We 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.
The method outlined by @johnneu worked for my situation.
I just restarted my outlook and never got this popup again :)

> Please make sure that you’ve signed into Outlook and Teams with the same account.

 

Heh... well that made the error message come up instantly instead of after a 5-10 second delay :pouting_face:

 

> And you go to Teams admin center to check if the required options are selected:

 

I have no idea how to go into the "admin centre" of which you speak...?

 

Also someone in an earlier post mentioned going to "Teams Avatar at top right" and checking settings there - also no idea what that refers to. In fact I find nowhere to make any meaningful administrative changes to Teams. What am I missing?

 

I am seeing this error message on a single PC in a company that has successfully been using Teams since shortly after COVID lockdown started - probably 30 people working just fine, just this one user having the issue. And I just spent an exciting weekend wiping the entire PC and reinstalling, only to get the exact same error.

 

Does it require a particular version of Windows? This PC is running Windows Home Single Language whereas the rest probably have Pro or maybe the regular Home (Home Premium?) not SL - not verified, no way to do that in anything less than a long, long time.

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?

@ChrisBedford 

 

And I suppose Outlook.com accounts aren't "the correct kind of Exchange Server." My primary account is an Outlook.com account.

 

2021-04-26 11_09_33-Inbox - markmessinger@outlook.com - Outlook.jpg

@MarkMessinger 

Yeah I wouldn't know those details :squinting_face_with_tongue: but I would imagine there is only one kind. Maybe?

I do know that the "correct" type, when you right-click the mailbox folder in the navigation pane, and select "Properties", has 4 tabs, the rightmost of which is "Synchronisation" (? something like that). When you select it, it shows how many mail items on the server and in the local copy. If you can see this information it seems to me you should be able to use the Teams Add-in, because why not. That's all I've got :(