VBox 2.1 NS_ERROR (fixed)
Posted: 28. Dec 2008, 00:23
I am running Mandriva 2009.0 host. AMD 64 Athlon uP. I was using VBox 2.06 working stable. I use the "All Distributions AMD64" download version to give me full USB support which the OSE version does not. Yesterday, I upgraded to VBox 2.1 downloaded from "All distributions AMD64" file name VirtualBox-2.1.0-41146-Linux_amd64.run. Version 2.1 appeared to work and I installed the guest additions. My guest WinXP worked, but I noticed that I couldn't access any USB devices. I shut down the WinXP guest. The USB devices were not listed when I tried to add them in the VBox GUI. From a terminal, I did a VBoxManage list usbhost to get a listing of my connected USB devices. I printed that out. Then I went back in to the VBox GUI to set up USB filters for those devices. As soon as I added one, the others became visible. I added the others (4 total) and shutdown the VBox GUI. Re-booted Linux and tried to bring back up VBox and start my WinXP guest. The VBox interface won't even start to show. I immediately get an error message.
VirtualBox Critical error
Failed to create the VirtualBox COM Object
The application will now terminate
Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)
I checked this forum for possible causes and came up with similar problems which were resolved by deleting the /home/user/.VirtualBox directory and letting VBox build a new one when it restarts. I renamed my .VirtualBox directory and VBox made a new one, but that didn't help. I renamed my /opt/VirtualBox-2.1.0 directory and re-installed VBox v2.1. again, but I still get the same error. Checking the VBox.log file doesn't help because VBox doesn't get far enough before it crashes to make a log file.
Any suggestions to resolve this?
Thanks.
VirtualBox Critical error
Failed to create the VirtualBox COM Object
The application will now terminate
Callee RC: NS_ERROR_FACTORY_NOT_REGISTERED (0x80040154)
I checked this forum for possible causes and came up with similar problems which were resolved by deleting the /home/user/.VirtualBox directory and letting VBox build a new one when it restarts. I renamed my .VirtualBox directory and VBox made a new one, but that didn't help. I renamed my /opt/VirtualBox-2.1.0 directory and re-installed VBox v2.1. again, but I still get the same error. Checking the VBox.log file doesn't help because VBox doesn't get far enough before it crashes to make a log file.
Any suggestions to resolve this?
Thanks.