Can't start VirtualBox manager. COM Object error

▲
0
▼

Our host is Windows Server 2008 r2.
When a user RDP's into the server and starts an instance of VirtualBox, then another user RDP's in to a different user account and tries to start VirtualBox, it throws this error:

Failed to create the VirtualBox COM object.
Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005) Windows Server 2008

Is VB able to handle multiple instances?

Our current case: U1 started VB to start up some of our VM's.
U2 (me in this case) just wants to create a couple new VM's on there.

If VB is unable to do this, how should I go about creating the new VM's?

virtualbox
virtualization
asked on Stack Overflow Mar 12, 2014 by mOrloff • edited Mar 14, 2014 by mOrloff

4 Answers

▲
4
▼

Well, it looks like we might have gotten to the bottom of it.
We had a service running that was an artifact from something that had been tried a while back.
VboxVMService was still installed and running.
As soon as we killed that, BINGO!, we were able to get in.

I hope this helps somebody :)

answered on Stack Overflow Mar 14, 2014 by mOrloff • edited Mar 14, 2014 by mOrloff
▲
4
▼

In my case the above solutions didn't work, but deleting the entire folder at C:\Users\YourUserName\.VirtualBox fixed the issue. Worth a try for anyone else for whom the above solutions don't help.

answered on Stack Overflow Jan 2, 2019 by T. Shaffner
▲
1
▼

For me the issue was that a VM that was setup had permissions set for a user that no longer existed. I tracked down the old user's folder, deleted them carefully and then set the permissions on my virtual machines folder and all children to my current user.

Starting VBox as administrator temporarily got things working, which is what led me to find that it was a permissions issue.

PS: VboxVMService was installed in my system as well, I did not have to uninstall it to get VirtualBox working again.

answered on Stack Overflow Apr 9, 2016 by Ray Foss • edited Sep 26, 2016 by Ray Foss
▲
0
▼

If you have this problem, uninstall VM first. At the time of installation process, right click on 'VirtualBox_any_version.exe' and click on -> Run as Administrator. This will fix this issue.

answered on Stack Overflow Nov 30, 2017 by Sayali Sonawane

User contributions licensed under CC BY-SA 3.0