Veeam connecting to guest os via vix error

veeam connecting to guest os via vix error cannot upload file to admin share

• Veeam: Version 9.5.0.1536 installed on Windows 2012 R2 (Vm guest, part of Domain)
• Vcenter: 6.5 (VM Guest, part of Domain)
• Multiple ESXI 6.5 servers under VC

I am using Domain Controller Administrator account, & getting Error when testing job under «Guest Processing» (although I can access all server’s admin share from the Veeam server like \target_serverC$ etc)

The error is showing for different vm guests example windows 7 , windows 2008, windows 2012.

• Tried disabling UAC (via UAC gui and Registry)
• Added LocalAccountTokenFilterPolicy in registry for 2012 as well,
• Firewall is disabled on all machines by group policy

Popular Topics in VMware

I can say I have gotten this and then the backups still work. Weird, but I haven’t upgraded to the last 2 versions because of a legacy tech I’m currently trying to replace. Try performing a backup on a small VM where the authentication test fails. I bet it still works. Why? I don’t know, but may have been resolved in a later build

problem still exists.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

poor wifi, school’s third floor

I work as a help desk technician at a high school for a school district. Teachers/students on the building’s third floor have been reporting poor wifi, with their Chromebooks/laptops etc experiencing slow connectivity and random disconnections. We hav.

Need help crafting a job posting for an IT Pro

I’d really appreciate some thoughts and advice. I’m looking to hire an IT pro to be our resident go-to for all things IT (device support, SQL Server, network admin, etc) but who also is interested in learning — or even has some experience in — the.

Snap! — AI Eye Contact, Mine Batteries, Headset-free Metaverse, D&D Betrayal

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: January 13, 1874: Adding Machine Patented (Read more HERE.) Bonus Flashback: January 13, 1990: Astronauts awakened to the song Attack of the Killer Tomatoes (Read mor.

Spark! Pro series – 13th January 2023

Happy Friday the 13th! This day has a reputation for being unlucky, but I hope that you’ll be able to turn that around and have a great day full of good luck and good fortune. Whether you’re superstitious or not, .

Источник

Troubleshooting Guest Processing «Test Now» issues

KB ID:	3225
Product:	Veeam Agent for Microsoft Windows | 4.0 | 5.0 Veeam Backup & Replication | 10 | 11
Published:	2020-07-23
Last Modified:	2021-08-13

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.

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.

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 is different from what is configured on the Guest Processing tab, check under the [Credentials. ] button on the Guest Processing tab to check if specific credentials have been set.

For VM Backup and Replication jobs (VMware or Hyper-V), the account specified to connect to the Guest is always the account used to login 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.

_{This is not an exhaustive list of potential errors. If you have an error not listed here, please use the «KB Feedback/Suggestion» button at the bottom of this article to notify Veeam Support.}

If the error you see 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 you can paste it somewhere else to see the full error.

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

connecting to guest os via vix failed.

connecting to guest os via vix failed.

Post by Kas_Tigar » Jan 29, 2015 3:09 pm this post

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!

Re: connecting to guest os via vix failed.

Post by Shestakov » Jan 29, 2015 3:20 pm this post

Re: connecting to guest os via vix failed.

Post by Kas_Tigar » Jan 29, 2015 3:28 pm this post

Re: connecting to guest os via vix failed.

Post by Shestakov » Jan 29, 2015 3:49 pm this post

Re: connecting to guest os via vix failed.

Post by MAA » Apr 30, 2015 2:25 pm this post

I also have this issue.

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

(DOMAINveeam is Domain Admin and vCenter Admin)

Re: connecting to guest os via vix failed.

Post by foggy » Apr 30, 2015 2:39 pm this post

Re: connecting to guest os via vix failed.

Post by dellock6 » Apr 30, 2015 3:53 pm this post

Luca Dell’Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1

Re: connecting to guest os via vix failed.

Post by muisesa » Apr 09, 2016 3:29 pm this post

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.

Re: connecting to guest os via vix failed.

Post by foggy » Apr 11, 2016 2:37 pm this post

Re: connecting to guest os via vix failed.

Post by kewnev » Apr 17, 2016 11:57 pm this post

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).

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Guest processing

Guest processing

Post by badams » Jan 22, 2018 2:58 am this post

During the setup when I get to guest processing and credentials, I use the same credentials I have used all along. I run the test, and it fails every time. I get a warning on checking standard credentials and a red x on Connecting to Guest OS on RPC. Also, Testing Admin Share Accessibility via RPC and Cannot Connect to the Host’s Administrative Share. Any thoughts?

