CO_E_NOTINITIALIZED

[Rassman48]

Using VirtualBox r0 of Vista.

From today I am getting

Failed to create new session.
Then in the details.

CalleeRC CO_E_NOTINITIALIZED (0x800401F0)

I have two VMs one being the main one Debian, the other SLED which was only on to try it.

But have worked for quite a long time, with the Debian being booted every day. The error just started today on both VMs.

According to an internet search I am the only person in the entire universe with this problem. But I am a bit stuck without my Debian.

Nothing has changed on my PC since yesterday when I was last in.

What should I look at and more important what none-destructive attempts can I use to recover them. As the Debian is the main one, I am willing to experiment with the SLED if needed.

[Perryg]

Sounds like a COM problem. Try completely closing down VBox and make sure that the VBoxsvc.exe is shut down in the task manager. Then restart VBox and see if this fixes your problem.

[Rassman48]

No sorry, I have restarted a couple of times.

A reinstall of VirtualBox hasn't fixed it, I also get the same error when I try to add a new VM.

So, I accept that it may be some unknown change on the PC that has caused this, though I haven't had any updates since VirtualBox died.

And as the first one (going by a google search) to get this error then I'm not likely to get a fix. But right now if someone from Sun could just tell me what the error means, then at least I have a clue.

[Rassman48]

Windows logs for VirtualBox is

Error 21/05/2009 12:10:16 Application Hang 1002 (101)

I think that Sun would be interested in a fault that can occur out of the blue on a trouble free Vista instal, that can not be repaired from a complete uninstall/install.

There are no updates in my logs between the last day that VirtualBox worked until the next day when it didn't.

Right now I just can not have VirtualBox on my vista because nothing of VBox works anymore. I am sort of worried now that if a VirtualBox on a server fails for the same reason, then how does the network manager find a solution? Because right now he he can not even find out what the error message is trying to tell him.

[Perryg]

Hummm!
First, since you can install VBox and it solves nothing I have my doubts that it is because of this program. It could be but there are a lot of other things that can cause this. I am posting a link at the last of this post of various places/things to do. Also I noticed that the problems started shortly after a Microsoft Patch Tuesday. Can you look back at the patch log and see what was changed. If you are just wanting to get this going and have not installed any programs that you can not reinstall do a system restore to the point before it failed.

http://www.google.com/search?q=Applicat ... 1002+(101)

[Alesis1001]

I ran into this weird error on Vista, but only when I installed MS Office 2007 enterprise version.
It's on a new Dell studio 14, only available in asia.

Virtualbox simply crashes when I try to do anything with the menu or the buttons. The "About" information
shows the version of virtualbox as simply "r0" although I installed 3.0.6. I get the same application
crash with 3.0.4. Uninstalling and installing virtualbox doesn't solve the problem. When I uninstalled
MS Office 2007, virtualbox was running fine again. The error report shows the crash occurring with ole32.dll.
I'm bummed since I have to use MS office as well.

I have the same MS office installed on an windows XP machine and there I don't have any problems.

I can provide some additional info if needed.