CO_E_SERVER_EXEC_FAILURE: Failed to create VirtualBox COM...

[opensas]

I have upgraded from version 2.2.4-47978 to 3.0.0-49315

and now I get the following error when tring to execute VirtualBox.exe

--
Fallo al crear el objeto COM de VirtualBox. (Failed to create VirtualBox's COM object)

La aplicación se cerrará. (Application will shut down)

Detalles (details)

Receptor RC:
CO_E_SERVER_EXEC_FAILURE (0x80080005)
--

I had a couple of troubles to install the version, the installer just hang up, or rolled back the installation. Once I even lost my wifi netword card, and had to reinstall it...

I tried upgrading and installing from scratch with no luck...

Now I'm trying with version 3.0.2-49928 with the same result...

I also found that a couples of versions ago a existed similar trouble, but it was long ago fixed

http://forums.virtualbox.org/viewtopic.php?t=10068


I've found the following error in the event viewer

El servidor {B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F} no se registró con DCOM dentro del tiempo de espera requerido.
Para obtener más información, vea el Centro de ayuda y soporte técnico en http://go.microsoft.com/fwlink/events.asp.

(something like: the server {B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F} has not registered with DCOM in the required time)

If I search with regedit I see that the server in fact is

F:\ARCHIV~1\Sun\XVMVIR~1\VBoxSVC.exe

so I try to manually execute it and I get the following error

La aplicación no se ha podido inicializar correctamente (0x0000142). Haga click en Aceptar para terminar la aplicación.

(The application could not start correctly (0x0000142). Click on Ok to finish the application)

Any idea what could be the issue???

[vbox4me2]

Possible fixes: http://www.google.nl/search?hl=nl&q=0x8 ... eken&meta=

[Perryg]

Reinstall the version that you had to start with and select repair. (2.2.4)
When it is done DO NOT reboot and run it again this time selecting uninstall
When done still DO NOT reboot and then install the new version and reboot when it is complete.

[estabien99]

This didn't work for me. But I now fixed this problem in my case.

I read in the most posts that it has something to do with audio devices, which sounds for me very implausible because in the most cases this problem occured after a certain time and not directly after installation. That the reinstallation doesn't fix the problem (even if I delete all user files like confgs etc...) suggests that the problem lies in some wrong system configuration. I found that the error "Callee RC: CO_E_SERVER_EXEC_FAILURE (0x80080005)" is also thrown in the ms visual studio if an application is missing some access rights for creating a DCOM-instance.

In my case it was a problem with a wrong user variable PATH in the environment variables. I recognized this because I found the .Virtualbox folder in the installation directory of this program.

[tz_earl]

On my Windows 7 host and VB 4.3.10, I was getting errors that included "CO_E_SERVER_EXEC_FAILURE " and "the VirtualBox COM server is not running or failed to start" when trying to run, for instance, VBoxManage.exe from a command window.

I found that I no longer get those kinds of errors after doing the following:

(1) Enable "Run as Administrator" for VirtualBox.exe, which is the VirtualBox Manager
(2) Enable "Run as Administrator" for any command windows that I use for doing VB stuff

These are general suggestions for those of us on Windows hosts. This may help with the particular issue on this thread as well as other issues around permissions / UAC.