Set-Mailbox : Active Directory operation failed. This error is not retriable. Additional information: Insufficient access rights

 Issue : 

When I tried to convert a user mailbox in to Shared in On-prem environment I got the error.

Error : 

Set-Mailbox : Active Directory operation failed on DC01.DC.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.

Active directory response: 00002098: SecErr: DSID-031514A0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

 I have tried many blogs which are suggested to add the user under Exchange Trusted Subsystem or Enable/Disable the inheritance and few suggested to check the working users and copy the permission under non-working user's Security tab.

 Solution:

However, none of the solution had helped me and I tried to add the affected user under RSA and ISA servers Security group and issue fixed.

The specified user logon name already exists in the enterprise

 I have a Azure sync issue for a user due to it has other language character (for examplw German's ü) we tried to change character to u instead of ü, however we got an below error,

The specified user logon name already exists in the enterprise. Specify a new one, either by changing the prefix or slecting a different suffix from the list.

 

Tried find the user with character u (we thought there is another user with this name already) and ensured that, there is no such user(s). 

Seems the Windows OS settings could not identify the both characters are different and it always says above error.

Also tried customer LDAP query and result display only affected the user. 

(&(objectCategory=person)(objectClass=user)(sAMAccountName=logumm))

So, we tried to rename the user with random number, like  logümm121 and renamed to logumm. It works fine and AAD synced the user to Azure portal.

The source detected that the destination failed to resume - Veeam Instant recovery

When we are trying to move a VM using Instant reovery and it fails with below error.

Relocating VM Error: A general system error occurred: The source detected that the destination failed to resume.
(An error occurred restoring the virtual machine state during migration. , Failed to receive migration.)

Here are findings from the Log:

[22.02.2023 14:49:33] <11> Info [CQuickMigrationImpl] Calculated QM path: [[CQuickMigrationPath]
[22.02.2023 14:49:33] <11> Info Path: 'Relocate'
[22.02.2023 14:49:33] <11> Info Errors: [[CQuickMigrationErrors]
[22.02.2023 14:49:33] <11> Info QmType: 'VMotion'
[22.02.2023 14:49:33] <11> Info Errors: [No errors.]
[22.02.2023 14:49:33] <11> Info ]

Veeam uses the VMotion type to migrate the VM. And It fails with:

[22.02.2023 17:04:26] <22> Error Relocating VM
[22.02.2023 17:04:26] <22> Error Relocate VM failed, vmRef 'vm-947169', newHostRef 'host-221', newResPool 'resgroup-82' (System.Exception)
[22.02.2023 17:04:26] <22> Error A general system error occurred: The source detected that the destination failed to resume.
[22.02.2023 17:04:26] <22> Error (An error occurred restoring the virtual machine state during migration. , Failed to receive migration. ) (Veeam.Backup.ViSoap.ViServiceFaultException)
[22.02.2023 17:04:26] <22> Error VimApi.SystemError
[22.02.2023 17:04:26] <22> Error Relocate VM failed, vmRef 'vm-947169', newHostRef 'host-221', newResPool 'resgroup-82' (System.Exception)
[22.02.2023 17:04:26] <22> Error A general system error occurred: The source detected that the destination failed to resume.
[22.02.2023 17:04:26] <22> Error (An error occurred restoring the virtual machine state during migration. , Failed to receive migration. ) (Veeam.Backup.ViSoap.ViServiceFaultException)
[22.02.2023 17:04:26] <22> Error VimApi.SystemError
[22.02.2023 17:04:26] <22> Error [CQuickMigrationImpl] Failed to migrate VM

Cause : 

This issue occurs due to incorrect datastore information or out-of-date virtual hardware.

Solution : 

We tried some solutions given by Veeam and VMware and could not fix and found the our Vcetner which is used to move as destination is 5.5 version.

So moved to another location which has update to version of ESXi/Vcenter host and fixed.