Re: Guest processing

Post by veremin » Jan 22, 2018 3:14 pm this post

Re: Guest processing

Post by mriksman » Aug 16, 2018 4:45 pm this post

This is what I am seeing.

I used my personal, domain admin account when I first setup. Backups seem fine — no errors — but I haven’t tried a restore yet (it’s on the list of things to do. ). Log/report says that SQL logs were truncated (which I presume is related to Application Aware processing)

But I decided to create a standalone account. So I made it a domain admin member as well (as I saw this is required for DC backups), and went to modify the ‘Guest OS Credentials’. I clicked Test Now, and all of them have;
A warning next to ‘Checking Standard Credentials’
A red cross next to ‘Connecting to guest OS via VIX Error: Cannot upload file . ‘
A red cross next to ‘Testing admin share accessibility via VIX’

I tried my personal account again, and I too get the same warnings/errors.

So — the test fails, but the backups work.

I read somewhere, to try using the standard DOMAINAdministrator account to get around UAC. I tried this and _most_ of them now pass. Well — Windows 2012×64 and Windows 7 does. But my 2 Windows 2008R2 still fail (although these are Honeywell PCs and as part of their installation, may have extra security policies/settings enforced on them).

Any ideas? Am I missing anything critical with these errors, but the backups are ‘working’?

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

i can’t add servers on backup job

i can’t add servers on backup job

Post by astoinemicro » Feb 12, 2021 4:17 pm this post

