Office365 - 'Sorry, we are having temporary server issues'

califauna

Member
Joined
Aug 5, 2019
Posts
14
I have an Office365 subscription through university. About 5 months ago I starting getting a pop-up message when trying to log in to Office365 apps: 'Sorry, we are having temporary server issues'.
This prevents any saving, or writing, or editing of documents.
I have tried the following recommended steps:
  1. Resetting Internet Explorer's settings in the 'Advanced' tab of that menu.
  2. Looking for Office credentials in the windows credentials manager (found via control panel) and deleting them.
  3. Logging out of the account in Office (for some reason it was saying I was logged in in the top right of the Office window, even though it was also asking me to log in).
  4. Uninstalling and reinstalling. Repeating the process using the 'SetupProd_OffScrub.exe' uninstall and repair tool from Windows.
Can anyone help diagnose the problem?
 
Hi,

I think you are mixing things!

On the first part you mention Office365 apps, those are the Office applications that can be used using any web browser from any computer/device without anything installed (Office related), trying with a different browser or on a different computer, its a good step to find if something is wrong with your account or something on the computer.

The steps 2 to 4 apply essentially when you have Office 365 installed on the computer and you can use it totally off-line, the program only need to be activated one time and it will automatically contact the Microsoft activation servers from time to time to check if the license continues valid.
 
The following 2 links may be tried :


"We had trouble getting the featured templates and can't show them right now" error in Office 365 and Pro Plus 2016



Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows

To fix this issue, run the Easy fix tool. The tool adds support for the DefaultSecureProtocols registry entry. This enables the system administrator to specify which SSL protocols should be used when the WINHTTP_OPTION_SECURE_PROTOCOLS flag is used.

This fix can also enable certain applications that were built to use the ‘’WinHTTP’’ default flag to use the newer TLS 1.2 or TLS 1.1 protocols natively without having to use application updates.

The Easy fix also adds the secure protocols at the following registry location to help enable TLS 1.1 and 1.2 for Internet Explorer.

From the "blue link" above, download the tool, Easy Fix, Install and execute.
That should fix the problem
 
Internet Explorer, Options, Advanced, Ensure TLS 1.0, 1.1, 1.2 ect. are all ticked and try again, if anyone else encounters the issue.. This resolved it for me, GPO then created to enable in our RDS environment.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top