SOLVED

Error starting after latest update

%3CLINGO-SUB%20id%3D%22lingo-sub-52549%22%20slang%3D%22en-US%22%3EError%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52549%22%20slang%3D%22en-US%22%3E%3CDIV%3EStarting%20error%2C%20and%20so%20in%20a%20circle.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3Edesktop-7841bf6d-1bc3-45e5-8a9a-20d2ea7391ea%3C%2FDIV%3E%3CDIV%3EError%20code%20-%20500%3C%2FDIV%3E%3CDIV%3EFailed%20to%20reach%3A%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2F%3C%2FA%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-52549%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352717%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352717%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20teams%20was%20down%20it%20was%20a%20matter%20of%20minutes%20between%20applying%20the%20KB%20updates%20and%20it%20failing%20then%20clearing%20the%20Explorer%20cache%20and%20it%20working.%26nbsp%3B%20In%20my%20case%2C%20I%20think%20that%20was%20the%20issue%2C%20We%20do%20use%20SSO%20so%20I%20think%20my%20issue%20was%20around%20cached%20creds%20(possibly)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352702%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352702%22%20slang%3D%22en-US%22%3EYes!%20Teams%20service%20has%20been%20down%20but%20has%20started%20to%20work%20again%20%3A)%3C%2Fimg%3E%20probably%20not%20issues%20with%20the%20KB!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352691%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352691%22%20slang%3D%22en-US%22%3E%3CP%3EI%20uninstalled%20KB4487044%2C%20it%20started%20working%2C%20but%20then%20read%20other%20posts%20where%20it%20just%20started%20working%20for%20some%20people.%26nbsp%3B%20So%20perhaps%20a%20Teams%20service%20issue%3F%26nbsp%3B%20I%20reinstalled%20KB4487044%20and%20Teams%20is%20still%20working.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352687%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352687%22%20slang%3D%22en-US%22%3E%3CP%3EWas%20getting%20the%20same%20error%20after%20the%20latest%20update%202019-02%20KB4487017%20the%20only%20thing%20that%20fixed%20the%20Teams%20APP%20was%20clearing%20the%20Edge%20history.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352644%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352644%22%20slang%3D%22en-US%22%3EYes!%20Seems%20it%20starts%20to%20work%20for%20many%20right%20now!!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352643%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352643%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20the%20same%20issue%20this%20morning.%26nbsp%3B%20I%20attempted%20all%20of%20the%20recommendations%20in%20this%20post%20and%20none%20of%20them%20worked.%20I%20remembered%20that%20it%20was%20working%20prior%20to%20the%20last%20update%2C%20so%20I%20uninstalled%20Windows%20Security%20Update%20KB4487044%20and%20it%20worked.%3C%2FP%3E%3CP%3EI%20found%20that%20even%20through%20a%20browser%20I%20couldn't%20reach%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%3C%2FA%3E%20and%20Teams%20was%20working%20on%20my%20Pixel%20so%20it%20wasn't%20a%20network%20issue%20but%20local%20to%20my%20laptop.%26nbsp%3B%20This%20lead%20me%20to%20think%20about%20the%20last%20update%20recently%20installed.%3C%2FP%3E%3CP%3EGive%20it%20a%20try%2C%20hopefully%20it%20works%20and%20hopefully%20someone%20from%20MS%20is%20watching%20this%20thread%20to%20escalate%20to%20dev%20to%20have%20a%20fix%20for%20KB4487044%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352642%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352642%22%20slang%3D%22en-US%22%3E%3CP%3EVedha123%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20is%20resolved%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20that%20was%20a%20drop%20in%20Teams%20services.%26nbsp%3BEverything%20is%20fine%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352631%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352631%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20getting%20the%20same%20problem%20in%20our%20office%20-%20all%20Windows%20desktops%20are%20failing%20with%20the%20same%20issue%20but%20the%20IOS%20app%20works%20fine%20on%20mobiles.%26nbsp%3B%20If%20you%20are%20already%20logged%20in%20then%20you%20are%20OK%20but%20if%20you%20log%20out%20you%20can't%20get%20back%20in%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20looks%20like%20the%20problem%20is%20post-authentication.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352630%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352630%22%20slang%3D%22en-US%22%3EHi!%20Please%20follow%20the%20thread%20I%20posted!%20We%20try%20keep%20you%20posted%20there%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352629%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352629%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20let%20me%20know%20if%20the%20issue%20got%20resolved.%3C%2FP%3E%3CP%3EI%20am%20facing%20the%20same%20issue%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F286221%22%20target%3D%22_blank%22%3E%40XxTheGameBoxX%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EI%20have%20the%20same%20problem%20here.%20When%20I've%20trayed%20to%20open%20Teams%20web%20I've%20recived%20the%20next%20error%20message%3A%3C%2FP%3E%3CP%3E%3CEM%3EThe%20page%20cannot%20be%20displayed%20because%20an%20internal%20server%20error%20has%20occurred.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECoincidence%3F%20I%20think%20not.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20gonna%20try%20after%20one%20hour.%20Maybe%20this%20issue%20can%20resolve%20itself.%3C%2FSPAN%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352628%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352628%22%20slang%3D%22en-US%22%3ESee%20my%20earlier%20response!%20This%20is%20affecting%20not%20only%20MAC%20clients!%20Follow%20that%20that%20thread%20instead!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352626%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352626%22%20slang%3D%22en-US%22%3Eit%20seems%20so%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352625%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352625%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%20when%20launching%20Teams%20I%20get%20a%20500%20error%2C%20so%20I%20signed%20out%20of%20Teams%20and%20logged%20into%20O365%2C%20I%20see%20Teams%20icon%20there%2C%20clicked%20on%20it%20and%20got%20this%20message%20%22%3CSPAN%3EThe%20page%20cannot%20be%20displayed%20because%20an%20internal%20server%20error%20has%20occurred.%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20been%20in%20Teams%20for%20the%20last%20two%20months%20-%20I%20am%20a%20MacBook%20Pro%20user.%20After%20a%20couple%20minutes%20-%2030ish%20minutes%20I%20relaunched%20Teams%20and%20it%20is%20back%20working%20fine..wierd%3C%2FSPAN%3E%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F30677%22%20target%3D%22_blank%22%3E%40Martin%20Front%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3E%3CP%3EHi%20Alexey%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20you%20tried%20to%20restart%20your%20computer%3F%3C%2FP%3E%3CP%3EHave%20you%20tried%20to%20reinstall%20the%20software%3F%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20works%20in%20a%20browser%2C%20Internet%20Explorer%20for%20example%3F%3C%2FP%3E%3CP%3EDoes%20it%20works%20on%20your%20mobile%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBR%3C%2FP%3E%3CP%3EMartin%20Front%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352623%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352623%22%20slang%3D%22en-US%22%3ERelated%20to%3F%3F%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FTeams-Crashes-on-Startup%2Fm-p%2F352600%23M26364%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FMicrosoft-Teams%2FTeams-Crashes-on-Startup%2Fm-p%2F352600%23M26364%3C%2FA%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352622%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352622%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%20since%20today.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Elogging%20of%20clearing%20credential%20cache%20isn't%20working%20for%20me%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352616%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352616%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20tried%20every%20solution%2C%20searches%20have%20produced%2C%20with%20no%20good%20result.%20%26nbsp%3BLogging%20off%2C%20restarting%2C%20uninstalling%20all%20end%20in%20the%20same%20error.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvery%20OSX%20Teams%20user%20in%20my%20organization%20is%20having%20the%20same%20issue.%20%26nbsp%3BWe%20can%20all%20access%20through%20iOS%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352604%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352604%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20problem%20here.%20When%20I've%20trayed%20to%20open%20Teams%20web%20I've%20recived%20the%20next%20error%20message%3A%3C%2FP%3E%3CP%3E%3CEM%3EThe%20page%20cannot%20be%20displayed%20because%20an%20internal%20server%20error%20has%20occurred.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ECoincidence%3F%20I%20think%20not.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20gonna%20try%20after%20one%20hour.%20Maybe%20this%20issue%20can%20resolve%20itself.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206797%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206797%22%20slang%3D%22en-US%22%3E%3CP%3EPressing%20%22Sign%20Out%22%20on%20the%20tray%20icon%20does%20nothing%20for%20me.%20I%20am%20unsure%20of%20why.%20I%20have%20deleted%20all%20the%20credentials%20in%20Credential%20Manager%20as%20well.%3CBR%20%2F%3E%3CBR%20%2F%3EStill%20no%20resolution%20here.%20I%20really%20want%20to%20use%20the%20desktop%20app%2C%20but%20I%20can't.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206655%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206655%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20having%20the%20same%20issue%20but%20only%20when%20trying%20to%20access%20a%20guest%20tenant.%20My%20company%20tenant%20is%20perfectly%20fine%2C%20but%20anytime%20I%20try%20to%20switch%20to%20the%20guest%20it%20gets%20hung%20up.%20To%20%22fix%22%20and%20just%20use%20my%20company%20tenant%20I%20have%20to%20log%20out%20using%20the%20tray%20icon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-205842%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-205842%22%20slang%3D%22en-US%22%3E%3CP%3EHitting%20the%20same%20error...%20I%20have%20a%20personal%20account%20with%20MAM%20policies%20from%20my%20work%20account%20that%20apply%20Hello%20for%20Business%20login.%3CBR%20%2F%3E%3CBR%20%2F%3EPressing%20%22sign%20out%22%20does%20nothing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-152714%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-152714%22%20slang%3D%22en-US%22%3ERight-click%20on%20Teams%20in%20the%20Start%20bar%20and%20%22logoff%22.%20Next%20time%20your%20login%20will%20be%20asked.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-68070%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-68070%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20not%20the%20otpion%20Log%20out%20when%20i%20right%20click%20on%20the%20app%20...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-61713%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-61713%22%20slang%3D%22en-US%22%3E%3CP%3EA%20slight%20adjustment%20to%20the%20process%20outlined%20by%20Orlando%20worked%20for%20me.%20You%20have%20to%20skip%20the%20first%20small%20sign-in%20window%20(by%20closing%20it)%2C%20then%20Teams%20Desktop%20will%20continue%20to%20load%20and%20present%20you%20with%20a%20larger%20sign-in%20window.%20%26nbsp%3BFilling%20in%20my%20credentials%20here%20worked!%20%26nbsp%3B(Side%20note%3A%20I%20did%20not%20do%20a%20reinstall%20-%20this%20was%20the%20first%20time%20I%20used%20Teams).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20the%20adapted%20process%3A%3C%2FP%3E%3CP%3E1)%20Go%20to%20the%20System%20Tray%20and%20right-click%20on%20the%20Teams%20icon%3C%2FP%3E%3CP%3E2)%20Select%20Log%20Out%3C%2FP%3E%3CP%3E3)%20The%20app%20will%20go%20through%20the%20motions%20of%20logging%20off%20and%20restart%2C%20then%20ask%26nbsp%3Bfor%20your%20credentials.%20(screenshot%3A%20Desktop2.PNG)%3C%2FP%3E%3CP%3E4)%20Close%20this%20window.%20%26nbsp%3BThe%20app%20will%20continue%20to%20load%20and%20present%20you%20with%20a%20(more%20comprehensive%3F)%20sign-on%20window%20(which%20looks%20like%20it%20is%20within%20the%20app%2C%20rather%20than%20an%20%22additional%22%20window%20-%20screenshot%3A%20Desktop3.PNG)%3C%2FP%3E%3CP%3E5)%20%26nbsp%3BEntering%20my%26nbsp%3B%3CSPAN%3EO365%20credentials%20(company%20credentials)%20worked%20for%20me%20here.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-59331%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-59331%22%20slang%3D%22en-US%22%3E%3CP%3E1-%20start%20the%20Microsoft%20mac%20client%20Teams%3C%2FP%3E%3CP%3E(Obviously%20it%20locks%20to%20the%20point%20that%20we%20know%20...)%20but%20!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2-%20press%20the%20dock%20icon%20with%20the%20right%20mouse%20button.%20It%20opens%20a%20small%20context%20menu%20...%3CBR%20%2F%3E%22Disconnect%22%20with%20the%20voice.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E3-%20disconnect%20by%20clicking%20on%20the%20application%20after%20a%20few%20moments%20closes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E4-%20restarting%20the%20application%20this%20time%20the%20credential%20window%20opens.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E5-%20At%20this%20point%20you%20enter%20the%20credentials%20of%20365%20office%20...%20and%20...%20everything%20works%20great%20!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-55848%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-55848%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20similar%20problem%20with%20the%20native%20app%20on%26nbsp%3Bthe%20Mac%20side.%20I%20tried%20uninstalling%20and%20removing%20all%20Microsoft%20Teams%20app%26nbsp%3Bpreferences.%20%26nbsp%3BRestarted.%20I%20reinstalled%20the%20app.%20I%20even%20logged%20out%20of%20Office%20365%20in%20my%20other%20apps.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverytime%20I%20load%20up%20Microsoft%20Teams%20for%20Mac%20I%20get%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E---%3C%2FDIV%3E%3CDIV%3ED'oh!%20Something%20went%20wrong...%3C%2FDIV%3E%3CDIV%3ERestart%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CDIV%3Edesktop-f37dbf05-dca6-4f3e-96be-c5eaa4ede814%3C%2FDIV%3E%3CDIV%3EError%20code%20-%20500%3C%2FDIV%3E%3CDIV%3EFailed%20to%20reach%3A%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2F%3C%2FA%3E%3C%2FDIV%3E%3CDIV%3E---%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ECan't%20get%20out%20of%20it.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EAny%20solutions%20would%20be%20appreciated.%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54094%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54094%22%20slang%3D%22en-US%22%3EThank%20you%20so%20much!%20It%20really%20helped.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53716%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53716%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20that%20fixed%20it%20for%20me.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53294%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53294%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20Teams%20clean-installed%20recently%20and%20I%20get%20the%20error%20from%20the%20get-go.%20This%20is%26nbsp%3Bhow%20I%26nbsp%3Bfixed%20mine....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Go%20to%20the%20System%20Tray%20and%20right-click%20on%20the%20Teams%20icon%3C%2FP%3E%3CP%3E2.%20Select%20Log%20Out%3C%2FP%3E%3CP%3E3.%20The%20app%20will%20go%20through%20the%20motions%20of%20logging%20off%20and%20restart%2C%20then%20ask%26nbsp%3Bfor%20your%20credentials.%20Enter%20your%20O365%20credentials%20and%20you%20should%20be%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20discovered%20that%20my%20issue%20was%20likely%26nbsp%3Bdue%20to%20my%20having%20a%20Hotmail%20account%20to%20login%20to%20my%20Windows%2010%20PC.%20Teams%20was%20probably%20picking%20up%20on%20that%20and%20using%20this%20wrong%20account%20to%20login%2C%20which%20incidentally%20caused%20it%20to%20fail.%20Logging%20off%20and%20logging%20in%20with%20the%20correct%20credentials%20solved%20mine.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-53146%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-53146%22%20slang%3D%22en-US%22%3EHave%20the%20same%20issue%20here%20with%20a%20couple%20of%20users.%3CBR%20%2F%3ENo%20personal%20credentials%20used%20for%20login%20or%20found%20in%20Credential%20Manager%3CBR%20%2F%3ENuked%20all%20the%20Teams%20folders%20I%20could%20find%20and%20did%20a%20complete%20re-install.%20Did%20not%20fix%20the%20issue.%20Still%20reports%20Error%20Code%20-%20500%20Failed%20to%20reach%3A%20%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%3C%2FA%3E%3CBR%20%2F%3ESome%20users%20updated%20fine%20and%20some%20did%20not.%20The%20ones%20that%20did%20not%20are%20basically%20up%20a%20creek%20without%20a%20paddle%20and%20can't%20get%20back%20on%20to%20teams%20via%20the%20App.%20Sign%20in%20to%20site%20is%20still%20available.%20Just%20the%20app%20is%20broken.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52880%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52880%22%20slang%3D%22en-US%22%3EBy%20mistake%20I%20used%20a%20personal%20microsoft%20login%2C%20maybe%20an%20error%20in%20this.%3CBR%20%2F%3EPS%3A%20Luke%20Nosbisch's%20decision%20did%20not%20help.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52879%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52879%22%20slang%3D%22en-US%22%3EHi%2C%20Luke.%3CBR%20%2F%3EThanks%20for%20solution.%20But%20is%20not%20helping%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52875%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52875%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Martin.%3CBR%20%2F%3EYes%2C%20I%20restart%20my%20computer.%3CBR%20%2F%3EYes%2C%20I%20reinstall%20software%20and%20install%20again.%20After%20starting%20with%20previose%20version%20his%20self%20updating%20and%20error%20appears.%20Update%20%D1%81an%20not%20be%20disabled.%3CBR%20%2F%3EWeb%20version%20is%20work%20fine.%3CBR%20%2F%3EMobile%20version%20not%20testing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52848%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52848%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here%2C%20reinstalled%2C%20removed%20credentials.%20Nothing%20has%20worked.%20Hopefully%20this%20gets%20resolved%20soon.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52734%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52734%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20issue%20here%2C%20reinstalling%20doesn't%20solve%20the%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52732%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52732%22%20slang%3D%22en-US%22%3EI%20tried%20this%2C%20and%20it%20did%20not%20resolve%20my%20issue%20(which%20is%20the%20same%20as%20the%20problem%20initially%20described%20on%20this%20page).%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52726%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52726%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20the%20same%20issue%20this%20morning.%20I%20used%20my%20personal%20account%20to%20sign%20into%20teams%20rather%20than%20my%20work%2Feducation%20account.%20You%20may%20have%20done%20the%20same%20thing.%20Go%20to%20your%20control%20Panel%20and%20Select%20the%20Credential%20Manager%2C%20then%20remove%20all%20of%20the%20msteams%20stuff%2C%20then%20try%20teams%20again.%20It%20will%20prompt%20you%20to%20login%20again.%20When%20I%20logged%20in%20as%20my%20work%20account%20it%20worked.%20One%20of%20my%20coworkers%20had%20the%20same%20issue%20and%20he%20figured%20it%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52594%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52594%22%20slang%3D%22en-US%22%3EI%20received%20some%20updates%20last%20week%20and%20no%20problems%20when%20using%20Teams...Did%20you%20use%20the%20same%20login%20to%20access%20teams%20after%20updates%20were%20applied%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52580%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20starting%20after%20latest%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52580%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Alexey%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20guess%20you%20tried%20to%20restart%20your%20computer%3F%3C%2FP%3E%3CP%3EHave%20you%20tried%20to%20reinstall%20the%20software%3F%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20it%20works%20in%20a%20browser%2C%20Internet%20Explorer%20for%20example%3F%3C%2FP%3E%3CP%3EDoes%20it%20works%20on%20your%20mobile%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBR%3C%2FP%3E%3CP%3EMartin%20Front%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor
Starting error, and so in a circle.
 
