connecting to guest os via vix failed.

VMware specific discussions

connecting to guest os via vix failed.

Veeam Logoby Kas_Tigar » Thu Jan 29, 2015 3:09 pm

Hi. I am new to veeam and have a strange issue. Trying to go with guest processing with Windows Server 2012 or 2008 VM, I am getting the follow:
- connecting to guest os via RPC successful
- connecting to guest os via vix failed. Failed to open VM (datatore/vmx file). VIX Error: there was an error in communication code 14010

I do not understand what the problem is.
Please help.
Thanks!
Kas_Tigar
Influencer
 
Posts: 13
Liked: 2 times
Joined: Thu Jan 29, 2015 9:18 am

Re: connecting to guest os via vix failed.

Veeam Logoby Shestakov » Thu Jan 29, 2015 3:20 pm

Hi,
According to the error code, looks like you have a problem with a name resolution. Have you tried a relevant VMware KB?
If it doesn`t work, please contact Veeam technical support.
Thanks.
Shestakov
Veeam Software
 
Posts: 4842
Liked: 393 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: connecting to guest os via vix failed.

Veeam Logoby Kas_Tigar » Thu Jan 29, 2015 3:28 pm

Ok, thanks! I will check this.
Kas_Tigar
Influencer
 
Posts: 13
Liked: 2 times
Joined: Thu Jan 29, 2015 9:18 am

Re: connecting to guest os via vix failed.

Veeam Logoby Shestakov » Thu Jan 29, 2015 3:49 pm

Let me know if it works. Otherwise, please provide your support case number once you contact the support team.
Thanks.
Shestakov
Veeam Software
 
Posts: 4842
Liked: 393 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: connecting to guest os via vix failed.

Veeam Logoby MAA » Thu Apr 30, 2015 2:25 pm

I also have this issue.

:: Connecting to guest OS via VIX, user DOMAIN\veeam Error: Cannot connect to host [a.b.c.d] over VIX. Login: [DOMAIN\veeam]. Guest Login: [DOMAIN\veeam].
Failed to login to VM: [[datastore] server01/server01.vmx]. User: [DOMAIN\veeam].
VIX Error: Authentication failure or insufficient permissions in guest operating system Code: 3015


(DOMAIN\veeam is Domain Admin and vCenter Admin)
MAA
Enthusiast
 
Posts: 38
Liked: never
Joined: Sat Apr 27, 2013 12:10 pm

Re: connecting to guest os via vix failed.

Veeam Logoby foggy » Thu Apr 30, 2015 2:39 pm

Check whether credentials are entered correctly and contact technical support.
foggy
Veeam Software
 
Posts: 14716
Liked: 1075 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: connecting to guest os via vix failed.

Veeam Logoby dellock6 » Thu Apr 30, 2015 3:53 pm

Be careful about which credentials you use: this mode has a limitation that "classic" mode (network-based) doesn't have: you either need to disable UAC or use exactly the "well-known" administrator accounts (.\ADMINISTRATOR or DOMAIN\ADMINISTRATOR). Other administrative credentials that are not exactly "ADMINISTRATOR" will fail, even if they are domain admins. Since DOMAIN\veeam is none of these users, I suspect UAC is enabled.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5047
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: connecting to guest os via vix failed.

Veeam Logoby muisesa » Sat Apr 09, 2016 3:29 pm

Just curious if there was ever a solution posted for this error... I am also receiving:

- connecting to guest os via RPC successful
- connecting to guest os via vix failed. Failed to open VM (datatore/vmx file). VIX Error: there was an error in communication code 14010

Thanks for the help...
muisesa
Lurker
 
Posts: 1
Liked: never
Joined: Sat Apr 09, 2016 3:27 pm
Full Name: Scott Muise

Re: connecting to guest os via vix failed.

Veeam Logoby foggy » Mon Apr 11, 2016 2:37 pm

Do you have UAC enabled on the affected VMs? What credentials do you specify for the guest processing (please see Luca's answer above)?
foggy
Veeam Software
 
Posts: 14716
Liked: 1075 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: connecting to guest os via vix failed.

Veeam Logoby kewnev » Sun Apr 17, 2016 11:57 pm

muisesa wrote:Just curious if there was ever a solution posted for this error... I am also receiving:

- connecting to guest os via RPC successful
- connecting to guest os via vix failed. Failed to open VM (datatore/vmx file). VIX Error: there was an error in communication code 14010

Thanks for the help...


I recently came across this when moving our environment from Hyper-V to VMware, and if your situation is the same as ours the error only appears when executing the "Test Now" button under the Backup Job -> Guest Processing.
In your case, the VIX error you shouldn't need to worry about (assuming you don't have any guests that are "networkless").
You see, when Veeam performs a backup it will first try to connect with RPC. Only if RPC fails will it try with VIX.
As you can see in your above log extract RPC succeeds. Hence you can ignore the VIX error, and there is no need to disable UAC in the guest or to back up as the actual "administrator" login. The backup will work without warnings or errors (well it has for us).

To remove this confusion I think Veeam should not attempt VIX testing if RPC testing succeeds (ie when "Test Now" is executed).
kewnev
Enthusiast
 
Posts: 57
Liked: 19 times
Joined: Sun Jun 17, 2012 1:09 pm
Full Name: Nev V

Re: connecting to guest os via vix failed.

Veeam Logoby ita-tomi » Mon Apr 18, 2016 6:31 am 1 person likes this post

Only time you need VIX is if you have to backup VM with AppAware and there is no network connection from Veeam server to the VM. In those situations one needs to choose least bad option:
- Open access trough network
- Use Administrator account for backup job credentials
- Disable UAC
- Disable AppAware
ita-tomi
Influencer
 
Posts: 12
Liked: 7 times
Joined: Thu Apr 09, 2015 7:14 pm

Re: connecting to guest os via vix failed.

Veeam Logoby Andreas Neufert » Mon Apr 18, 2016 11:53 am

There are 2 ways to speak with the VM for InGuest processing.
RPC - The typical Windows way over the network.
VIX - Veeam connects to the ESXi hosts and opens a network less connection to the VM by using the VIX communication channel of the VMware Tools.

RPC is faster than VIX.
Veeam tries first to connect by RPC and fallback to VIX.

So if you can connect by RPC there is no need to fix the VIX connection.

To allow VIX to work you need several things:
- Actual VMware Tools installed within the VM.
- VM is running
- VIX is enabled within VMware Tools and ESXi (this is by default the case).
- DNS resolution needs to work correctly with the ESXi VMKernel interfaces (VMKernel Hostname and Domain settings needs to be inline with DNS).

For authentication within the VM you need one of the following.
a) Disabled UAC and a account that is somehow member of the local Administrator group.
or
b) the usage of a user with the name "Administrator" servername\administrator or domain\administrator and enabled UAC.
Andreas Neufert
Veeam Software
 
Posts: 2198
Liked: 357 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

[MERGED] Testing admin share accessibility via VIX fails

Veeam Logoby SaAtomic » Mon Dec 12, 2016 12:00 pm

I'm setting up an application-aware backup of a Windows Server 2012 R2 and get the following error message:

Code: Select all
Connecting to guest OS via VIX Error: Cannot upload  file to admin share [C:\Windows].
Cannot create folder in guest: [C:\Windows\VeeamGuestHelpersTest].
VIX Error: A file was not found Code: 4

Testing admin share accessibility via VIX


I've googled for a while and came across this blog entry https://notesfrommwhite.net/2016/06/28/connecting-to-guest-os-via-vix-error-error-4/ and if I understand it correctly, the error can be fixed by using a local administrator account.
But I'm already using a local administrator account, for the target machine.

edit: The local administrator account is not named Administrator and I've added the following key in the registry:

Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy 1


What do I have to do to have my setup pass the application-aware backup test?
SaAtomic
Novice
 
Posts: 9
Liked: never
Joined: Mon Oct 17, 2016 9:07 am

Re: connecting to guest os via vix failed.

Veeam Logoby Vitaliy S. » Mon Dec 12, 2016 2:20 pm

You either need to use built-in local administrator (named one) or disable UAC on this server. Please review this topic for more info.
Vitaliy S.
Veeam Software
 
Posts: 19539
Liked: 1097 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

[MERGED] VIX Error

Veeam Logoby jamerson » Fri Jan 06, 2017 12:34 pm

Hi Guys.
we are building a new ESXI6 for our customer.
i have created a daily job after adding the globe admin username and password and run a test , everything seems to be fine only one error.

Code: Select all
1/6/2017 2:32:02 PM :: Connecting to guest OS via VIX Error: Cannot connect to host [10.10.2.2] over VIX. Login: [root]. Guest Login: [domain\admin_me].
Failed to open VM [[SSD] DC001/DC001.vmx].
VIX Error: There was an error in communication Code: 14010


admin_me user is globe admin and can access the admin$ of each VM.
is this a firewall block ?

thank you
jamerson
Expert
 
Posts: 257
Liked: 16 times
Joined: Wed May 01, 2013 9:54 pm
Full Name: Julien

Next

Return to VMware vSphere



Who is online

Users browsing this forum: Bing [Bot], cthorpe and 17 guests