Failed to find owner host for VM

[BrianBuchanan]

Case #07343961

Upgraded from 12.1.156 to 12.1.2.172 and since the upgrade our first/lone Windows Server 2022 server is giving "Failed to find owner host for VM" when running the job to backup the host. The log shows successful enumeration of the vms on the host, but the very next step it fails with access denied.

We have 60+ other servers running Server 2019 that are backing up fine after the upgrade, and this host was successfully backing up before the upgrade. It seems to be something peculiar about this newest host. Windows updates are current.

Support asked to confirm the account is local admin, which it is, check for event id 10036 in case the issue is dcom hardening (no event found & never applied dcom hardening as a policy, unless 2022 does something different by default), and removed and re-added the host to the job with the same results.

I found this thread discussing similar problem, but while we do have VMM, this host isn't in VMM and my host been added directly to Veeam.
microsoft-hyper-v-f25/owner-host-for-vm ... 86128.html

[Mildur]

Hello Brian

Out of my mind, I'm not aware of any known issues regarding your error message.
Please give our customer support team more time to investigate the issue. There was a new mail with troubleshooting steps a few hours ago.

If you need to escalate the case to a higher tier, use our "Talk to A manager" button in the support portal.
https://www.veeam.com/kb2320

Best,
Fabian

[BrianBuchanan]

I found a work around, in our backup jobs we typically specify the host, not the VMs. When I edited the job to specify the VMs the job ran fine. Switching the job back to the host and it fails again.