Меню

Microsoft teams код ошибки caa82ee2 как исправить

Иногда команды Microsoft могут не запускаться с кодом ошибки caa82ee2. Обычно приложение зависает на несколько секунд незадолго до появления этого кода ошибки на экране. И сообщение об ошибке гласит:

  • Сожалеем, у нас возникла проблема. Рестарт. Если это не помогло, попробуйте выйти и снова войти. Код ошибки — caa82ee2.

Интересно, что ошибка команды caa82ee2 чаще возникает на серверах RDS. Обычно это означает, что истекло время ожидания запроса.

Ошибка в первую очередь затрагивает настольное приложение. Часто, если пользователи пытаются открыть команды в своем веб-браузере, служба застревает в бесконечном цикле перезарядки.

Решения для исправления ошибки Microsoft Teams caa82ee2

Очистить кеш

  1. Щелкните правой кнопкой мыши значок Teams на панели значков. Выбирать Покидать чтобы закрыть приложение.
  2. Затем откройте проводник и перейдите в % appdata% Microsoft команд.папка кэша команд Microsoft
  3. Очистите файлы из следующих папок кеша:
    • % appdata% Microsoft team кеш приложения cache.
    • % appdata% Microsoft team blob_storage.
    • % appdata% Microsoft team баз данных.
    • % appdata% Microsoft team GPUcache.
    • % appdata% Microsoft team IndexedDB.
    • % appdata% Microsoft team Локальное хранилище.
    • % appdata% Microsoft team tmp.
  4. После этого перезапустите Teams. Если это не помогло, попробуйте удалить все файлы из % appdata% Microsoft команд каталог.

Отключить настройки прокси

  1. Перейдите к Настройки → Сеть и Интернет → Прокси.
  2. Включите опцию Автоматически определять настройки.
  3. Затем отключите опцию Использовать прокси-сервер. Обновите команды и проверьте, сохраняется ли ошибка.

настройки прокси

Проверьте свою сеть

Ошибка caa82ee2 также может возникнуть, если ваше сетевое соединение довольно медленное и нестабильное. Если вашему компьютеру не удается подключиться к серверу в течение указанного диапазона времени, Teams отключит запрос на подключение.

  • Перезагрузите модем и компьютер. Или отключите модем.
  • Отключите все программы VPN, которые вы можете использовать.
  • Кроме того, отключите другие устройства, используя соединение.
  • Отключите брандмауэр.

После того, как вы все это сделали, снова запустите Teams и проверьте, сохраняется ли проблема.

Удалить учетные данные Teams

Ошибка caa82ee2 также может возникнуть, если вы недавно изменили настройки учетной записи или пароль. Следовательно, очистка учетных данных Teams должна исправить это.

  1. Перейти к Панель управления → Учетные записи пользователей → Менеджер учетных данных и откройте Диспетчер учетных данных.
  2. Затем нажмите на Учетные данные Windows.учетные данные windows pc
  3. Перейти к Общие учетные данные и найти msteams_adalsso / adal_context_segments.менеджер учетных данных ms team
  4. А затем удалите эту строку. Проверьте, исчезла ли ошибка.

Очистить временные данные с ПК

Временные данные, хранящиеся на вашем компьютере, могут замедлить ваше соединение. Используйте Очистку диска, чтобы быстро удалить временные файлы с вашего компьютера.

  1. Тип ‘очистка диска‘На панели поиска Windows и запустите инструмент.
  2. Выберите диск, на котором вы установили Teams и большинство ваших программ. Для большинства пользователей это диск C :.
  3. После этого выберите файлы, которые хотите очистить. Обязательно установите два флажка, предназначенные для временных файлов.очистка диска временные интернет-файлы
  4. Нажмите ОК.

Переустановите команды

Если ничего не помогло, попробуйте удалить и переустановить Teams. Запустите панель управления, перейдите в раздел «Программы», выберите «Команды» и нажмите кнопку Удалить кнопка. Перезагрузите вашу машину.удалить команды Майкрософт

Затем снова загрузите приложение с Официальный сайт Microsoft.

Источник

Here is a Couple of Fixes for Error Code caa82ee2 in Microsoft Teams. The major reason for this issue is the accumulation of temporary app-data

The major reason for this issue is the accumulation of temporary app-data. These do not only include the Cache but also the tmp, Blob, and other related data. The fix, as you might have guessed, involves deleting all these bits of data from the Teams directory. In some instances, a proxy server might also lead to this error, so consider disabling it as well. Both these methods are listed below.

caa82ee2 for teams

Fix 1: Delete Temporary Data

Delete Temporary Data

  1. To delete the app’s temporary data, launch File Explorer and head over to the below location:
    %appdata%Microsoftteams
  2. Now select the following folders and delete them:
    • Cache
    • Blob_Storage
    • Databases
    • GPUcache
    • IndexedDB
    • Local Storage
    • Tmp
  3. Once the deletion is complete, relaunch the app and it should fix the error code caa82ee2.

Fix 2: Turn off Proxy

If the Proxy Server has been enabled on your system, then the data packets would be reaching the Teams server with a masked IP Address. This could lead to issues in establishing a successful connection and in turn, could show up the above error as well. So it’s better to disable the proxy, at least till the time you are using the Teams app.

Turn off Proxy

To do so, head over to Settings > Network and Internet > Proxy > Disable the “Use a Proxy server” option. That’s it. You may now try and re-establish the connection.

Fix 3: Check your Internet

It mainly happens due to poor internet connectivity at a slow speed. The teams may take time to connect to the server, causing the error to pop-up. Just disable any proxy or background downloads and try again to login to the teams account.

If you’ve any thoughts on Fix Microsoft Teams Error caa82ee2, then feel free to drop in below comment box. Also, please subscribe to our DigitBin YouTube channel for videos tutorials. Cheers!

Источник

Сбой caa7004 в Майкрософт Тимс появляется при открытии программы, в момент входа в учетную запись или во время подключения к онлайн-конференции. Встречается он нечасто, но сильно осложняет жизнь пользователям. Особенно неприятно, когда даже перезагрузка не помогает. Что же делать, когда возникает код ошибки caa70004 в Microsoft Teams? Именно этому вопросу посвящена наша статья.

Решение проблемы

Вид ошибки caa70004 в Microsoft Teams

Выглядит данный сбой следующим образом:

В первую очередь при его появлении перезапустите ПК, если еще этого не делали. Многие проблемы и системные сбои удается устранить таким способом. Начинать нужно с такого решения. А если оно не помогло, то придется перейти к более сложному.

Суть данной ошибки в том, что компьютер пользователя не может подключиться к серверам Микрософт Тимс. Это может быть связано с:

Разберемся с каждым случаем по отдельности.

Вариант №1: Устаревший Майкрософт Тимс

На официальном сайте программы указано, что корректная работа гарантируется только при использовании последней версии MS Teams. А значит, появление проблем может быть связано с тем, что новое обновление еще не установлено. Решение – установить его вручную. Для этого:

Вариант №2: Антивирус

Антивирусная защита в некоторых ситуациях мешает корректной работе программ. Например, она может заблокировать подключение MS Teams к интернету. Решение тут одно – на время приостановить работу антивируса. Если это помогло, то программу стоит добавить список исключений.

Вариант №3: Системный сбой

В Windows может с течением времени случиться ситуация, когда настройки сетевого подключения собьются. А значит, их нужно сбросить до исходных значений. Делается это с помощью одной консольной команды.

Вариант №4: Проблемы с Wi-Fi-роутером

Если вы подключены к интернету через Wi-Fi-роутер, то появление сбоя с кодом caa70004 может быть вызвано именно им. В настройках устройства мы копаться не рекомендуем. Попробуйте просто его перезапустить (выключить и включить). Как ни странно, это может помочь.

Вариант №5: Избыток кэш-файлов

В кэш сохраняются те данные, которые загружались в Teams с течением времени – аватары пользователей, показанные презентации и т. д. И если он забит или файлы оттуда повреждены, то могут возникнуть неполадки. Решение тут – ручная чистка. Но предварительно следует удалить программу.

Вот пошаговая инструкция:

Fix Microsoft Teams Error caa82ee2

fix error caa82ee2 for teams

The major reason for this issue is the accumulation of temporary app-data. These do not only include the Cache but also the tmp, Blob, and other related data. The fix, as you might have guessed, involves deleting all these bits of data from the Teams directory. In some instances, a proxy server might also lead to this error, so consider disabling it as well. Both these methods are listed below.

caa82ee2 for teams

Fix 1: Delete Temporary Data

Delete Temporary Data

Fix 2: Turn off Proxy

If the Proxy Server has been enabled on your system, then the data packets would be reaching the Teams server with a masked IP Address. This could lead to issues in establishing a successful connection and in turn, could show up the above error as well. So it’s better to disable the proxy, at least till the time you are using the Teams app.

Turn off Proxy

To do so, head over to Settings > Network and Internet > Proxy > Disable the “Use a Proxy server” option. That’s it. You may now try and re-establish the connection.

Fix 3: Check your Internet

It mainly happens due to poor internet connectivity at a slow speed. The teams may take time to connect to the server, causing the error to pop-up. Just disable any proxy or background downloads and try again to login to the teams account.

If you’ve any thoughts on Fix Microsoft Teams Error caa82ee2, then feel free to drop in below comment box. Also, please subscribe to our DigitBin YouTube channel for videos tutorials. Cheers!

How to Fix Microsoft Teams Error caa82ee2

You may have experienced the Microsoft Teams Error caa82ee2 at one point or the other, and it can be a disconcerting experience. Not to worry, we are here with the solution to fix the issue of the Microsoft Teams caa82ee2 error.

Microsoft Teams is a rich and versatile proprietary business communication platform developed by Microsoft in March 2017. It is part of the larger Microsoft 365 family of products. Microsoft Teams offers workspace chat and video conferencing, file storage, and application integration, among a host of other activities. Because of its versatility, MS Teams is being deployed as an all-around solution platform in business, education, and a wide array of fields.

The desktop app of Microsoft Teams sometimes may not open successfully and will instead give the error code caa82ee2. The app will freeze for some seconds before the caa82ee2 error appears on the screen, with the following message:

“We’re sorry—we’ve run into an issue. Restart. If that doesn’t work, try signing out and back in. Error code – caa82ee2.”

You may have experienced the Microsoft Teams Error caa82ee2 at one point or the other, and it can be a disconcerting experience. Not to worry, we are here with the solution to fix the issue of the Microsoft Teams caa82ee2 error. Join us as we navigate to a comprehensive resolution of your Microsoft Teams Error caa82ee2 code issues.

If your MS Teams desktop client comes up with the error code caa82ee2, you may have to take the following steps to resolve the error:

Clear the Cache

Microsoft Teams Error caa82ee2

After this procedure, restart your MS Teams. If the error still persists, then try emptying the %appdata%Microsoftteams directory. This can be achieved by removing all the files from the directory.

Disable Proxy Settings

Microsoft Teams Error caa82ee2

Resolve all Network Connectivity Issues

Microsoft Teams Error caa82ee2 could also occur if your network connectivity is weak or fluctuating. If your PC is unable to connect to the MS Teams server within a short time duration, Teams will decline the connection request and the caa82ee2 error shows up.

The first thing to do is to check whether your internet connection is stable. Examine the network icon on your taskbar, if the network has limited connectivity, then it is not possible to reach the MS Teams server. If you have access to an alternative network, you may try establishing that network connection to see whether the error will disappear.

You may also troubleshoot your network settings using the inbuilt network diagnostics tool, by right-clicking on the network icon on your taskbar and selecting “Troubleshoot problems”. Your network diagnostics tool will begin a deep search of the possible errors and detect these errors, in addition to recommending possible solutions.

If at the conclusion of this process, your problem is yet to be solved, move to the next fix.

Clear Teams Credentials from PC

The Microsoft Teams Error caa82ee2 may be as a result of the user changing his/her account settings or password. The following steps will help you resolve the issue of the MS Teams Error caa82ee2.

Microsoft Teams Error caa82ee2

Microsoft Teams Error caa82ee2

Clear Temporary Data From your Computer

Temporary data stored on your PC may also slow down your network connectivity. Use the Disk Cleanup tool to clear temporary files from the system.

Reinstall MS Teams on your PC

Microsoft Teams Error caa82ee2

The error code will not be visible again after you have properly reinstalled MS Teams on your device.

Источники:

https://ms-teams. ru/faq/error-caa70004-in-microsoft-teams

https://www. digitbin. com/fix-error-caa82ee2-teams/

https://www. phonereporters. com/2021/01/fix-microsoft-teams-error-caa82ee2/

Источник

  • Question

  • What does this mean? 

    Modern Authentication failed here, but you’ll still be able to sign in.  Your status code is caa82ee2.

    What is the status code caa82ee2?

    What do i do to fix it?  BTW, we dont use ADFS.  We simply use ADDS with basic Azure Active Directory.

