StarWind Software

Hello.

I'm trying to do a P2V from a Windows Server 2008 R2 physical host to a Windows Server 2019 Hyper-V host.

Whenever I try to connect, I get this error:

Access is denied 0x80070005

I know the 0x error is a DCOM error so I checked that and confirmed that all settings for the DCOM are where they should be -- I even turned them down a bit but the error persists.

I added the Admnistrator user to the DCOM group in lusrmgr.msc as well as to Hyper-V and other admin groups but the issue persists.

I created a new account and gave it all the needed admin groups but the issue persists.

I confirmed that the C$ share is accessible from the 2008 host.

I've confirmed that all Hyper-V features are currently installed.

I'm really stuck on where else to proceed.

Here is the log from today's attempts:

I wanted to post the log but apparently I can't since it says that it "Contacts contacts."

Here's the important part:

10/1 15:25:31.304 1318 Facility ???INFO: WrapperHyperV::connect: Host - \\hyperv-1\root\virtualization\v2
10/1 15:25:31.380 1318 Facility ???ERROR: WrapperHyperV::connect: pLoc->ConnectServer \\hyperv-1\root\virtualization\v2 - 0x80070005
10/1 15:25:31.380 1318 Facility ???ERROR: WrapperHyperV::failResultToStr: Last Error - Access is denied.
(0x80070005)

HI,

Make sure the user has the read/write privileges for that share.

The “access denied” error can be quite annoying, especially when migrating from an older server to a newer one. To quickly fix this error, make sure that the user has the necessary read/write permissions for the shared folder and double-check all DCOM configurations to ensure they are set up correctly.

Thanks!

tonyaljohnson wrote: ↑

Fri Feb 07, 2025 3:15 am

The “access denied” error can be quite annoying, especially when migrating from an older server to a newer one. To quickly fix this error, make sure that the user has the necessary read/write permissions for the shared folder and double-check all DCOM configurations to ensure they are set up correctly.

Thank you very much for these detailed instructions, I will check the access rights and DCOM configuration right away to fix the “access denied” error.

You are welcome!
Make sure you have CredSSP on both nodes.
What also helps is a failover cluster as a domain admin on the cluster nodes themselves.
If nothing helps, redeploy might be needed.