Access is denied (Exception from HRESULT: 0x80070005) with VMRCplus 1.8.0

I received several posts last week related to the error above.

I am still investigating how/why this happened but it is caused by the fact that the .Net Framework 3.0 is missing from the machine where VMRCplus is being used.

So to fix this for now, install the .Net Framework 3.0 (with SP1).

Comments (19)
  1. The same with 1.8. It hangs immediately after I select a virtual machine and press Ctrl+C.

  2. Please submit VMRCplus 1.8 issues only.

  3. Anonymous says:

    Hi guys,

    i tried the .Net version 3 with Sp1 and it now works fine,

    luckily I don’t require .Net 3.5 version just yet.

    Thanks for info


  4. Anonymous says:

    i tried to update .Net version 3with Sp1 – no luck.

    One thing I did find was to turn off Windows XP Firewall and then I could connect.

  5. Anonymous says:

    HAve the same issue  I’ve tried VMRC+ 1.8 on Windows XP x86 with .Net Framework 3.5 installed, and I’ve encountered the same problem.

    Reinstall did not help either

  6. It seems that .Net 3.0 SP1 is sufficient. Of course, .Net 3.5 contains that.

  7. Hey there – I just tried VMRCplus 1.8 on Vista Business x64 and got this same error message. I already had the .Net Framework 3.5 installed, but I did a repair on that and it didn’t fix the problem. Then I reinstalled VMRCplus including both options and still encountered the issue. Hope you can help…

  8. Anonymous says:

    As I suspected it seems to be a security issue, explained at another one of Matthijs’s blogs:

    As Keith Comb wrote it was not what I wanted to hear, but at least now I know what the problem is. Just thought I’d mention this here since I was still wasting time looking for a solution myself. Perhaps in the future there will be a version that addresses this issue? Who knows…

  9. Bug works for me too.

    And I have a strange bug under VMRC Plus 1.7. It hangs immediately after I select a virtual machine and press Ctrl+C ("Settings" context menu item for a virtual machine).

  10. Anonymous says:

    I’m running Vista Ultimate x64, SP1.

    Virtual Server 2005 R2 is running on a Windows Server 2003 SP2. Everything is working as expected on the W2K3, but I cannot connect in Vista.

    Vista Computer has:

    – .Net FrameWork Compact 1.0 SP3, 2.0 SP2, 3.5

    – .Net FrameWork 2.0 SDK (x64), 3.5 SP1

    .Net 3.0 enabled in the Windows Feature.

    I Tried "run as administrator", failed to connect.

    I checked the DCOM access rights, failed to connect.

    Running VMRCplus in 32 and 64 bits, failed to connect.

    Checked the W2k3 firewall settings, failed to connect.

    Tried running as a Administrator DOS Prompt, failed to connect.

    I have no problem getting a connection to the Virtual machines through the web interface (or the server for that matter).

    Any suggestions?

  11. Anonymous says:

    Me too, I’ve tried VMRC+ 1.8 on Windows XP x86 with .Net Framework 3.5 installed, and I’ve encountered the same problem.

  12. @Bill

    VMRCplus most likely won't work on Windows7. It has not been developed (hence tested) on anything above the Vista/2008 release. In general you cannot expect products to work on operating systems they were never developed for.

  13. Anonymous says:

    I have this problem only remote (not using a domain member XP machine on the same local network). When I try connecting from a "public" computer through a VPN (PPTP) connection I get the mentioned "Access is denied…" error.

    The remote server is a Windows 2003 server with SP2. This is a domain controller + IAS + RAS server (I know this is not "best practice" being connected to the internet) including the latest updates as wel as .NET 3.0 and .NET 3.5.

    The local computer is a Windows XP workstation with SP3, also including .NET 3.0 and .NET 3.5. and various updates. This is not a domain member and connecting through VPN (PPTP)

    From this VPN-connected remote XP workstation I can access all resources (network shares, printers etcetera) at my home server. Only VMRCPlus (version cannot get a connection due to the mentioned "Access is denied…" error.

    Personally I suspect this whole issue has something to do with authentication/verification. I tried the "Run-as" for VMRCPlus, but it cannot seem to verify the (remote) user account (which has administrator rights). It seems like the locally started VMRCPlus does not send the desired credentials. Since I see no option to add a username/password for the VMRCPlus connection I see no solution so far.

  14. Anonymous says:

    @Matt: Using Hyper-V isn't an option as it can't physically be installed on the machines.  While the servers are 64-bit, the processors do not support Hyper-V, which is why we are using Virtual Server 2005 R2 SP1.  The servers are running 2008 (not R2) and my workstation is running Windows 7, which I just upgraded to SP1.  After the workstation upgrade, VMRCPlus v1.8 no longer works.

  15. Anonymous says:

    I install VMRCPlus on Windows XP SP3,when I use VMRCPlus connect a Remote Virtual Server,it show me a message:

    Virtual Server returned ‘access denied’ (Code 5).You may hace isufficient privileges to connect to Virtual Server.

  16. smy says:

    To resolve this problem " access denied (Code 5).You may hace isufficient privileges " Goto Virtual Server Properties > Virtual Server security and add an entry for the user and give the desired permissions.

  17. zack says:

    Where is Virtual Server Properties?

  18. nicko says:

    I have VMRCPlus V1.8 on a Windows 2008 Server R2 machine. Working fine until I updated with Windows 2008 Server Service Pack 1 today.

    Now I can only access the virtual machines through the web client only.

    I get the "Access is Denied"(Exception from HRESULT: 0x80070005) error when I use the VMRCPlus V1.8 console and click the connect button to open the list of virtual machines on localhost.

    I am just going to view your vmrcplus and authentication article now to aid in a resolution for this issue.

  19. @NickO: Notice that this has never been tested under Windows Server 2008. I would suggest to migrate to Hyper-V when using Windows Server 2008 R2.

Comments are closed.

Skip to main content