All replies

  • That’s what I thought too, but We dont use ADFS. Its not that you are explicitly using ADFS in your environment , the forums titles are misleading.
      when you login with your Teams internally it uses optimized path for the first time login process to login with WS-Trust kerberos authentication endpoints of ADFS. And If this is not successful then the client (Descktop) will try to
    perform an interactive login session which is presented as web browser dialog.

    No need to use ADFS , just enable

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    • Proposed as answer by

      Tuesday, April 23, 2019 7:05 AM

  • Hi jrauman,

    Agree with Thuyavan Ganesan, please enable the Forms Authentication with the commend Thuyavan provided, then check whether fix this issue. 

    In addition, you could refer to the following blog to find the troubleshooting steps:

    Microsoft Teams login error — Modern authentication failed here status code caa20004. 

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Thank you both. Two follow-up questions.

    1. i have seen other people getting the Modern Authentication error, but no one has the exact error code i have.  Why is my error code unique to my company 

    caa82ee2

    2. Where do i type that command? On the domain controller?  do i have to use Active Directory Management Shell to type it?

  • Hi just checking to see if anyone knows what the error ‘caa82ee2’ means?  and how do I type this command?

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    Do i use AD PowerShell?  Do i type it exactly as written above?

  • Hi just checking to see if anyone knows what the error ‘caa82ee2’ means?  and how do I type this command?

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    Do i use AD PowerShell?  Do i type it exactly as written above?

    You can get the details of the status code «caa82ee2» from the log files located in your machine 
    C:UsersusernameAppDataRoamingMicrosoftTeams

    Yes AD Powershell and type as it is.

    • Proposed as answer by
      woshixiaobai
      Friday, April 26, 2019 6:52 AM

  • Hi jrauman,

    Agree with Thuyavan, please follow the steps, then check again.

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Hi jrauman,

    Is there any update for this issue? If the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Hi everybody,

    I have same issue in my company with 500+ O365 users. We have AD on premise with AD Connect sync to Azure AD, we do not use ADFS. Starting several days one user gets error caa82ee2 while trying to login to Teams application. I tried to enter above command Enable-AdfsEndpoint
    -TargetAddressPath “/adfs/services/trust/13/windowstransport” into PowerShell console of our onpremise AD but I got error that command is not recognized most likely because we do not have ADFS services running on the server. Does anybody have solution if ADFS
    services are not in use?

    Best Regards

    Haris Alatović

    • Proposed as answer by
      Nargly
      Friday, January 31, 2020 6:38 PM

  • Thank you woshixiaobai.  I tried running that command from my domain controller and i got the following error. 

    PS C:> Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”
    >>
    >>
    Enable-AdfsEndpoint : The term ‘Enable-AdfsEndpoint’ is not recognized as the name of a cmdlet, function, script file,
    or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
    try again.
    At line:1 char:1
    + Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windo …
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Enable-AdfsEndpoint:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

     Is this because i’m not running ADFS?

  • Evan, i ran that command that you said i should run. i got this error.

    PS C:> Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”
    >>
    >>
    Enable-AdfsEndpoint : The term ‘Enable-AdfsEndpoint’ is not recognized as the name of a cmdlet, function, script file,
    or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
    try again.
    At line:1 char:1
    + Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windo …
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Enable-AdfsEndpoint:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

  • Can someone PLEASE tell me what this error code means?  caa82ee2.

    Here is the error in the context of the Teams logs.

    Microsoft_ADAL_response_rtime: 121011, Microsoft_ADAL_api_error_code: caa82ee2, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 05:52:53 GMT-0500 (Eastern Standard Time) <18484> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: c94cc26e-461d-479a-a8a1-d5368459fb6f, 

  • Haris, did you have any luck?  See my replies i made earlier today. I didnt.

  • I’m also seeing these errors in the Teams log after a password change.

    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — error — BluetoothLE Desktop: ble:scan-stop BluetoothRadioState.Unavailable 
    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — error — BluetoothLE Desktop: ble:advertisement-stop BluetoothRadioState.Unavailable 
    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — info — BluetoothLE Desktop: ble:get-radio-state 2 

    Wed Feb 05 2020 09:17:04 GMT-0500 (Eastern Standard Time) <18484> — event — errorCode: FailedOrchestration, errorStep: fetch_user_profile, errorState: oops, errorUrl: undefined, status: success, scenario: 4d780fd8-bf75-418a-a832-1b2706cd16ca, scenarioName:
    desktop_web_app_error_redirect, name: desktop_web_app_error_redirect, step: start, sequence: 0, delta: 1, scenarioDelta: 1, elapsed: 42516372, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_web_app_error_redirect, Scenario.Step: start,
    Scenario.Status: success,  

    Wed Feb 05 2020 09:17:04 GMT-0500 (Eastern Standard Time) <18484> — event — errorCode: FailedOrchestration, errorStep: fetch_user_profile, errorState: oops, errorUrl: undefined, status: success, scenario: 4d780fd8-bf75-418a-a832-1b2706cd16ca, scenarioName:
    desktop_web_app_error_redirect, name: desktop_web_app_error_redirect, step: stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 42516372, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_web_app_error_redirect, Scenario.Step: stop, Scenario.Status:
    success,  

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Resetting teamsUserProfile 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Current guest tenants: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ieMode11d is not enabled from preauth setting. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: domain_name_check_being_called, featureToCheck: undefined, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — wam is not enabled from preauth setting. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: domain_name_check_being_called, featureToCheck: undefined, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — ADAL: IE emulation not enabled from ECS flag. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: ieMode_disabled., vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Creating SSO context diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Let’s get you up and running… diag:0 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Let’s get you up and running… 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: teams_regkeyHive_exist_true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Teams folder in regkey exist: true. 

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: c704649c-939b-4737-a5a9-c32a101ee3af, scenarioName: desktop_check_register_key, name: desktop_check_register_key, step: start, sequence: 0, delta:
    0, scenarioDelta: 0, elapsed: 647, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_check_register_key, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — successfully get adalVersionvalue 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: c704649c-939b-4737-a5a9-c32a101ee3af, scenarioName: desktop_check_register_key, name: desktop_check_register_key, step: stop, sequence: 1, delta:
    0, scenarioDelta: 0, elapsed: 647, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_check_register_key, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: teams_regkeyHive_exist_true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — After setup adal version Teams folder in regkey exist: true. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: WAM enabled via ECS: undefined, OS version above RS2: true, EnableAdal2: true, isDomainNameEnabledForWam: false 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Tenant Id: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Getting context for:msteams_adalsso_adal_context 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Tenant Id: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — warning — No saved context found to resume from. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — warning — No saved context found. Creating a new context. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Logout forceprompt: fpStorage null prevForcePrompt nullshouldForcePrompt null 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Signing in with upn diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Auth Authority:https://login.microsoftonline.com/common 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Acquiring token… isFirstRunfalse diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Authenticating resource — https://api.spaces.skype.com… diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: Authenticating resource — https://api.spaces.skype.com… correlationId: 26db4493-58aa-47c8-8b7f-dec1d5138f9c 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Hang tight! We’re getting you connected. diag:0 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Hang tight! We’re getting you connected. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — Error occurred while saving env_config.json 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — type: gpu, electronBuild: 24210732, appRuntime: 0.658, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,
    timeSinceActivity: 0.011, appStates: Started,SSOStart, timeSinceAppState: 0.016000032424926758, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,
    timeSinceLastDiagnosticEvent: 0.010999917984008789, timeSinceSecondLastDiagnosticEvent: 0.016000032424926758, status: success, scenario: 935f624d-53fc-4bc4-94fd-2997064adfcd, scenarioName: desktop_gpu_process_crashed, name: desktop_gpu_process_crashed, step:
    start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 658, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_gpu_process_crashed, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — type: gpu, electronBuild: 24210732, appRuntime: 0.658, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,
    timeSinceActivity: 0.011, appStates: Started,SSOStart, timeSinceAppState: 0.016000032424926758, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,
    timeSinceLastDiagnosticEvent: 0.010999917984008789, timeSinceSecondLastDiagnosticEvent: 0.016000032424926758, status: success, scenario: 935f624d-53fc-4bc4-94fd-2997064adfcd, scenarioName: desktop_gpu_process_crashed, name: desktop_gpu_process_crashed, step:
    stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 659, stepDelta: 1, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_gpu_process_crashed, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: desktop_gpu_process_crashed, type: gpu, electronBuild: 24210732, appRuntime: 0.659, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,desktop_gpu_process_crashed,
    timeSinceActivity: -1, appStates: Started,SSOStart, timeSinceAppState: 0.01699995994567871, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,ua:desktop_gpu_process_crashed,
    timeSinceLastDiagnosticEvent: 0, timeSinceSecondLastDiagnosticEvent: 0.011999845504760742, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — GPU process crashed, not restarting app and fallback to software rendering. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — BluetoothLE Desktop: ble:radio-not-ready  

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — GPU process crashed, not restarting app and fallback to software rendering. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — notification manager: dom-ready event received 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 910cec8a-be9b-43bc-9227-279a666f9290, scenarioName: desktop_notification_window_initialized, name: desktop_notification_window_initialized, step:
    stop, sequence: 1, delta: 301, scenarioDelta: 301, elapsed: 835, stepDelta: 301, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_notification_window_initialized, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — notification manager: notification window ready 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Main Window Hide: loading window ready 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Loading window shown with focus due to first show 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: 26db4493-58aa-47c8-8b7f-dec1d5138f9c, Microsoft_ADAL_response_rtime: 810, Microsoft_ADAL_api_error_code: caa2000c, vdiMode:
    0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: SSO requires credential. Status: caa2000c. Attempting windows auth. 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — SSO requires credential. Status: caa2000c. Attempting windows auth. diag:1 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: fda60763-f2c9-4034-b89f-e51cc814e403, scenarioName: desktop_wia, name: desktop_wia, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed:
    1468, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_wia, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:Login promise for online check 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:Response promise for online check success with retryAttempt=0 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:background sync downloaded preauth settings 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 386d1986-8c38-404b-be31-7b05d87da88c, scenarioName: desktop_preauth_settings_file_save, name: desktop_preauth_settings_file_save, step: start, sequence:
    0, delta: 0, scenarioDelta: 0, elapsed: 1690, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_preauth_settings_file_save, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 63f87a25-7e8f-4901-aab4-19f94f57cee7, scenarioName: desktop_preauth_download_sync, name: desktop_preauth_download_sync, step: stop, sequence: 1, delta:
    1087, scenarioDelta: 1087, elapsed: 1690, stepDelta: 1087, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_preauth_download_sync, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — retryAttempt: 0, coldboot: false, status: success, scenario: ffc13764-c258-4aab-aaf7-64cab352d239, scenarioName: desktop_preupn_download_async, name: desktop_preupn_download_async,
    step: stop, sequence: 1, delta: 1089, scenarioDelta: 1089, elapsed: 1691, stepDelta: 1089, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_preupn_download_async, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 386d1986-8c38-404b-be31-7b05d87da88c, scenarioName: desktop_preauth_settings_file_save, name: desktop_preauth_settings_file_save, step: stop, sequence:
    1, delta: 4, scenarioDelta: 4, elapsed: 1694, stepDelta: 4, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_preauth_settings_file_save, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 30fe235f-4845-40db-b09d-591e1cec8fa2, scenarioName: desktop_settings_save, name: desktop_settings_save, step: start, sequence: 0, delta: 0, scenarioDelta:
    0, elapsed: 2219, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_settings_save, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 30fe235f-4845-40db-b09d-591e1cec8fa2, scenarioName: desktop_settings_save, name: desktop_settings_save, step: stop, sequence: 1, delta: 4, scenarioDelta:
    4, elapsed: 2223, stepDelta: 4, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_settings_save, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — error — ssoerr -Needs to do login window promise. Login failed with error:Error: 0�
    �: 
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — event — wiaError: {}, status: failure, scenario: fda60763-f2c9-4034-b89f-e51cc814e403, scenarioName: desktop_wia, name: desktop_wia, step: stop, sequence: 1, delta: 1547, scenarioDelta:
    1547, elapsed: 3015, stepDelta: 1547, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_wia, Scenario.Step: stop, Scenario.Status: failure,  
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — info — SSO requires credential. Status: caa2000c. Windows auth. caa90002 diag:1 
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: SSO requires credential. Status: caa2000c. Windows auth. caa90002 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: b655a1db-7142-4442-bbfd-ba746cdd683b, Microsoft_ADAL_response_rtime: 796, Microsoft_ADAL_api_error_code: caa2000c, vdiMode:
    0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — https://api.spaces.skype.com: Login status caa2000c diag:1 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: Acq token failed with:caa2000c 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Showing login window. correlationId:b655a1db-7142-4442-bbfd-ba746cdd683b 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — status: abandoned, scenario: 5bbf49ae-7fb9-4329-8eb8-d4bd6e1a8d1e, scenarioName: desktop_app_load, name: desktop_app_load, step: stop, sequence: 1, delta: 3607, scenarioDelta:
    3607, elapsed: 3813, stepDelta: 3607, vdiMode: 0, eventpdclevel: 1, Scenario.Name: desktop_app_load, Scenario.Step: stop, Scenario.Status: abandoned,  
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Go ahead and log in. diag:0 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Go ahead and log in. 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Login UI in progress for upn. diag:1 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: (Login Window) Login UI in progress. 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — panelview: Panel.Type: loginWindow, Panel.Region: modal, Panel.LaunchMethod: login, DataBag.AuthStack: ADAL, Panel.ViewId: bc05acd9-a4ca-4c1e-805c-f49facb1a54c, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — emit status indicator state change from undefined to Unknown 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — Clearing taskbar overlay icon 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — Added Unknown (current state: undefined -> Unknown) 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — StatusIndicatorStateService initialized 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — event — name: initialize_status_indicator, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — event — panelaction: Action.Outcome: launch, Action.Gesture: click, Action.Scenario: openTrayIconMenu, Action.ScenarioType: other, DataBag.StatusIndicatorState: Unknown, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:44 GMT-0500 (Eastern Standard Time) <16328> — event — panelaction: Action.Outcome: launch, Action.Gesture: click, Action.Scenario: openTrayIconMenu, Action.ScenarioType: other, DataBag.StatusIndicatorState: Unknown, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 176, Microsoft_ADAL_correlationId: 74f1266a-78dd-42ea-924e-88b5532864fa, Microsoft_ADAL_response_rtime: 300052, Microsoft_ADAL_api_error_code: caa7000a,
    vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Could not login user — status: caa7000a diag:1 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — (Login Window) Could not login user — status: caa7000a 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — SSO Uber catch 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Set upn window user upn 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Modern authentication failed here, but you’ll still be able to sign in. Your status code is caa7000a. diag:0 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Modern authentication failed here, but you’ll still be able to sign in. Your status code is caa7000a. 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Sso failed, updating cookie settings. Status:caa7000a diag:1 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — Fallback to webauth. Err:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: past-sso-success, eventInfo: true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: webAuthDisabled, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: indivRoadblockDisabled:false,modernAuthSucceeded:true, disableWebAuth:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: roadBlockEnabled:undefined,loginInAsGuest:false,IndividualRoadblock:true,isLoggedInAnonymously:false,isRigel:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Guest Tenant Id set to  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: webAuthDisabled, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: indivRoadblockDisabled:false,modernAuthSucceeded:true, disableWebAuth:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — panelview: Panel.Type: oopsPage, Panel.Region: main, Panel.LaunchMethod: userInitiated, DataBag.OopsReason: auth_indiv_roadblock, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — warning — Loading oops page with id: 0 due to: auth_indiv_roadblock 

  • More errors

    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: desktop_auth_roadblock, reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having
    trouble completing the process, talk to your IT admin., oopsId: 0, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having trouble completing the process,
    talk to your IT admin., oopsId: 0, status: success, scenario: 7db982fc-f01b-4627-86b9-1af00309d9b6, scenarioName: desktop_auth_roadblock, name: desktop_auth_roadblock, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 303903, stepDelta: 0, vdiMode:
    0, eventpdclevel: 3, Scenario.Name: desktop_auth_roadblock, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having trouble completing the process,
    talk to your IT admin., oopsId: 0, status: success, scenario: 7db982fc-f01b-4627-86b9-1af00309d9b6, scenarioName: desktop_auth_roadblock, name: desktop_auth_roadblock, step: stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 303904, stepDelta: 1, vdiMode:
    0, eventpdclevel: 3, Scenario.Name: desktop_auth_roadblock, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — emit status indicator state change from Unknown to AuthenticationFailed 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Setting the taskbar overlay icon — Sign in again 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Added AuthenticationFailed (current state: Unknown -> AuthenticationFailed) 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — SSO failed. ErrorCode:authentication_failed Error Desc: Status: caa7000a 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 3dd8a248-b2c2-4774-a9cd-9f27f4ca9987, scenarioName: desktop_win_sso, name: desktop_win_sso, 

  • I received this same error code «caa82ee2″ but also the other related error code «4c7».  After much troubleshooting, it
    turned out that I did not have to mess with the settings on our DC at all.  I realized that I was signed in to Teams on a remote computer.  After I signed out of all devices, (then after waiting a while), I tried again while running Teams as admin,
    then Teams finally started up properly at that point!

    Note: this problem occurred as a result of a password policy update after which I was forced to change my password.

  • Has anyone figured this out yet? I also get all of the above and the not recognized error when trying to run the powershell command. Any help would be appreciated. The users are piling up now. Whats annoying is it is not all of them??? Why?

