Additional features, settings, or issues not covered by specific Microsoft Teams categories
Hi Sandi,
If you have any updates with us?
Thanks,
Richard
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi
I get the message ... "Doh! Something went wrong ... Try again .. If that does not work, try signing out and back in"
I have tried again several times, signed out and back and also rebooted.
Cheers,
Sandi
Additional features, settings, or issues not covered by specific Microsoft Teams categories
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi Sandi,
If you have any updates with us?
Thanks,
Richard
Hi Sandi,
Thanks for your feedback. Based on your description, I understand that you encounter this situation on Microsoft Teams desktop app and it only happen on when you connect to office Lan.
For this, I suppose this situation relate to the network connection. I suggest you contact your organization admin ti check there is any settings on office Lan, such as: port setting or firewall setting. You can check the organization's network for Microsoft Teams: https://docs.microsoft.com/en-us/microsoftteams/prepare-network.
Thanks,
Richard
Hi Richard,
The error I am getting is displayed below but this only happens when I use the office Lan. However, we connected remotely I am able to load the Miscrosoft Teams App.
… https://teams.microsoft.com/_#/oops?errorCode=orchestration&errorMessage=App failed app orchestration: Orchestration plan max execution time reached as stages: authenticationService_skype-auth could not complete
Also noted this in the logs
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Starting daemon App updates
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Set modern auth succeeded to true
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Logging telemetry event: memoryIndexAppBootstrap
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- Perf_WorkingSetSizeKB: 234912, name: memoryIndexAppBootstrap,
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Log file collection: file of type slimcore not found in <app-data-path>\Microsoft
\Teams\skylib. Used the regex '/debug-.*.log$/' to look for it.
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- zoom level reset to 0 - system
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- saved desktop zoom level as 3
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- delta: 23719, status: success, scenario: 5ff1b46b-8336-44cb-ba7c-14958107cdd9,
scenarioName: desktop_app_launch, name: desktop_app_launch, step: stop, sequence: 9, scenarioDelta: 23719, elapsed: 23719, Scenario.Name: desktop_app_launch,
Scenario.Step: stop, Scenario.Status: success,
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- preload renderer crash reporter: starting setup
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- preload renderer crash reporter: enable watson
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- phase: PLT, status: success, scenario: 441693e6-df02-4dfb-95a8-820023ae653f,
scenarioName: desktop_app_start, name: desktop_app_start, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 1014, Scenario.Name: desktop_app_start,
Scenario.Step: start, Scenario.Status: success,
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- phase: PLT, status: success, scenario: 441693e6-df02-4dfb-95a8-820023ae653f,
scenarioName: desktop_app_start, name: desktop_app_start, step: stop, sequence: 1, delta: 1295, scenarioDelta: 1295, elapsed: 2309, Scenario.Name: desktop_app_start,
Scenario.Step: stop, Scenario.Status: success,
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_set_session,
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Setting app session to 07f5e967-01eb-5189-8ada-45829a5ede69
Thu Jun 14 2018 13:24:44 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Machine has been idle for 0.234 seconds
Thu Jun 14 2018 13:24:48 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_page_bad_response_unhandled, responseCode: 403, errorUrl: https://,
Thu Jun 14 2018 13:24:48 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Unhandled get response details with http response code 403: https://
Thu Jun 14 2018 13:24:53 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_page_bad_response_unhandled, responseCode: 403, errorUrl: https://,
Thu Jun 14 2018 13:24:53 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Unhandled get response details with http response code 403: https://
Thu Jun 14 2018 13:25:01 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_page_bad_response_unhandled, responseCode: 403, errorUrl: https://,
Thu Jun 14 2018 13:25:01 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Unhandled get response details with http response code 403: https://
Thu Jun 14 2018 13:25:14 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_page_bad_response_unhandled, responseCode: 403, errorUrl: https://,
Thu Jun 14 2018 13:25:14 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Unhandled get response details with http response code 403: https://
Thu Jun 14 2018 13:26:05 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_page_bad_response_unhandled, responseCode: 403, errorUrl: https://,
Thu Jun 14 2018 13:26:05 GMT+1000 (AUS Eastern Standard Time) <2584> -- warning -- Unhandled get response details with http response code 403: https://
Thu Jun 14 2018 13:26:06 GMT+1000 (AUS Eastern Standard Time) <2584> -- event -- name: desktop_loading_timeout, url: https://, isTimeboxingWebAppInitialize: false,
Thu Jun 14 2018 13:26:06 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- Main Window Show: after 90 sec of no response from url https://
Thu Jun 14 2018 13:26:06 GMT+1000 (AUS Eastern Standard Time) <2584> -- info -- visible: truefocused: + falseminimized: falsewinVisible: falsewinFocused:
falsewinMinimized: false)
Hi Sandi,
To better help you, please send us a complete screenshot for the error message and let me know when this error happen. When you open Teams? When you perform some actions? Please let know the details.
Meanwhilw, if you are using Microsoft Teams desktop client, please help to try to sign in Teams on the web: https://teams.microsoft.com/. And you can try to change another browser and network to see if this issue persist.
Thanks,
Richard