Author: Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on http://www.ChicagoTech.net How to Install and Configure Windows, VMware, Virtualization and Cisco on http://www.HowToNetworking.com

Veeam backup: Failed to upload disk

Situation: The client has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Failed to upload disk.

Troubleshooting 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Troubleshooting 2: It could be the hard disk issue. Please run chkdsk: /f /x /r to check and fix it.

Troubleshooting 3: Modify SkipBadBlocks settings on Registry.

1. Open up regedit.
2. Locate the Path: HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup
3. Add the following new DWORD: SkipBadBlocks and change the value to 1.
4. Close regedit, open up the services.msc console, and then restart the Veeam Agent for Microsoft Windows service.

Troubleshooting 4: It could be system time issue. Quoted from Veeam website:

Cause

The Veeam Backup Service uses a system of timed leases to monitor the many processes it manages. Usually, this error involves a five minute lease for the VeeamAgent processes (Data Movers). When the Veeam Backup Service is operating normally, this lease is continually renewed. If the lease expires, the associated process is shut down.

Typically the lease will expire either because the system time has changed by several minutes, or because a problem communicating with the Veeam Backup Configuration Database has prevented the Veeam Backup Service from renewing the lease.

Solution

On VMware virtual machines, the VMware Tools will periodically synchronize the system time with the ESXi host. If the time on the host differs from the NTP server used by the Guest OS, the system time will repeatedly shift between the two different times. The best solution is to synchronize the time between the ESXi host, the Veeam Backup & Replication server and/or the domain controllers with the same source. If this is not possible, you could disable VMware Tools time synchronization on the Veeam Backup & Replication server.

Troubleshooting 5: Restarting Veeam services may fix the problem.

 

Veeam Backup: Shared memory connection was closed

Situation: Some users has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Shared memory connection was closed.

Troubleshooting 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Troubleshooting 2: It could be the Hard Disk issue. Please double check it or run chkdsk /f /r command to check and fix it.

Troubleshooting 3: In another case, the user uses a USN external drive to be the backup storage. We don’t recommend using external USB as a backup storage. However, if this is workstation and you have to use USB drive, you may try to upgrade the USB driver. Also, if the USB is FAT32 or exFAT format, it is not a good choice for a backup target. Perhaps, you can format as NTFS.

Troubleshooting 4: Run VSSadmin to check any errors? Please refer to this article:

Troubleshooting VSS Writers timeout or failed error

Troubleshooting 5: To fix it, follow these steps :
1) Open Backup & Replication
2) Open your properties (top left corner)
3) Network Traffic
4) Check the number near “Use multiple upload streams per job”. Endpoint need at least 3 streams to work.

If the RAM is not the issue, restarting Veeam services may fix the problem.

 

Veeam Backup: Unable to allocate memory for storage metadata bank

Situation: The client has Veeam backup to back up all their VMs on Microsoft Hyper-V. The backup failed with this error: Unable to allocate memory for storage metadata bank.

Resolution 1: It could be physical server low RAM. Please refer to this article for RAM requirement.

Resolution 2: If the RAM is not the issue, restarting Veeam services may fix the problem.

Resolution 3: Check the status of Windows update. If there is any windows update installed or pending for restart, please do so.

 

 

 

Integrated laptop camera issue with Microsoft Teams

Situation: The user has a problem to use Integrated laptop camera ion Microsoft Teams. he receives a message that my camera stops working frequently while on a Teams’ meeting. He doesn’t have the problem to use the camera on other apps. Also, external camera doesn’t have this issue.

Resolution 1: clear my Teams cache.

Resolution 2: Install Windows and Office latest updates.

Resolution 3: Install latest Camera driver.

Resolution 4: Repair Office 365.

 

Veeam Failed to call RPC function ‘InstallAndCreateSession’ with Code: 0x80131500

Situation: the client is running Veeam Backup v11. One of the Veeam backups has this warning: Unable to perform indexing because connection to the guest could not be established
Unable to perform guest file system indexing: Failed to call RPC function ‘InstallAndCreateSession’:
Cannot connect to VM [45a2a1d8-c9a5-42e3-bb7b-239f0d35b478] over PSDirect.
Failed to invoke func [Connect]:
Unknown error 0x80131500. Unknown error 0x80131500.
Failed to execute PowerShell command: The credential is invalid.;COM error: Code: 0x80131500.

Resolution: You may want to disable Enable guest file system indexing.

Or do nothing. Please refer to this article:

KB3179: Failed to call RPC function: Error code: 0x80131500 – KB3179: Failed to call RPC function: Error code: 0x80131500 (veeam.com)

Resolution 2: make sure PowerShell 2.0+ module is installed on top of Hyper-V host? (Server-Add Roles-Features).

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”