desktop-7841bf6d-1bc3-45e5-8a9a-20d2ea7391ea
Error code - 500
38 Replies
Highlighted

Hi Alexey,

 

I guess you tried to restart your computer?

Have you tried to reinstall the software? 

Does it works in a browser, Internet Explorer for example?

Does it works on your mobile?

 

BR

Martin Front

Highlighted
I received some updates last week and no problems when using Teams...Did you use the same login to access teams after updates were applied?
Highlighted

I had the same issue this morning. I used my personal account to sign into teams rather than my work/education account. You may have done the same thing. Go to your control Panel and Select the Credential Manager, then remove all of the msteams stuff, then try teams again. It will prompt you to login again. When I logged in as my work account it worked. One of my coworkers had the same issue and he figured it out.

Highlighted
I tried this, and it did not resolve my issue (which is the same as the problem initially described on this page).
Highlighted

Same issue here, reinstalling doesn't solve the problem. 

Highlighted

Same issue here, reinstalled, removed credentials. Nothing has worked. Hopefully this gets resolved soon. 

Highlighted

Hi Martin.
Yes, I restart my computer.
Yes, I reinstall software and install again. After starting with previose version his self updating and error appears. Update сan not be disabled.
Web version is work fine.
Mobile version not testing.

Highlighted
Hi, Luke.
Thanks for solution. But is not helping :)
Highlighted
By mistake I used a personal microsoft login, maybe an error in this.
PS: Luke Nosbisch's decision did not help.
Highlighted
Have the same issue here with a couple of users.
No personal credentials used for login or found in Credential Manager
Nuked all the Teams folders I could find and did a complete re-install. Did not fix the issue. Still reports Error Code - 500 Failed to reach: https://teams.microsoft.com
Some users updated fine and some did not. The ones that did not are basically up a creek without a paddle and can't get back on to teams via the App. Sign in to site is still available. Just the app is broken.
Highlighted
Solution

