Error when backup domain controler

[Bristolvm]

Hi team,
I try to backup my virtual vmware domain controler in a backup job with enable application-aware processing.

Code: Select all

9/17/2026 11:38:33 AM :: Using guest interaction proxy Backup02 (Same subnet)  
9/17/2026 11:38:38 AM :: Failed to inject guest runtime components, failing over to guest agent connection  
9/17/2026 11:38:50 AM :: Failed to connect to guest agent, failing over to guest runtime components through VIX  
9/17/2026 11:52:36 AM :: Failed to inject guest runtime components through VIX, failing over to guest agent through VIX  
9/17/2026 11:54:05 AM :: Failed to inventory guest system: Veeam Guest Agent is not started  
9/17/2026 11:54:05 AM :: Failed to prepare guest for hot backup. Error: Failed to connect to guest agent. Errors:
9/17/2026 11:54:07 AM :: Error: Failed to connect to guest agent. Errors:
'Cannot connect to the admin share. Host:  [DC02.kusior.local]. Account: [KUSIOR\Svc_Veeam].
Win32 error: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.
 Code: 1327
Cannot connect to the admin share. Host:  [10.184.16.20]. Account: [KUSIOR\Svc_Veeam].
Win32 error: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.
 Code: 1327
'  
9/17/2026 11:54:08 AM :: Processing finished with errors at 17/09/2026 11:54:08  

Do you have an idea ?
Thanks

Regards,

[david.domask]

Hi Bristolvm,

As it's a technical issue, you must open a Support Case as per the forum rules (and as noted when creating topics)

We cannot meaningfully troubleshoot technical issues over the forums, so a Support Case is required. Only post on technical issues once the case has concluded and only if you have questions / comments / requests based on the conclusion to the case.

Also while it may be tempting to analyze the Win32 error above that tells your account was rejected from sign-in, there's a bit of a quirk in how the error in the Job Statistics window returns failures for Guest Processing; Veeam has multiple ways of connecting to the GuestOS to deploy the Guest Processing Agents and you can see how it tries multiple methods to reach the GuestOS; thing is, if all methods fail, only the first failure is returned in the job statistics window, and that may not be the method you've configured for connecting.

Point is, start with a Support case as per the forum rules.