#12172 closed defect (fixed)
error starting VB Manager or issuing a vboxmanager command
Reported by: | JohnM391 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.2.18 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
Hi. If I start a VirtualBox VM, close it and right after that I open VirtualBox manager, sometimes it starts very slow and it says:
VirtualBox - Critical Error
Failed to create the VirtualBox COM object. The application will now terminate.
Details:
Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)
Vbox.log attached.
And also when I use VboxManage.exe commands (any) one after another, sometimes it waits and then says:
VBoxManage.exe: error: Failed to create the VirtualBox object! VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execu tion failed (extended info not available) VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
No Vbox.log found.
The error is in any VirtualBox 4.2.* and 4.3.* version. I reported the first error a while ago (with a different username, sorry I don't remember which one) and it was fixed only partially. Oh, and I searched before submitting and saw other reports with 0x80080005 error but not exactly the same.
Attachments (1)
Change History (4)
by , 11 years ago
comment:1 by , 11 years ago
comment:2 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please reopen if still relevant with VBox 4.3.10.
comment:3 by , 10 years ago
Actually it could be related to #12509 so you might also want to try the 4.3.11 test build posted there.
PS: I just noticed that the VboxManage.exe is crashing more often when a VirtualBox VM session was recently closed (just like in the first error)...