Problem description
Hyper-V VM backup fails with HYPERV3 error.
Cause
A change in Hyper-V Cluster or SCVMM credentials can cause this error.
Traceback
Agent Version 6.x and older agent:
[2020-04-13 20:02:18,885] [ERROR]
<_MainThread(MainThread)> Error <class
'inSyncLib.inSyncError.SyncError'>:LogonUser:
incorrectError Code : HYPERV3
(most recent call last):
File "agentPartnerProcess.pyc", line 84, in _process_request_start
File "agents\hyperv\hypervAgent.pyc", line 67, in process_backup_start
File "agents\hyperv\hypervBackup.pyc", line 77, in init
File "agents\hyperv\hypervBackup.pyc", line 236, in __validate_mgmt_entity
File "roboHyperVUtils.pyc", line 109, in validate_mgmt_entity
File "hypervCredsMgr.pyc", line 390, in validate
File "hypervCredsMgr.pyc", line 339, in _validate
File "inSyncLib\inSyncError.pyc", line 30, in raise_error
SyncError: LogonUser:The user name or password is incorrect. (#100090003 : 1326) (Error Code : HYPERV3)
Agent Version 7.x and newer agent:
[2025-03-09 03:11:47,841] [ERROR] <_MainThread(MainThread)> Test Credentials Failed with error: (1327, 'LogonUser', "Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.")
[2025-03-09 03:11:47,841] [ERROR] <_MainThread(MainThread)> SyncError: LogonUser:Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced.
[2025-03-09 03:11:47,841] [INFO] <_MainThread(MainThread)> Disabled fault scheck for backup
[2025-03-09 03:11:47,841] [INFO] <_MainThread(MainThread)> roboSyncer: scheck abort check is disabled
[2025-03-09 03:11:47,841] [INFO] <_MainThread(MainThread)> roboSyncer: Sending log to Phoenix server with message : 'Backup operation failed.'
[2025-03-09 03:11:47,934] [INFO] <_MainThread(MainThread)> Enabled fault scheck for backup
[2025-03-09 03:11:47,934] [ERROR] <_MainThread(MainThread)> HypervAgent: Hyperv backup failed: LogonUser:Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (#100090003 : 1327) (Error Code : HYPERV3)
Code : HYPERV3)
Resolution
Use the following command to update the credential of the affected Hyper-V host.
Agent Version 6.x and older agent:
Go to Command Prompt (cmd) and run it with administrative privileges.
In command prompt navigate to
C:\Program Files\Druva\Phoenix Agent\Run the below mentioned command.
Command:
PhoenixHyperVControl.exe set_credential --type <scvmm/cluster> --scvmm_fqdn <scvmm FQDN> --user <scvmm/cluster username> --password <scvmm/cluster password>Example:
PhoenixHyperVControl.exe set_credential --type scvmm --scvmm_fqdn=192.0.2.9 --user=exampledomain\user --password=Ex@mpleP@$$w0rd
Agent Version 7.x and newer agent:
Go to Command Prompt (cmd) and run it with administrative privileges.
In command prompt navigate to
C:\Program Files\Druva\EnterpriseWorkloads\Run the below mentioned command.
Command:
EnterpriseWorkloadsAgent.exe hyperv configure --type <scvmm/cluster/standalone> --scvmm_fqdn <scvmm FQDN> --user <username>Example:
EnterpriseWorkloadsAgent.exe hyperv configure --type cluster --user Domain\user_name
📝 Note
Do not use the following characters in the command:
Double quotes "
Single quotes '
Double back-slash \\
In case the above resolution steps does not work then follow the below steps to re-register the host and attempt to update the credentials as a workaround.
Agent Version 6.x and older agent:
Stop the Hybrid workloads Agent Client Service.
Rename the directory
C:\ProgramData\PhoenixtoC:\ProgramData\Phoenix.oldStart the Hybrid workloads Agent Client Service.
Follow the steps as mentioned in document to re-register a Hyper-V Host.
Agent Version 7.x and older agent:
Stop the Druva-EnterpriseWorkloads Service.
Rename the directory
C:\ProgramData\DruvatoC:\ProgramData\Druva.oldStart the Hybrid workloads Agent Client Service.
Follow the steps as mentioned in document to re-register a Hyper-V Host.