Источник

  • Question

  • What does this mean? 

    Modern Authentication failed here, but you’ll still be able to sign in.  Your status code is caa82ee2.

    What is the status code caa82ee2?

    What do i do to fix it?  BTW, we dont use ADFS.  We simply use ADDS with basic Azure Active Directory.

All replies

  • That’s what I thought too, but We dont use ADFS. Its not that you are explicitly using ADFS in your environment , the forums titles are misleading.
      when you login with your Teams internally it uses optimized path for the first time login process to login with WS-Trust kerberos authentication endpoints of ADFS. And If this is not successful then the client (Descktop) will try to
    perform an interactive login session which is presented as web browser dialog.

    No need to use ADFS , just enable

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    • Proposed as answer by

      Tuesday, April 23, 2019 7:05 AM

  • Hi jrauman,

    Agree with Thuyavan Ganesan, please enable the Forms Authentication with the commend Thuyavan provided, then check whether fix this issue. 

    In addition, you could refer to the following blog to find the troubleshooting steps:

    Microsoft Teams login error — Modern authentication failed here status code caa20004. 

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Thank you both. Two follow-up questions.

    1. i have seen other people getting the Modern Authentication error, but no one has the exact error code i have.  Why is my error code unique to my company 

    caa82ee2

    2. Where do i type that command? On the domain controller?  do i have to use Active Directory Management Shell to type it?

  • Hi just checking to see if anyone knows what the error ‘caa82ee2’ means?  and how do I type this command?

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    Do i use AD PowerShell?  Do i type it exactly as written above?

  • Hi just checking to see if anyone knows what the error ‘caa82ee2’ means?  and how do I type this command?

    Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”

    Do i use AD PowerShell?  Do i type it exactly as written above?

    You can get the details of the status code «caa82ee2» from the log files located in your machine 
    C:UsersusernameAppDataRoamingMicrosoftTeams

    Yes AD Powershell and type as it is.

    • Proposed as answer by
      woshixiaobai
      Friday, April 26, 2019 6:52 AM

  • Hi jrauman,

    Agree with Thuyavan, please follow the steps, then check again.

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Hi jrauman,

    Is there any update for this issue? If the reply is helpful to you, please try to mark it as an answer, it will help others who have the similar issue.

    Best Regards,
    Evan Jiang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.


    Click
    here to learn more. Visit the dedicated
    forum to share, explore and talk to experts about Microsoft Teams.

  • Hi everybody,

    I have same issue in my company with 500+ O365 users. We have AD on premise with AD Connect sync to Azure AD, we do not use ADFS. Starting several days one user gets error caa82ee2 while trying to login to Teams application. I tried to enter above command Enable-AdfsEndpoint
    -TargetAddressPath “/adfs/services/trust/13/windowstransport” into PowerShell console of our onpremise AD but I got error that command is not recognized most likely because we do not have ADFS services running on the server. Does anybody have solution if ADFS
    services are not in use?

    Best Regards

    Haris Alatović

    • Proposed as answer by
      Nargly
      Friday, January 31, 2020 6:38 PM

  • Thank you woshixiaobai.  I tried running that command from my domain controller and i got the following error. 

    PS C:> Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”
    >>
    >>
    Enable-AdfsEndpoint : The term ‘Enable-AdfsEndpoint’ is not recognized as the name of a cmdlet, function, script file,
    or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
    try again.
    At line:1 char:1
    + Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windo …
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Enable-AdfsEndpoint:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

     Is this because i’m not running ADFS?

  • Evan, i ran that command that you said i should run. i got this error.

    PS C:> Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windowstransport”
    >>
    >>
    Enable-AdfsEndpoint : The term ‘Enable-AdfsEndpoint’ is not recognized as the name of a cmdlet, function, script file,
    or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and
    try again.
    At line:1 char:1
    + Enable-AdfsEndpoint -TargetAddressPath “/adfs/services/trust/13/windo …
    + ~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : ObjectNotFound: (Enable-AdfsEndpoint:String) [], CommandNotFoundException
        + FullyQualifiedErrorId : CommandNotFoundException

  • Can someone PLEASE tell me what this error code means?  caa82ee2.

    Here is the error in the context of the Teams logs.

    Microsoft_ADAL_response_rtime: 121011, Microsoft_ADAL_api_error_code: caa82ee2, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 05:52:53 GMT-0500 (Eastern Standard Time) <18484> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: c94cc26e-461d-479a-a8a1-d5368459fb6f, 

  • Haris, did you have any luck?  See my replies i made earlier today. I didnt.

  • I’m also seeing these errors in the Teams log after a password change.

    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — error — BluetoothLE Desktop: ble:scan-stop BluetoothRadioState.Unavailable 
    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — error — BluetoothLE Desktop: ble:advertisement-stop BluetoothRadioState.Unavailable 
    Wed Feb 05 2020 09:15:02 GMT-0500 (Eastern Standard Time) <18484> — info — BluetoothLE Desktop: ble:get-radio-state 2 

    Wed Feb 05 2020 09:17:04 GMT-0500 (Eastern Standard Time) <18484> — event — errorCode: FailedOrchestration, errorStep: fetch_user_profile, errorState: oops, errorUrl: undefined, status: success, scenario: 4d780fd8-bf75-418a-a832-1b2706cd16ca, scenarioName:
    desktop_web_app_error_redirect, name: desktop_web_app_error_redirect, step: start, sequence: 0, delta: 1, scenarioDelta: 1, elapsed: 42516372, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_web_app_error_redirect, Scenario.Step: start,
    Scenario.Status: success,  

    Wed Feb 05 2020 09:17:04 GMT-0500 (Eastern Standard Time) <18484> — event — errorCode: FailedOrchestration, errorStep: fetch_user_profile, errorState: oops, errorUrl: undefined, status: success, scenario: 4d780fd8-bf75-418a-a832-1b2706cd16ca, scenarioName:
    desktop_web_app_error_redirect, name: desktop_web_app_error_redirect, step: stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 42516372, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_web_app_error_redirect, Scenario.Step: stop, Scenario.Status:
    success,  

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Resetting teamsUserProfile 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Current guest tenants: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ieMode11d is not enabled from preauth setting. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: domain_name_check_being_called, featureToCheck: undefined, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — wam is not enabled from preauth setting. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: domain_name_check_being_called, featureToCheck: undefined, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — ADAL: IE emulation not enabled from ECS flag. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: ieMode_disabled., vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Creating SSO context diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Let’s get you up and running… diag:0 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Let’s get you up and running… 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: teams_regkeyHive_exist_true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Teams folder in regkey exist: true. 

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: c704649c-939b-4737-a5a9-c32a101ee3af, scenarioName: desktop_check_register_key, name: desktop_check_register_key, step: start, sequence: 0, delta:
    0, scenarioDelta: 0, elapsed: 647, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_check_register_key, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — successfully get adalVersionvalue 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: c704649c-939b-4737-a5a9-c32a101ee3af, scenarioName: desktop_check_register_key, name: desktop_check_register_key, step: stop, sequence: 1, delta:
    0, scenarioDelta: 0, elapsed: 647, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_check_register_key, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: teams_regkeyHive_exist_true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — After setup adal version Teams folder in regkey exist: true. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: WAM enabled via ECS: undefined, OS version above RS2: true, EnableAdal2: true, isDomainNameEnabledForWam: false 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Tenant Id: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Getting context for:msteams_adalsso_adal_context 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — ADAL: Tenant Id: 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — warning — No saved context found to resume from. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — warning — No saved context found. Creating a new context. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Logout forceprompt: fpStorage null prevForcePrompt nullshouldForcePrompt null 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Signing in with upn diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Auth Authority:https://login.microsoftonline.com/common 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Acquiring token… isFirstRunfalse diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Authenticating resource — https://api.spaces.skype.com… diag:1 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: Authenticating resource — https://api.spaces.skype.com… correlationId: 26db4493-58aa-47c8-8b7f-dec1d5138f9c 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Hang tight! We’re getting you connected. diag:0 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Hang tight! We’re getting you connected. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — Error occurred while saving env_config.json 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — type: gpu, electronBuild: 24210732, appRuntime: 0.658, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,
    timeSinceActivity: 0.011, appStates: Started,SSOStart, timeSinceAppState: 0.016000032424926758, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,
    timeSinceLastDiagnosticEvent: 0.010999917984008789, timeSinceSecondLastDiagnosticEvent: 0.016000032424926758, status: success, scenario: 935f624d-53fc-4bc4-94fd-2997064adfcd, scenarioName: desktop_gpu_process_crashed, name: desktop_gpu_process_crashed, step:
    start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 658, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_gpu_process_crashed, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — type: gpu, electronBuild: 24210732, appRuntime: 0.658, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,
    timeSinceActivity: 0.011, appStates: Started,SSOStart, timeSinceAppState: 0.016000032424926758, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,
    timeSinceLastDiagnosticEvent: 0.010999917984008789, timeSinceSecondLastDiagnosticEvent: 0.016000032424926758, status: success, scenario: 935f624d-53fc-4bc4-94fd-2997064adfcd, scenarioName: desktop_gpu_process_crashed, name: desktop_gpu_process_crashed, step:
    stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 659, stepDelta: 1, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_gpu_process_crashed, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — name: desktop_gpu_process_crashed, type: gpu, electronBuild: 24210732, appRuntime: 0.659, appCoreServicesReady: false, appInitialized: false, activities: desktop_settings_initialize,desktop_settings_read,desktop_preauth_settings_load,desktop_settings_save,desktop_env_check,machine_activity_check_initialized,crash_reporting_initialize,create-interprocess-store,initNotificationManager,desktop_notification_window_initialized,desktop_compile_cache,desktop_endpoint_from_cache,desktop_pre_upn_settings_download,desktop_preupn_download_async,desktop_preauth_download_sync,desktop_env_fetched,desktop_preauth_download_async,desktop_win_sso,desktop_check_register_key,desktop_gpu_process_crashed,
    timeSinceActivity: -1, appStates: Started,SSOStart, timeSinceAppState: 0.01699995994567871, webAppStates: , timeSinceWebAppState: -1, diagnosticEvents: ua:desktop_settings_initialize,ua:desktop_settings_read,ua:desktop_preauth_settings_load,ua:desktop_settings_save,ua:desktop_env_check,ua:machine_activity_check_initialized,as:Started,ua:crash_reporting_initialize,ua:create-interprocess-store,ua:initNotificationManager,ua:desktop_notification_window_initialized,ua:desktop_compile_cache,ua:desktop_endpoint_from_cache,ua:desktop_pre_upn_settings_download,ua:desktop_preupn_download_async,ua:desktop_preauth_download_sync,ua:desktop_env_fetched,ua:desktop_preauth_download_async,ua:desktop_win_sso,as:SSOStart,ua:desktop_check_register_key,ua:desktop_gpu_process_crashed,
    timeSinceLastDiagnosticEvent: 0, timeSinceSecondLastDiagnosticEvent: 0.011999845504760742, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — GPU process crashed, not restarting app and fallback to software rendering. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — BluetoothLE Desktop: ble:radio-not-ready  

    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — error — GPU process crashed, not restarting app and fallback to software rendering. 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — notification manager: dom-ready event received 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 910cec8a-be9b-43bc-9227-279a666f9290, scenarioName: desktop_notification_window_initialized, name: desktop_notification_window_initialized, step:
    stop, sequence: 1, delta: 301, scenarioDelta: 301, elapsed: 835, stepDelta: 301, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_notification_window_initialized, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — notification manager: notification window ready 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Main Window Hide: loading window ready 
    Wed Feb 05 2020 09:30:53 GMT-0500 (Eastern Standard Time) <16328> — info — Loading window shown with focus due to first show 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: 26db4493-58aa-47c8-8b7f-dec1d5138f9c, Microsoft_ADAL_response_rtime: 810, Microsoft_ADAL_api_error_code: caa2000c, vdiMode:
    0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: SSO requires credential. Status: caa2000c. Attempting windows auth. 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — SSO requires credential. Status: caa2000c. Attempting windows auth. diag:1 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: fda60763-f2c9-4034-b89f-e51cc814e403, scenarioName: desktop_wia, name: desktop_wia, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed:
    1468, stepDelta: 0, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_wia, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:Login promise for online check 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:Response promise for online check success with retryAttempt=0 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — info — appOnlineSvc:background sync downloaded preauth settings 
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 386d1986-8c38-404b-be31-7b05d87da88c, scenarioName: desktop_preauth_settings_file_save, name: desktop_preauth_settings_file_save, step: start, sequence:
    0, delta: 0, scenarioDelta: 0, elapsed: 1690, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_preauth_settings_file_save, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 63f87a25-7e8f-4901-aab4-19f94f57cee7, scenarioName: desktop_preauth_download_sync, name: desktop_preauth_download_sync, step: stop, sequence: 1, delta:
    1087, scenarioDelta: 1087, elapsed: 1690, stepDelta: 1087, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_preauth_download_sync, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — retryAttempt: 0, coldboot: false, status: success, scenario: ffc13764-c258-4aab-aaf7-64cab352d239, scenarioName: desktop_preupn_download_async, name: desktop_preupn_download_async,
    step: stop, sequence: 1, delta: 1089, scenarioDelta: 1089, elapsed: 1691, stepDelta: 1089, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_preupn_download_async, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 386d1986-8c38-404b-be31-7b05d87da88c, scenarioName: desktop_preauth_settings_file_save, name: desktop_preauth_settings_file_save, step: stop, sequence:
    1, delta: 4, scenarioDelta: 4, elapsed: 1694, stepDelta: 4, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_preauth_settings_file_save, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 30fe235f-4845-40db-b09d-591e1cec8fa2, scenarioName: desktop_settings_save, name: desktop_settings_save, step: start, sequence: 0, delta: 0, scenarioDelta:
    0, elapsed: 2219, stepDelta: 0, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_settings_save, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:54 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 30fe235f-4845-40db-b09d-591e1cec8fa2, scenarioName: desktop_settings_save, name: desktop_settings_save, step: stop, sequence: 1, delta: 4, scenarioDelta:
    4, elapsed: 2223, stepDelta: 4, vdiMode: 0, eventpdclevel: 3, Scenario.Name: desktop_settings_save, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — error — ssoerr -Needs to do login window promise. Login failed with error:Error: 0�
    �: 
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — event — wiaError: {}, status: failure, scenario: fda60763-f2c9-4034-b89f-e51cc814e403, scenarioName: desktop_wia, name: desktop_wia, step: stop, sequence: 1, delta: 1547, scenarioDelta:
    1547, elapsed: 3015, stepDelta: 1547, vdiMode: 0, eventpdclevel: 2, Scenario.Name: desktop_wia, Scenario.Step: stop, Scenario.Status: failure,  
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — info — SSO requires credential. Status: caa2000c. Windows auth. caa90002 diag:1 
    Wed Feb 05 2020 09:30:55 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: SSO requires credential. Status: caa2000c. Windows auth. caa90002 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 13, Microsoft_ADAL_correlationId: b655a1db-7142-4442-bbfd-ba746cdd683b, Microsoft_ADAL_response_rtime: 796, Microsoft_ADAL_api_error_code: caa2000c, vdiMode:
    0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — https://api.spaces.skype.com: Login status caa2000c diag:1 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: Acq token failed with:caa2000c 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Showing login window. correlationId:b655a1db-7142-4442-bbfd-ba746cdd683b 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — status: abandoned, scenario: 5bbf49ae-7fb9-4329-8eb8-d4bd6e1a8d1e, scenarioName: desktop_app_load, name: desktop_app_load, step: stop, sequence: 1, delta: 3607, scenarioDelta:
    3607, elapsed: 3813, stepDelta: 3607, vdiMode: 0, eventpdclevel: 1, Scenario.Name: desktop_app_load, Scenario.Step: stop, Scenario.Status: abandoned,  
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Go ahead and log in. diag:0 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Go ahead and log in. 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — Login UI in progress for upn. diag:1 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — info — SSO: (Login Window) Login UI in progress. 
    Wed Feb 05 2020 09:30:56 GMT-0500 (Eastern Standard Time) <16328> — event — panelview: Panel.Type: loginWindow, Panel.Region: modal, Panel.LaunchMethod: login, DataBag.AuthStack: ADAL, Panel.ViewId: bc05acd9-a4ca-4c1e-805c-f49facb1a54c, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — emit status indicator state change from undefined to Unknown 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — Clearing taskbar overlay icon 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — Added Unknown (current state: undefined -> Unknown) 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — info — StatusIndicatorStateService initialized 
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — event — name: initialize_status_indicator, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:36 GMT-0500 (Eastern Standard Time) <16328> — event — panelaction: Action.Outcome: launch, Action.Gesture: click, Action.Scenario: openTrayIconMenu, Action.ScenarioType: other, DataBag.StatusIndicatorState: Unknown, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:32:44 GMT-0500 (Eastern Standard Time) <16328> — event — panelaction: Action.Outcome: launch, Action.Gesture: click, Action.Scenario: openTrayIconMenu, Action.ScenarioType: other, DataBag.StatusIndicatorState: Unknown, vdiMode: 0,
    eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — Microsoft_ADAL_api_id: 176, Microsoft_ADAL_correlationId: 74f1266a-78dd-42ea-924e-88b5532864fa, Microsoft_ADAL_response_rtime: 300052, Microsoft_ADAL_api_error_code: caa7000a,
    vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Could not login user — status: caa7000a diag:1 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — (Login Window) Could not login user — status: caa7000a 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — SSO Uber catch 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Set upn window user upn 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Modern authentication failed here, but you’ll still be able to sign in. Your status code is caa7000a. diag:0 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — adalsso:statusChanged to: Modern authentication failed here, but you’ll still be able to sign in. Your status code is caa7000a. 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Sso failed, updating cookie settings. Status:caa7000a diag:1 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — Fallback to webauth. Err:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: past-sso-success, eventInfo: true, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — AuthStateService: nativeWamEnabled:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: webAuthDisabled, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: indivRoadblockDisabled:false,modernAuthSucceeded:true, disableWebAuth:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: roadBlockEnabled:undefined,loginInAsGuest:false,IndividualRoadblock:true,isLoggedInAnonymously:false,isRigel:false 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Guest Tenant Id set to  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: webAuthDisabled, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Auth: indivRoadblockDisabled:false,modernAuthSucceeded:true, disableWebAuth:true 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — panelview: Panel.Type: oopsPage, Panel.Region: main, Panel.LaunchMethod: userInitiated, DataBag.OopsReason: auth_indiv_roadblock, vdiMode: 0, eventpdclevel: 2,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — warning — Loading oops page with id: 0 due to: auth_indiv_roadblock 

  • More errors

    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — name: desktop_auth_roadblock, reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having
    trouble completing the process, talk to your IT admin., oopsId: 0, vdiMode: 0, eventpdclevel: 3,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having trouble completing the process,
    talk to your IT admin., oopsId: 0, status: success, scenario: 7db982fc-f01b-4627-86b9-1af00309d9b6, scenarioName: desktop_auth_roadblock, name: desktop_auth_roadblock, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 303903, stepDelta: 0, vdiMode:
    0, eventpdclevel: 3, Scenario.Name: desktop_auth_roadblock, Scenario.Step: start, Scenario.Status: success,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — reason: auth_indiv_roadblock, errorCode: caa7000a, errorDescription: There’s a more permanent way to sign in to Microsoft Teams. If you’re having trouble completing the process,
    talk to your IT admin., oopsId: 0, status: success, scenario: 7db982fc-f01b-4627-86b9-1af00309d9b6, scenarioName: desktop_auth_roadblock, name: desktop_auth_roadblock, step: stop, sequence: 1, delta: 1, scenarioDelta: 1, elapsed: 303904, stepDelta: 1, vdiMode:
    0, eventpdclevel: 3, Scenario.Name: desktop_auth_roadblock, Scenario.Step: stop, Scenario.Status: success,  
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — emit status indicator state change from Unknown to AuthenticationFailed 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Setting the taskbar overlay icon — Sign in again 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — info — Added AuthenticationFailed (current state: Unknown -> AuthenticationFailed) 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — error — SSO: ssoerr — SSO failed. ErrorCode:authentication_failed Error Desc: Status: caa7000a 
    Wed Feb 05 2020 09:35:56 GMT-0500 (Eastern Standard Time) <16328> — event — status: success, scenario: 3dd8a248-b2c2-4774-a9cd-9f27f4ca9987, scenarioName: desktop_win_sso, name: desktop_win_sso, 

  • I received this same error code «caa82ee2″ but also the other related error code «4c7».  After much troubleshooting, it
    turned out that I did not have to mess with the settings on our DC at all.  I realized that I was signed in to Teams on a remote computer.  After I signed out of all devices, (then after waiting a while), I tried again while running Teams as admin,
    then Teams finally started up properly at that point!

    Note: this problem occurred as a result of a password policy update after which I was forced to change my password.

  • Has anyone figured this out yet? I also get all of the above and the not recognized error when trying to run the powershell command. Any help would be appreciated. The users are piling up now. Whats annoying is it is not all of them??? Why?