I had Teams clean-installed recently and I get the error from the get-go. This is how I fixed mine....

 

1. Go to the System Tray and right-click on the Teams icon

2. Select Log Out

3. The app will go through the motions of logging off and restart, then ask for your credentials. Enter your O365 credentials and you should be fine.

 

I discovered that my issue was likely due to my having a Hotmail account to login to my Windows 10 PC. Teams was probably picking up on that and using this wrong account to login, which incidentally caused it to fail. Logging off and logging in with the correct credentials solved mine.

Highlighted

Thanks that fixed it for me.

Highlighted
Thank you so much! It really helped.
Highlighted

I have similar problem with the native app on the Mac side. I tried uninstalling and removing all Microsoft Teams app preferences.  Restarted. I reinstalled the app. I even logged out of Office 365 in my other apps. 

 

Everytime I load up Microsoft Teams for Mac I get

 

---
D'oh! Something went wrong...
Restart
 
desktop-f37dbf05-dca6-4f3e-96be-c5eaa4ede814
Error code - 500
---
 
Can't get out of it.
 
Any solutions would be appreciated.
Highlighted

1- start the Microsoft mac client Teams

(Obviously it locks to the point that we know ...) but !!!

 

2- press the dock icon with the right mouse button. It opens a small context menu ...
"Disconnect" with the voice.

 

3- disconnect by clicking on the application after a few moments closes.

 

4- restarting the application this time the credential window opens.

 

5- At this point you enter the credentials of 365 office ... and ... everything works great !!!

Highlighted

A slight adjustment to the process outlined by Orlando worked for me. You have to skip the first small sign-in window (by closing it), then Teams Desktop will continue to load and present you with a larger sign-in window.  Filling in my credentials here worked!  (Side note: I did not do a reinstall - this was the first time I used Teams).

 

So, the adapted process:

1) Go to the System Tray and right-click on the Teams icon

2) Select Log Out

3) The app will go through the motions of logging off and restart, then ask for your credentials. (screenshot: Desktop2.PNG)

4) Close this window.  The app will continue to load and present you with a (more comprehensive?) sign-on window (which looks like it is within the app, rather than an "additional" window - screenshot: Desktop3.PNG)

5)  Entering my O365 credentials (company credentials) worked for me here.

 

Highlighted

I have not the otpion Log out when i right click on the app ...

Highlighted
Right-click on Teams in the Start bar and "logoff". Next time your login will be asked.
Highlighted

Hitting the same error... I have a personal account with MAM policies from my work account that apply Hello for Business login.

Pressing "sign out" does nothing.