Note: While this article is targeted at VMware environments, because most of the errors are generic Windows OS errors the solutions to RPC and Win32 errors are applicable to the Credentials Tester when used with Hyper-V and Veeam Agent for Windows.
When using the 'Test Now' feature on the Guest Processing tab of a job an error or warning is observed.
In VMware environments Veeam Backup & Replication is able to use two methods to connect to a guest, RPC and VIX. If RPC is testing successfully, it is generally acceptable for the VIX test to fail as it will not likely be used. If it is desired to not have this fail please see the relevant section at the bottom of the solutions section.
Important note about the Account you may see in the error:
This is not an exhaustive list of potential errors, if you have an error not listed here please use the "Request New Content" button at the bottom of this article to notify Veeam Support.
If the error you are seeing is not listed here and you need help, please open a support case.
The following is a few of the possible errors which may be seen in the Guest Credentials Test in the line after "Testing admin share accessibility via RPC"
Right-click on the line item and copy it to the clipboard so that it can be pasted somewhere else to see the full error.
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
Cannot connect to the host's administrative share. Host: [DC01]. Account: [HSVMv2\veeam].;Win32 error:Access is denied.; Code: 5;
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 is able to 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.
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.
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.
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
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: