connecting to guest os via vix failed.

VMware specific discussions

Re: connecting to guest os via vix failed.

Veeam Logoby Vitaliy S. » Fri Jan 06, 2017 12:43 pm

Julien, please take a look at my previous post for the solution. Should help.
Vitaliy S.
Veeam Software
 
Posts: 19575
Liked: 1106 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: connecting to guest os via vix failed.

Veeam Logoby Andreas Neufert » Fri Jan 06, 2017 2:09 pm

Let me please add again that VIX processing is used ad fallback (only) if RPC connection is not possible. So you can ignore this if you start a test.

If you can not avoid VIX usage, then look at my above statement for details.
Andreas Neufert
Veeam Software
 
Posts: 2201
Liked: 360 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

Re: connecting to guest os via vix failed.

Veeam Logoby jamerson » Fri Jan 06, 2017 4:23 pm

Vitaliy S. wrote:You either need to use built-in local administrator (named one) or disable UAC on this server. Please review this topic for more info.

which server do you mean to disable the UAC ? the VEEAM Server or the Client servers that need to be backed up ?
jamerson
Expert
 
Posts: 257
Liked: 16 times
Joined: Wed May 01, 2013 9:54 pm
Full Name: Julien

Re: connecting to guest os via vix failed.

Veeam Logoby Vitaliy S. » Fri Jan 06, 2017 4:26 pm

This refers to client servers (VMs).
Vitaliy S.
Veeam Software
 
Posts: 19575
Liked: 1106 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: connecting to guest os via vix failed.

Veeam Logoby Andreas Neufert » Fri Jan 06, 2017 6:31 pm 1 person likes this post

Andreas Neufert wrote: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: 2201
Liked: 360 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

Re: connecting to guest os via vix failed.

Veeam Logoby jamerson » Sun Jan 22, 2017 12:35 am

Disabled the UAC and after it works.
if it can't run the test , and the UAC is not off, would it do some harm stuff to the backup files ?
jamerson
Expert
 
Posts: 257
Liked: 16 times
Joined: Wed May 01, 2013 9:54 pm
Full Name: Julien

Re: connecting to guest os via vix failed.

Veeam Logoby Andreas Neufert » Sun Jan 22, 2017 6:47 am

It has not something to do with the way we write data, it is a question if the data is consistent and if you backup application-aware.

If RPC (over Network) works, you do not need VIX as VIX is ONLY used as fallback if RPC not work.
Andreas Neufert
Veeam Software
 
Posts: 2201
Liked: 360 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

Re: connecting to guest os via vix failed.

Veeam Logoby lreese » Tue Jan 24, 2017 2:35 pm

I pointed all of my backups to use the local admin account instead of the domain admin account and found this to fix my issue.
It seems like a messy fix, but it will do for now.
lreese
Novice
 
Posts: 8
Liked: 1 time
Joined: Tue Aug 30, 2016 12:38 pm
Full Name: Logan Reese

Re: connecting to guest os via vix failed.

Veeam Logoby Andreas Neufert » Wed Jan 25, 2017 8:55 am

Thanks for the feedback.

VIX is only needed if there is no network connection for RPC and RPC can work with any account that belong to local admin group (inherit).
Andreas Neufert
Veeam Software
 
Posts: 2201
Liked: 360 times
Joined: Wed May 04, 2011 8:36 am
Location: Germany
Full Name: @AndyandtheVMs Veeam PM

[MERGED] Backing up non-domain server

Veeam Logoby jrafter » Tue Mar 21, 2017 9:39 pm

I've been back and forth with support regarding this topic/issue. I have a non-domain server sitting in my vSphere environment. I used local admin credentials for Veeam to use...RPC fails but VIX appears to work. In the email log I see "Failed to call RPC function 'Vss.Unfreeze': Error code: 0x80004005. Failed to invoke func [Unfreeze]: Unspecified error. Failed to unfreeze guest system (VIX mode). Cannot run program [C:\Windows\TEMP\{e1e7ef23-3551-4564-8433-fbcd048f0dad}]. VIX Error: VMware Tools are not running in the guest Code: 3016"

VMware tools are up to date and running...the funny thing is that the on the second attempt it backed up successfully. I cant seem to find any definitive answers for backing up a non-domain box.

Any help?
jrafter
Novice
 
Posts: 4
Liked: never
Joined: Fri Dec 02, 2016 3:12 pm
Full Name: John R

Re: connecting to guest os via vix failed.

Veeam Logoby PTide » Tue Mar 21, 2017 11:04 pm

Hi,

Your post has been merged to the existing thread on the subject. Please review the thread and post your case ID. I'd also recommend to check VSS event log for any errors.

Thank you.
PTide
Veeam Software
 
Posts: 3022
Liked: 247 times
Joined: Tue May 19, 2015 1:46 pm

[MERGED] VIX communication failure

Veeam Logoby b.vanhaastrecht » Thu Apr 20, 2017 11:56 am

Hello,

We have vSphere 6.0 and need networkless backup. Currently there's a problem with VIX:

Code: Select all
[20.04.2017 13:20:44] <49> Info     [WinGuestConnectionProxy] Connecting to guest service via VIX, hostIp '1.1.1.1', postPort '443', hostUser 'user', vmVmx '[spbr_ssd1] THLxxxxx (6f0051d4-bee4-4684-83e0-c25d8c4f13ce)/THL-xxxxxx(6f0051d4-bee4-4684-83e0-c25d8c4f13ce).vmx', vmUser 'domain\administrator'
[20.04.2017 13:20:45]      Info             Connecting to host [1.1.1.1] over VIX. Login: [user].
[20.04.2017 13:21:06]      Info             Connecting to host [1.1.1.1] over VIX. Login: [user].. Failed.
[20.04.2017 13:21:06]      Error             Cannot connect to host [1.1.1.1] over VIX. Login: [spbr_veeam]. Guest Login: [domain\administrator].
[20.04.2017 13:21:06]      Error             Failed to open VM [[spbr_ssd1] THL-xxxxxxx (6f0051d4-bee4-4684-83e0-c25d8c4f13ce)/THL-xxxxxxx (6f0051d4-bee4-4684-83e0-c25d8c4f13ce).vmx].
[20.04.2017 13:21:06]      Error             VIX Error: There was an error in communication Code: 14010


The user account is 100% correct and used to access the vCenter inventory correctly, it's an Administrator in vCenter.

There's a firewall between Veeam and vCenter (not managed by us). Does VIX use an other TCP port then 443? Other things that could be causing this?

Regards,
Bastiaan
========================================
Veeam ProPartner and Cloud Connect Provider
b.vanhaastrecht
Service Provider
 
Posts: 337
Liked: 66 times
Joined: Mon Aug 26, 2013 7:46 am
Location: The Netherlands
Full Name: Bastiaan van Haastrecht

Re: connecting to guest os via vix failed.

Veeam Logoby PTide » Thu Apr 20, 2017 12:55 pm

Hi,

Does VIX use an other TCP port then 443?

I guess that it does:

vmware technote, page 4 wrote:1. VIX client program calls a function in the VIX library.
2. VIX sends a command over a TCP connection (on port 902) to the virtual machine’s VMX process. The TCP connection for VIX guest operations goes directly to VMX on the ESXi host, bypassing the vCenter Server, and the host agent process. By contrast, virtual machine and datacenter operations are proxied by vCenter Server using SOAP/https on port 443, and relayed to the host agent.
3. VMX relays the command to VMware Tools in the guest.
4. VMware Tools has the Guest OS execute the guest operation.


14010 is a VIX_E_HOST_TCP_SOCKET_ERROR

Thanks
PTide
Veeam Software
 
Posts: 3022
Liked: 247 times
Joined: Tue May 19, 2015 1:46 pm

Previous

Return to VMware vSphere



Who is online

Users browsing this forum: No registered users and 28 guests