Источник

RRS feed

  • Remove From My Forums

  • Question

  • Can someone PLEASE tell me what the error code caa82ee2 means?   We get it everytime a user changes their password.  I cant find it online.

All replies

  • Hi jrauma,

    Can you provide more details about this error code message?

    Does this issue persist all the time?

    Can you account still log in to Teams after changing the password?

    You can get the details of the status code “caa82ee2” from the log files located in your machine. The location is: C:UsersusernameAppDataRoamingMicrosoftTeams.

    In my research, the error code may be related to ADFS configuration. Microsoft Teams requires Forms Authentication. When you deploy AD FS, Forms Authentication is not enabled for the intranet by default. For
    more details, you can refer to:

    https://support.microsoft.com/en-us/help/4041047/modern-authentication-fails-in-teams-status-code-4c7

    Besides, please make sure Teams application is the latest version. Sometimes if you are on an older version the authentication protocols can break until updated.

    Best Regards,
    Jimmy Yang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.

    • Proposed as answer by

      Friday, February 14, 2020 6:25 AM

  • Hi
    jrauma    ,

    Is there any update on this case?

    Please feel free to drop us a note if there is any update.

    Have a nice day!

    Best Regards,
    Sharon Zhao

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact
    tnsf@microsoft.com.

Источник

