Failed to inject guest runtime...

[flomp]

Hi,

I built a second Hyper-V 2016 server and installed my first Windows Server 2016 instance.
In the VM settings, all "integration services" are selected.
Then, I added the Hyper-V-Server to my inventory and the VM to an existing backup job.

The new VM fails with:

Code: Select all

10.11.2018 21:32:52 :: Queued for processing at 10.11.2018 21:32:52  
10.11.2018 21:32:55 :: Required backup infrastructure resources have been assigned  
10.11.2018 21:39:34 :: VM processing started at 10.11.2018 21:39:34  
10.11.2018 21:39:34 :: VM size: 250,0 GB (26,7 GB used)  
10.11.2018 21:39:37 :: Preparing to create snapshot  
10.11.2018 21:39:42 :: Using guest interaction proxy backup...... (Same subnet)  
10.11.2018 21:40:09 :: Failed to inject guest runtime using guest interaction proxy, failing over to PowerShell Direct  
10.11.2018 21:40:09 :: Failed to inject guest runtime using PowerShell Direct, failing over to backup server  
10.11.2018 21:40:09 :: Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Unable to perform application-aware processing because connection to the guest could not be established  
10.11.2018 21:40:11 :: Error: Unable to perform application-aware processing because connection to the guest could not be established  
10.11.2018 21:40:11 :: Network traffic verification detected no corrupted blocks  
10.11.2018 21:40:11 :: Processing finished with errors at 10.11.2018 21:40:11  

All other VMs work fine. What am I doing wrong?

Both, the Hyper-V Server and the instance have all Microsoft updates installed.

[flomp]

ok, found it myself. The firewall was still on

To fix, run the following in the VM:

Code: Select all

Set-NetFirewallRule -DisplayGroup 'File and Printer Sharing' -Enabled true
# or for the german version:
Set-NetFirewallRule -DisplayGroup 'Datei- und Druckerfreigabe' -Enabled true

[Mike Resseler]

Hey flomp,

Glad that you have found it yourself. How ever, I also noticed that PowerShell direct (which is MSFT alternative for VMware's VIX) also failed. So you might want to have a look at that for these specific cases where you don't want to have direct connection to the VM

Cheers
Mike

[micros]

I know this wasn't your initial problem but for this error "Failed to inject guest runtime using PowerShell Direct, failing over to backup server"...
Make sure you have the Hyper-V Powershell module installed on all Hyper-V hosts.