Can’t login Office 365 with error code: 53004

Situation: A user can’t login Office 365 with error code: 53004.

Troubleshooting:

  1. Login Azure portal.
  2. Go to Azure Active Directory.

3. Click Security on the left pane.

4. Click on Multifactor authentication.

5. Click on Block/Unlock users.

6. Highlight the user who is blocked and click on Unlock.

Also refer to these posts:

Fixing “Your organization doesn’t allow you to update your password on this site”

Fixing “Your sign in was successful but does not meet the criteria to access this resource”

Office 365: Your sign-in was blocked

Situation: When attempting to login Office 365, you may receive this message: “Your sign-in was blocked”.

Troubleshooting:

  1. Login Azure portal.
  2. Go to Azure Active Directory.

3. Click Security on the left pane.

4. Click on Multifactor authentication.

5. Click on Block/Unlock users.

6. Highlight the user who is blocked and click on Unlock.

Also refer to these posts:

Fixing “Your organization doesn’t allow you to update your password on this site”

Fixing “Your sign in was successful but does not meet the criteria to access this resource”

 

 

Veeam: Can’t remove Backup repository

Situation: When attempting to remove a Backup repository, you may receive this message: Backup is used for configuration backup.

Troubleshooting: 1. If one Backup is using the Backup repository, delete the backup job if you don’t need it or switch to another Backup repository first.

2. If the Backup repository is default Backup repository, switch to another Backup repository by following these steps:

  • From the main menu, select Configuration Backup.

  • Switch the Backup repository.

 

 

 

 

Veeam Backup: The timeout period elapsed prior to completion of the operation or the server is not responding

Situation: When upgrading Veeam v9.5 to V11, the client has an issue with SQL 2016 database. They re-installed it by changing the SQL instant name from VeeamBackup to VeeamBackup2. The installation was successful.

However, they can’t create a backup with The timeout period elapsed prior to completion of the operation or the server is not responding message.

Troubleshooting: Changed the database name back to VeeamBackup instead of VeeamBackup2. To do that, open Veeam Backup and Replication Database Connection Settings.

 

Veeam Backup: Execution Timeout Expired

Situation: When upgrading Veeam v9.5 to V11, the client has an issue with SQL 2016 database. They re-installed it by changing the SQL instant name from VeeamBackup to VeeamBackup2. The installation was successful.

However, they can’t create a backup with Execution Timeout Expired message.

Troubleshooting: Changed the database name back to VeeamBackup instead of VeeamBackup2. To do that, open Veeam Backup and Replication Database Connection Settings.

 

Veeam Backup: The wait operation timed out

Situation: When upgrading Veeam v9.5 to V11, the client has an issue with SQL 2016 database. They re-installed it by changing the SQL instant name from VeeamBackup to VeeamBackup2. The installation was successful.

However, they can’t create a backup with The wait operation timed out.

Troubleshooting: Changed the database name back to VeeamBackup instead of VeeamBackup2. To do that, open Veeam Backup and Replication Database Connection Settings.

 

GloabProtect VPN Client can’t ping each other

Situation: Since WFH, more users WFH. However, VPN users can’t call each other using Softphone.

Resolution 1: Make sure VPN client can ping each other. If not, make sure GloablProect has VPN route setup correctly. Go to Network>GloablProtect>Gateways>Agent>Client Settings. in our example, 10.144.0.0/16 is VPN Client IP Pool.

Resolution 2: Make sure you have VPN Inbound and Outbound policy under Policy>Security. For example

 

 

Fixing Windows Update Error 0X800F0982

Situation: When installing Windows update, you may receive this error: Error 0X800F0982.

 

Resolution 1: Running the Windows Update Troubleshooter

tart by opening up a Run dialog box by pressing Windows key + R. Next, inside the text box, type “ms-settings-troubleshoot” and press Enter to open up the Troubleshooting tab of the Settings app.

2. Resetting the Windows Update component and Clear the SoftwareDistribution Folder

  1. Run Command Promopt.
  2. Run these commands;
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

If ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old

commands don’t work, you can delete them from C:\Windows

3. Force the installation of the update via Powershell

Run this command:

wuauclt.exe /UPDATENOW

4. Start the Windows Modules Installer Service

Start the Windows Modules Installer Service by running this command:

‘SC config trustedinstaller start=auto’

Then restart the computer and try to install the update again