Connection issues in sign-in after update to Office 2016 build 16.0.7967 – Office 365

Connection issues in sign-in after update to Office 2016 build 16.0.7967 – Office 365
  • Article
  • 7 minutes to check out
  • Applies to:
    Microsoft 365 Apps for business, Office 2016

Overview

This short article consists of info about a brand-new authentication structure for Microsoft Office 2016.

By default, Microsoft 365 Apps for business (2016 variation) utilizes Azure Active Directory Authentication Library (ADAL) framework-based authentication. Beginning in construct 16.0.7967, Office utilizes Web Account Manager (WAM) for sign-in workflows on Windows constructs that are behind 15000 (Windows 10, variation 1703, develop 15063.138).

General assistance

If you experience authentication problems in Office application on Windows 10, we advise to do the following actions:

  • Update Office items to the current construct for your channel according to Update history for Microsoft 365 Apps for business (noted by date)
  • Make sure that you are running any of the following Windows develops:
    • Any construct for Windows 10, variation 1809 or a later variation
    • 17134677 or later on develops for Windows 10, variation 1803
    • 16299461 or later on develops for Windows 10, variation 1709
    • 150631112 or later on constructs for Windows 10, variation 1703

Symptoms

You might experience among the following signs after you upgrade to Microsoft Office 2016 construct 16.0.7967 or a later variation on Windows 10.

Symptom 1

When the general network is dealing with your gadgets, Office applications might experience connection problems. You might see a message that looks like the following:

You’ll require the web for this.
We could not link to among the services we required to sign you in. Please inspect your connection and attempt once again.
0xCAA70007

Screenshot of the error message shows that you will need the internet for this.

To identify whether you’re experiencing this type of concern, follow these actions:

  1. Make sure that you’re running Office construct 16.0.91262259 or a later construct. (The most current construct on your channel is fantastic. See the basic assistance in the Overview area.)
  2. Open Event Viewer.
  3. Go to Applications and Services Logs > Microsoft > Windows > AAD
  4. In the Operational logs, find messages from XMLHTTPWebRequest that have the following pattern:
     0x? aa7????, 0x? aa8????, 0x? aa3????, 0x102, 0x80070102
  5. Make sure that the time of these mistakes is associated with the time when you in fact had an Internet connection. This is not a periodic network problem due to the fact that of the loss of a Wi-Fi connection or a wake-up after hibernation and initialization of the network stack.

Then, to identify whether your concern is because of network environment or regional firewall/antivirus software application, follow these actions:

  1. Open Edge (not Internet Explorer) and go to https://login.microsoftonline.com Navigation ought to arrive at https://www.office.com or your business’s default landing page. If this stops working, the problem remains in a network environment or regional firewall/antivirus software application.
  2. Open Edge (not Internet Explorer) in InPrivate mode and go to https://login.microsoftonline.com After you get in qualifications, navigation must arrive on https://www.office.com or your business’s default landing page. If this stops working, the problem remains in a network environment or regional firewall/antivirus software application.

To solve this concern, make certain that your regional firewall software, anti-virus software application, and Windows Defender do not obstruct the following AAD WAM plug-in procedures that took part in token acquisition:

C: Windows SystemApps Microsoft.AAD.BrokerPlugin _ cw5n1h2txyewy Microsoft.AAD.BrokerPlugin.exe

C: Windows System32 backgroundTaskHost.exe

Note The PackageFamilyName of the plugin is the following:

Microsoft.AAD.BrokerPlugin _ cw5n1h2txyewy

Also, ensure that your network environment does not obstruct the main location:

https://login.microsoftonline.com/

Note This main address covers lots of IP addresses (and numerous services). A few of these addresses might be obstructed in the environment for no great factor, which triggers periodic issues in some gadgets while other gadgets work fine.

Symptom 2

When you attempt to open or conserve a file in Microsoft SharePoint Online, OneDrive for Business, or SharePoint, or you attempt to integrate e-mail messages or your calendar in Microsoft Outlook, you’re triggered for qualifications. After you get in qualifications, you’re triggered once again. This concern might happen for the following factors:

  • The Trusted Platform Module (TPM) chip or firmware is malfunctioning. Windows utilizes the TPM chip to secure your qualifications. The chip might end up being damaged or reset in some conditions. To identify whether you are experiencing this type of concern, follow these actions:
    1. Open Event Viewer.
    2. Go to Applications and Services Logs > Microsoft > Windows > AAD
    3. In the Operational logs, find the mistakes that show the following pattern: 0x?028????, 0x?029???? or 0x?009????

    To prevent this concern in future, we advise that you upgrade the TPM firmware.

    For Windows 10, variation 1709 or later on variations: The os immediately finds scenarios that relate to TPM failures and offers a user healing procedure that ought to happen instantly. If this procedure does not happen immediately, we suggest that you utilize this manual healing approach.

    For Windows 10, variation 1703: An automated procedure is attended to Hybrid Azure advertisement sign up with. No automated procedure is attended to other environment setups. If the Hybrid Azure advertisement sign up with procedure does not happen instantly, we suggest that you utilize this manual healing approach.

  • A gadget is disabled by the user, the Enterprise administrator, or a policy since of a security issue or by error. To identify whether you are experiencing this problem, follow these actions:
    1. Open Event audience.
    2. Go to Applications and Services Logs > Microsoft > Windows > AAD
    3. In the Operational logs, find the following message:

    Description: AADSTS70002: Error verifying qualifications. AADSTS135011: Device utilized throughout the authentication is handicapped.

    To solve this problem, we suggest that the Enterprise administrator make it possible for the gadget in Active Directory or Azure Active Directory (Azure Advertisement). For details about how to handle gadgets in Azure advertisement, see the Device management jobs area of the “How to handle gadgets utilizing the Azure website” subject.

  • The Enterprise administrator or a policy erased a gadget due to the fact that of a security factor or by error. To confirm that you are experiencing this concern, follow these actions:
    1. Open Event audience.
    2. Go to Applications and Services Logs > Microsoft > Windows > AAD
    3. In the Operational logs, find the following message:

    Description: AADSTS70002: Error confirming qualifications. AADSTS50155: Device is not verified.

    To fix this concern, we advise that you recuperate the gadget by utilizing the manual healing approach. Note If no one on the Enterprise erased the gadget, please submit an assistance ticket and offer an example of a gadget that is not recuperated.

Manual healing

To do a manual healing of the computer system, follow the suitable actions, depending upon how the gadget is signed up with to the cloud (Hybrid Azure advertisement sign up with, Add a work account, or Azure advertisement sign up with).

Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: