- Veeam Support Knowledge Base
- Troubleshooting Guest Processing Issues | "Test Now" or "Verify network connectivity and credentials"
Troubleshooting Guest Processing Issues | "Test Now" or "Verify network connectivity and credentials"
| KB ID: | 3225 |
| Product: |
Veeam Backup & Replication | 10 | 11 | 12 | 12.1 | 12.2 | 12.3 | 12.3.1 | 12.3.2 | 13 | 13.1 Veeam Agent for Microsoft Windows | 4.0 | 5.0 | 6.0 | 6.1 | 6.2 | 6.3 | 6.3.1 | 6.3.2 | 6.3.3 | 13 | 13.1 |
| Published: | 2020-07-23 |
| Last Modified: | 2026-04-30 |
Cheers for trusting us with the spot in your mailbox!
Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Oops! Something went wrong.
Please, try again later.
This article's primary focus is on traditional credentials-based authentication.
For environments using a Group Managed Service Account (gMSA), please review the User Guide first to ensure you are familiar with all the Requirements and Limitations of gMSA usage.
Challenge
Note: The solutions to RPC and Win32 errors apply to the Credentials Tester when used with vSphere, Hyper-V, and Veeam Agent for Microsoft Windows. The VIX Connection issues section of this article is related to VMware only.
Note: Prior to Veeam Backup & Replication v13, the button was simply labeled "Test Now".
Regarding Warning in VMware Environments
In VMware environments, Veeam Backup & Replication can use two methods to connect to a guest: RPC or VIX. If RPC is testing successfully, it is generally acceptable for the VIX test to fail as it will not likely be used. However, if it is desired to have VIX succeed, please see the relevant section at the bottom of the solutions section.
Solution
Important notes about the Account shown in the error:
- In some environments, there may be multiple entries in the Credentials Manager for the same account. It is advisable to review the credentials manager and remove duplicate entries. See: https://www.veeam.com/kb3224
- If the account specified in the error differs from what is configured on the Guest Processing tab, click the "Guest OS credentials for individual machines" link on the Guest Processing tab to see if specific credentials have been set.
- For VM Backup and Replication jobs (VMware or Hyper-V), the account used to connect to the Guest is always the same as the account used to log in to the SQL instance. So the Credentials Tester can show good for a SQL server, but the SQL-related tasks (Truncation, Transaction Log Backup) may fail if the account being used does not have the correct permissions in SQL.
If the error you see is not listed here and you need help, please open a support case.
Testing admin share accessibility via RPC Errors
The following are a few of the possible errors that may be seen in the Guest Credentials Test in the line after "Testing admin share accessibility via RPC"
Win32 error:The network path was not found.; Code: 53
Cannot connect to the host's administrative share. Host: [DC01]. Account: [lab\veeambu].;Win32 error:The network path was not found.; Code: 53;
This issue is covered in https://www.veeam.com/kb1230
Win32 error:Access is denied.; Code: 5;
Cannot connect to the host's administrative share. Host: [DC01]. Account: [HSVMv2\veeam].;Win32 error:Access is denied.; Code: 5;
"Access is denied" may occur if either:
- The account used to initiate Guest Processing is not a member of the Administrators group on the protected machine.
For more information, review the Guest Processing Required Permissions. - The account used to initiate Guest Processing is a local account other than the Administrator account (local accounts other than the Administrator account are blocked from remote logon by default).
The issue of remote login using local accounts is covered in detail here: https://www.veeam.com/kb4185.
The user account used to connect to the remote machine must work with the default UAC remote restrictions, meaning that the account must be either:- A domain account that is a member of the Local Administrators group.
- The built-in account named Administrator.
Note: The built-in Administrator account may fail if the "User Account Control: Admin Approval Mode for the Built-in Administrator account" policy is enabled on the remote machine.
Win32 error:The user name or password is incorrect.; Code: 1326;
Cannot connect to the host's administrative share. Host: [DC01]. Account: [lab\veeambu].;Win32 error:The user name or password is incorrect.; Code: 1326;
Check that the account specified can connect to the Host specified in the error. If that account should be able to connect, open the Credentials Manager in Veeam Backup & Replication and update the password.
Win32 error:The trust relationship between this workstation and the primary domain failed.; Code: 1789;
Cannot connect to the host's administrative share. Host: [DC01]. Account: [lab\veeambu].;Win32 error:The trust relationship between this workstation and the primary domain failed.; Code: 1789;
Test logging into the Host specified in the error with the Account specified in the error. Likely the same error will occur.
To correct this error, repair the trust relationship in Active Directory.
Connecting to guest OS via VIX Errors
VIX is a network-less alternative method for Veeam Backup & Replication to connect to a guest. This functionality only exists when processing a VMware Virtual Machine.
Cannot upload file to admin share
Connecting to guest OS via VIX Error: Cannot upload file to admin share [C:\Windows]. Could not create guest directory [C:\Windows\VeeamGuestHelpersTest] Could not create guest [vm-431254] directory [C:\Windows\VeeamGuestHelpersTest] Could not invoke guest operation Unable to access file C:\Windows\VeeamGuestHelpersTest
This issue is covered in https://www.veeam.com/kb1788
Could not validate ... credentials for guest
Connecting to guest OS via VIX Error: Cannot connect to host [vcsa.lab] over web services. Login: [vsphere.local\administrator]. Guest Login: [lab\veeambu]. Could not initiate Web Service connection Could not initiate guest virtual machine [vm-431254] with user [lab\veeambu] Could not validate host [https://vcsa.lab/sdk] credentials for guest [vm-431254] user [lab\veeambu] Could not invoke guest operation A general system error occurred: vix error codes = (1, 0).
This error means that when Veeam attempted to connect to the guest via VIX the account provided was unknown to the guest.
Possible causes include:
- password for the account is wrong.
- account specified does not have ability to connect to the guest.
- account being used is a domain account and the guest is not on the domain
- trust relationship between the guest and the domain is broken
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.