Microsoft Teams is a must-have in today’s workplace. Nothing is more inconvenient than receiving an error message such as ‘caa82ee2’ just when you need Microsoft Teams the most.

Microsoft Teams is a collaboration tool that was developed by Microsoft and it is available for Windows 10, Windows 10 Mobile, iOS, and other devices. It is known for being an easy to use collaboration tool that allows you to share documents, presentations and whiteboards.

Microsoft Teams is a great tool that can help you to collaborate with your colleagues. It has a lot of features that allow you to manage all your meetings and it can be used as a tool for remote support as well. The app can be used by anyone from all over the world.

Tech Support 24/7

Ask a Tech Specialist Online

Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.

Ask a Tech Specialist Online

On this page, you will find more information about the most common causes and most relevant solutions for the Microsoft Teams error ‘caa82ee2’. Do you need help straight away? Visit our support page.

Error information

How to solve Microsoft Teams error caa82ee2

We’ve created a list of solutions which you can follow if you want to solve this Microsoft Teams problem yourself. Do you need more help? Visit our support page if you need professional support with Microsoft Teams right away.

Tech Support 24/7

Ask a Tech Specialist Online

Connect with the Expert via email, text or phone. Include photos, documents, and more. Get step-by-step instructions from verified Tech Support Specialists.

Ask a Tech Specialist Online

Verified solution

There are many errors that can occur when you try to use Microsoft Teams. One of them is the Microsoft Teams Error Code caa82ee2. The cause of microsoft teams error code caa82ee2 is generally related to a mismatch between the device type of the computer and the profile or version of Microsoft teams installed on it.

The error code caa82ee2 indicates that the application on your computer cannot be located or that it is unable to access the registry database for your operating system.If you encounter this error code while installing or running a new version of Microsoft teams on your computer then you should check with your computer manufacturer to see if they have released any updates to correct this problem.

To fix this error, you need to try a few solutions.

In addition, you should check with Microsoft Support to see if there are any service packs or updates available for your specific product. The first thing to do is Download and install the latest version of Microsoft Teams on your computer.

Second solution is Use the windows features to uninstall Microsoft teams from your computer. To do this, click on the start button and then go to Programs > All Programs > Microsoft Teams > Uninstall . Once you have uninstalled the application, restart your computer.

Third, ​​Check with your computer manufacturer to see if they have released any updates to correct this problem. In addition, you should check with Microsoft Support to see if there are any service packs or updates available for your specific product.

This error may be caused by a mismatch between the device type of the computer and the profile or version of Microsoft teams installed on it. To resolve this issue, please download and install the latest version of Microsoft teams.

If none of these solutions works, you might need to contact Microsoft Support and ask them to fix the issue.

Have you found a solution yourself, but it is not in the list? Share your solution in the comments below.

Need more help?

Do you need more help?

Tech experts are ready to answer your questions.

Ask a question

Источник

0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии

А вот еще интересные материалы:

  • Яшка сломя голову остановился исправьте ошибки
  • Ятрогенная патология врачебные ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного исправьте ошибки
  • Ясность цели позволяет целеустремленно добиваться намеченного где ошибка
  • Microsoft teams код ошибки caa70007

    • ➤