{"id":111,"date":"2017-09-21T12:57:48","date_gmt":"2017-09-21T12:57:48","guid":{"rendered":"https:\/\/www.intrigua.com\/scenario\/?p=111"},"modified":"2017-10-03T10:14:31","modified_gmt":"2017-10-03T10:14:31","slug":"error-signing-in-to-office-365","status":"publish","type":"post","link":"https:\/\/www.intrigua.com\/scenario\/error-signing-in-to-office-365\/","title":{"rendered":"How to Fix Error in Signing into Office 365 Perfectly"},"content":{"rendered":"

At the point when a client tries to sign into a Microsoft cloud service, for example, Office 365 from a sign-in website page whose URL begins with “https:\/\/login.microsoftonline.com\/login.srf,” the client gets an error message and can’t sign in.<\/p>\n

Here is the case of an error message that the user may get:
\nSorry, but we’re having trouble signing you in. Please try again in a few minutes. If this doesn’t work, you might want to contact your admin and report the following error: 80041034<\/em>.<\/strong><\/p>\n

Problem in Signing into Office 365\u2013Major Cause<\/h2>\n

This issue may happen when one of the below-given conditions is valid:<\/p>\n

    \n
  • When the UPN has been transformed from its original value. A client’s UPN was upgraded, and old sign-in data was stored on the Active Directory Federation Services (ADFS) server.<\/li>\n
  • The cases that are set up in the depending party trust with Azure Active Directory (Azure AD) return surprising information. This conduct may happen when the cases that are connected with the depending party trust are physically altered or expelled.<\/li>\n<\/ul>\n

    Can’t Sign in to Office 365 Account Issue\u2013Solution<\/h2>\n

    Solution 1:<\/strong><\/p>\n

    On a Client PC that has the Azure Active Directory Module for Windows PowerShell introduced, take after these strides:<\/p>\n

      \n
    1. Click Start, Go to All Programs, click Windows Azure Active Directory, right-click Windows Azure Active Directory Module for Windows PowerShell, and afterward click Run as Administrator.<\/li>\n
    2. Execute the following command Next.
      \n
      \n connect-MSOLService <\/strong><\/p>\n

      Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]<\/strong><\/p>\n

      [Note<\/strong>: In this command, [CurrentUPN] represents the user’s current user principal name (UPN), and [NewUPN]represents the user’s UPN that has a domain suffix that changed to the initial onmicrosoft.com domain.]<\/li>\n

    3. Exit the Azure Active Directory Module for Windows PowerShell.<\/li>\n
    4. Now Open the Azure Active Directory Module for Windows PowerShell once more, and after that run, the below-specified commands and press Enter after each command:
      \n
      \nconnect-MSOLService<\/strong><\/p>\n

      <\/strong>Set-MsolUserPrincipalName -UserPrincipalName [CurrentUPN] -NewUserPrincipalName [NewUPN]<\/strong><\/p>\n

      [Note<\/strong>: In this command,\u00a0[CurrentUPN]\u00a0represents the UPN of the user after you run the command in step 2, and[NewUPN]\u00a0is the original UPN.]<\/li>\n<\/ol>\n

      Solution 2:<\/strong><\/p>\n

      The user can also try temporarily disabling Local Security Authority (LSA) credential caching on your AD FS servers.<\/p>\n

        \n
      1. Log in to each ADFS servers and follow the steps:
        \nClick\u00a0Win +R<\/strong>\u00a0or go to Start >> Run. Enter\u00a0regedit<\/strong>\u00a0to open registry editor.<\/li>\n

         
        \n\"image1\"
        \n <\/p>\n

      2. Navigate to following registry Key
        \nHKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa<\/strong><\/li>\n

         
        \n\"image2\"
        \n <\/p>\n

      3. Press right click on\u00a0Lisa<\/strong>, then select\u00a0New<\/strong>\u00a0>\u00a0DWORD (32 bit)<\/strong><\/li>\n

         
        \n\"image3\"
        \n <\/p>\n

      4. Put\u00a0LsaLookupCacheMaxSize<\/strong>\u00a0as the value name<\/strong>.<\/li>\n

         
        \n\"image4\"
        \n <\/p>\n

      5. Select\u00a0Modify<\/strong>\u00a0after Right click on LsaLookupCacheMaxSize.<\/li>\n

         
        \n\"image5\"
        \n <\/p>\n

      6. Make Sure that the\u00a0Value data<\/strong>\u00a0is set to 0, thereafter select ok.<\/li>\n

         
        \n\"image6\"
        \n <\/p>\n

      7. Now try that the user can sign in successfully, once they can login, it is recommended to delete the key we have created so far. Right-click on the key and select\u00a0Delete<\/strong>.<\/li>\n
      8. Reboot<\/strong>\u00a0all ADFS servers in your environment.<\/li>\n<\/ol>\n

        Conclusion<\/h3>\n

        The user can use any of the above-mentioned solutions for resolving “Error in Signing into Office 365” issue very easily. The discussed manual methods will help you troubleshoot the error efficiently as these are the solutions for two basic cause of the problem. <\/p>\n","protected":false},"excerpt":{"rendered":"

        At the point when a client tries to sign into a Microsoft cloud service, for example, Office 365 from a sign-in website page whose URL begins with “https:\/\/login.microsoftonline.com\/login.srf,” the client gets an error message and can’t sign in. Here is the case of an error message that the user may get: Sorry, but we’re having […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-111","post","type-post","status-publish","format-standard","hentry","category-ms-office-365"],"_links":{"self":[{"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/posts\/111","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/comments?post=111"}],"version-history":[{"count":15,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/posts\/111\/revisions"}],"predecessor-version":[{"id":141,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/posts\/111\/revisions\/141"}],"wp:attachment":[{"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/media?parent=111"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/categories?post=111"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.intrigua.com\/scenario\/wp-json\/wp\/v2\/tags?post=111"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}