Hi ,after a new installation of veeam 10 on a BACKUP VM , wich was setup on a Vmware ESXI 6.7.0 ,i can’t add all my VM servers on veeam , i keep having this error :
Connecting to guest OS via VIX Error: Cannot connect to host [192.168.50.13] over web services.
Login: [root].
Guest Login: [promadomain.proma.localerjout].
Could not initiate Web Service connection
Could not initiate guest virtual machine [6] with user [promadomain.proma.localerjout]
Could not validate host [https://192.168.50.13:443/sdk] credentials for guest [6] user [promadomain.proma.localerjout]
Could not invoke guest operation
Current license or ESXi version prohibits execution of the requested operation.

The userrname and password are right and have the proper admin permission .
i disabled Firewall rules from remote Servers
Pings are working fine
I can do remote with RDP on those servers
Shared folder are accessible from The backupserver
i reinstalled the Vmware Tools

Do you have any Idea how to resolve this ?

Re: i can’t add servers on backup job

Post by wishr » Feb 12, 2021 4:26 pm this post

Welcome to Veeam R&D forums!

Is that a licensed or a free ESXi server? If the latter, then this is the case — free ESXI servers are not supported by VBR.

Источник

Hello.

As the title says I’m having some dificulty configuring with guest OS credentials.

We created a Service Account that is computer admin of this VM. Password is correct as I tried to login to the computer with the account, however when testing the access I get the following errors:

23/10/2020 15:31:32 :: Testing credentials via guest interaction proxy PROXYSERVER
23/10/2020 15:31:32 :: Find target VM on Host VCENTER
23/10/2020 15:31:32 :: Validating guest agent availability for the VM
23/10/2020 15:31:32 :: VM is powered on
23/10/2020 15:31:32 :: Guest OS state is Running
23/10/2020 15:31:32 :: VMware Tools status is Ok
23/10/2020 15:31:32 :: VMX file name: [3PAR_69739_T1_002] VM/VM.vmx
23/10/2020 15:31:32 :: IP address: 10.101.185.14,10.101.191.14,10.101.189.14
23/10/2020 15:31:32 :: Guest OS: Microsoft Windows Server 2008 R2
23/10/2020 15:31:32 :: Checking standard credentials
23/10/2020 15:31:32 :: Connecting to guest OS via RPC
23/10/2020 15:31:32 :: Testing admin share accessibility via RPC
23/10/2020 15:32:17 :: Testing guest OS connectivity via RPC
23/10/2020 15:33:22 :: Connecting to guest OS via VIX
23/10/2020 15:33:22 :: Testing admin share accessibility via VIX
23/10/2020 15:33:54 ::  Error code: 0x80004005;
23/10/2020 15:33:54 :: Failed to invoke func [TestUploadFile]: Unspecified error. Cannot upload  file to admin share [].
;
23/10/2020 15:33:54 :: Could not run program [C:UsersTEMPPT~1.000AppDataLocalTemp{8c0c7bea-0619-4010-88b1-4bfcda33b63d}] with arguments [-func GetTargetAdminFolder -out "C:UsersTEMPPT~1.000AppDataLocalTemp{fa982aaa-3d90-4923-b9a1-a05a17a078be}"] and timeout [3600000] in guest
;
23/10/2020 15:33:54 :: Could not run program [C:UsersTEMPPT~1.000AppDataLocalTemp{8c0c7bea-0619-4010-88b1-4bfcda33b63d}] with arguments [-func GetTargetAdminFolder -out "C:UsersTEMPPT~1.000AppDataLocalTemp{fa982aaa-3d90-4923-b9a1-a05a17a078be}"]
;
23/10/2020 15:33:54 :: Could not invoke guest operation
;
23/10/2020 15:33:54 :: File C:UsersTEMPPT~1.000AppDataLocalTemp{8c0c7bea-0619-4010-88b1-4bfcda33b63d} was not found;

Anyone came accross with this?

We’re running Veeam v10.

0 Flares Twitter 0 Facebook 0 LinkedIn 0 Email — 0 Flares ×

Since Microsoft introduced VSS libraries, it’s a smart way of doing backup using them, in order to guarantee a consistent backup of applications supporting them.

Veeam can do backups without the help of permanent agents inside the virtual machines, anyway if you want to do a VSS-based backup, Veeam deployes (and removes when the backup is completed) a small agent in the Windows VM in order to cohordinate VSS tasks. Usually, this is done by connecting to the target VM via network.

But, what happens when for any reason Veeam is in another network of the one used by the virtual machine, or they cannot communicate to each other? For example an IIS webserver in a DMZ network that cannot be reached from the network where Veeam server is connected to?

In these situations we can really appreciate VMware VIX libraries, and the way Veeam decided to use them. I found this quite old article , dated 2008, they noentheless explains in an awesome way what those libraries can do. Basically, they allow for direct interaction between the guest operating system inside a VM using the hypervisor running it, without any need for network connectivity. Among the several activities you can do, you can copy files, start and stop services, and run programs inside the guest VM.

Veeam has taken advantage of these libraries to allow VSS-based backups, even when the VM cannot be reached via network. To show you this, I created a small test in my lab, by deploying a Windows 2008 R2 VM with no network connection at all:

I then configured a quick backup job in Veeam, without any custom parameter other than the use of VSS libraries, just to see what was going to happen:

The backup was “simply” complteted successfully. To be honest, Veeam first tries to connect as usual via RPC, but right because the VM does not have any IP address, it fails and it then tries to use VIX libraries. You can appreciate the intimate procedure by looking at the relevant log parts:

[24.06.2013 14:00:20] <01> Info [VssGAConn('vix-test')] Initializing VSS guest agent connection.
[24.06.2013 14:00:20] <01> Error Failed to connect to guest agent: unable to obtain guest IP address. at Veeam.Backup.VssProvider.CVssGAConnection.ConnectViaRpc
[24.06.2013 14:00:20] <01> Error at Veeam.Backup.VssProvider.CVssGAConnection.CreateEx
[24.06.2013 14:00:20] <01> Info [VssGAConn] Connecting to guest via vix, hostIp '10.2.50.111', postPort '443', hostUser 'SKUNKWORKSadministrator', vmVmx '[qnap259] vix-test/vix-test.vmx', vmUser 'vix-testadministrator'
[24.06.2013 14:00:20] Info Connecting to host [10.2.50.111] over VIX library. Login: [SKUNKWORKSadministrator].
[24.06.2013 14:00:26] Info Temporary file [C:UsersADMINI~1AppDataLocalTempvmware161] created.
[24.06.2013 14:00:26] Info Copying files form host [C:Program FilesVeeamBackup and ReplicationVSSVeeamGuestAgentsVeeamVixProxy.exe] to guest [C:UsersADMINI~1AppDataLocalTempvmware161].
[24.06.2013 14:00:27] Info Connecting to host [10.2.50.111] over VIX library. Login: [SKUNKWORKSadministrator].. Ok.
[24.06.2013 14:00:27] Info Enter CVeeamVssGAInstaller::GetGateState
[24.06.2013 14:00:28] Info Temporary file [C:UsersADMINI~1AppDataLocalTempvmware185] created.
[24.06.2013 14:00:28] Info Running program [C:UsersADMINI~1AppDataLocalTempvmware161 -func GetServiceState -out "C:UsersADMINI~1AppDataLocalTempvmware185" -svcname "VeeamVssSupport"].
[24.06.2013 14:00:30] Info Copying files form guest [C:UsersADMINI~1AppDataLocalTempvmware185] to host [C:WindowsTEMPifd4720.tmp].
[24.06.2013 14:00:31] Info Deleting file [C:UsersADMINI~1AppDataLocalTempvmware185] in guest.
[24.06.2013 14:00:32] Info Leave CVeeamVssGAInstaller::GetGateState
[24.06.2013 14:00:32] <01> Info VssGAConn('vix-test')] Agent state: 'EVeeamVssNotInstalled'.
[24.06.2013 14:00:32] <01> Info [VssGAConn('vix-test')] Installing agent.
[24.06.2013 14:00:32] Info Enter CVeeamVssGAInstaller::Install
[24.06.2013 14:00:32] Info Installing agent.

As you can see, since the RPC connection has failed, Veeam connects to vCenter (10.2.50.111) and from here to the VM via VIX, using the same credentials I specified in the job (vix-testadministrator), since the VM is not joined to my lab domain “SKUNKWORKS”. VIX connection is successful, and Veeam is able to install the temporary agent into the VM.

How cool is that?

If you also want to remove the initial error, and save some seconds in the job execution, since Veeam Backup & Replication v6.1 patch 1 (build 6.1.0.205) you can switch the VSS connection order, telling Veeam to try VIX connection first. You can see how to do it in the release notes of that build:

Added new registry value that reverses the sequence of application-aware processing, making jobs try network-less processing mode before network one. HKEY_LOCAL_MACHINESOFTWAREVeeaMVeeam Backup and Replication DWORD: InverseVssProtocolOrder Value = 1 To disable (default behavior), value is 0 (false)

So, after I configured the new registry key as described, I run again the same backup job:

First thing you can see, “Preparing guest for hot backup” now lasted 15 seconds instead of 21, meaning something has really changed. But, as before, the detailed log is where you can appreciate the configuration change:

[24.06.2013 14:39:16] <01> Info [VssGAConn('vix-test')] Initializing VSS guest agent connection.
[24.06.2013 14:39:17] <01> Info [VssGAConn] Connecting to guest via vix, hostIp '10.2.50.111', postPort '443', hostUser 'SKUNKWORKSadministrator', vmVmx '[qnap259] vix-test/vix-test.vmx', vmUser 'vix-testadministrator'
[24.06.2013 14:39:17] Info Connecting to host [10.2.50.111] over VIX library. Login: [SKUNKWORKSadministrator].
[24.06.2013 14:39:24] Info Temporary file [C:UsersADMINI~1AppDataLocalTempvmware175] created.
[24.06.2013 14:39:24] Info Copying files form host [C:Program FilesVeeamBackup and ReplicationVSSVeeamGuestAgentsVeeamVixProxy.exe] to guest [C:UsersADMINI~1AppDataLocalTempvmware175].
[24.06.2013 14:39:25] Info Connecting to host [10.2.50.111] over VIX library. Login: [SKUNKWORKSadministrator].. Ok.
[24.06.2013 14:39:26] Info Temporary file [C:UsersADMINI~1AppDataLocalTempvmware215] created.
[24.06.2013 14:39:26] Info Running program [C:UsersADMINI~1AppDataLocalTempvmware175 -func GetServiceState -out "C:UsersADMINI~1AppDataLocalTempvmware215" -svcname "VeeamVssSupport"].
[24.06.2013 14:39:28] Info Copying files form guest [C:UsersADMINI~1AppDataLocalTempvmware215] to host [C:WindowsTEMPifd6AC3.tmp].
[24.06.2013 14:39:29] Info Deleting file [C:UsersADMINI~1AppDataLocalTempvmware215] in guest.
[24.06.2013 14:39:30] Info Leave CVeeamVssGAInstaller::GetGateState
[24.06.2013 14:39:30] <01> Info VssGAConn('vix-test')] Agent state: 'EVeeamVssNotInstalled'.
[24.06.2013 14:39:30] <01> Info [VssGAConn('vix-test')] Installing agent.

You can see as now Veeam has started first to connect via VIX libraries, without trying first a connection via network.

So, if you have several virtual machines you cannot reach via network, maybe you can configure Veeam to use VIX libraries as its primary backup mode for VSS.