The VBox 'Main' server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED
When trying to start the VBox 'Main' server (VBoxSVC.exe), the VBoxXPCOMIPCD.exe (the XPCOM IPC daemon) won't spawn, an error from this ticket title is returned. But if I start VBoxXPCOMIPCD.exe daemon manually, then it starts successfully.
But if I then try starting an appilcation, using the VBox XPCOM API (a user interface app, or a tstVBoxAPIXPCOM.exe testcase), then the next error in ticket #14 occurs.
Change History
(11)
Owner: |
set to Valery V. Sedletski
|
Status: |
new → assigned
|
Description: |
modified (diff)
|
Summary: |
The VBoxSVC.exe won't start with NS_ERROR_FACTORY_NOT_REGISTERED → The XPCOM server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED
|
Summary: |
The XPCOM server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED → The VBox 'Main' server app. won't start with NS_ERROR_FACTORY_NOT_REGISTERED
|
Description: |
modified (diff)
|
Description: |
modified (diff)
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
Resolution: |
fixed
|
Status: |
closed → reopened
|
Resolution: |
→ fixed
|
Status: |
reopened → closed
|
Now localized the problem to the concrete file. The problem is with XPCOM, which is the same version xpcom18a4 now and back in 2008 (from the last OS/2 port). It appears that since that, much VBox-related changes are applied to XPCOM. Yesterday I tried to revert back the src\libs\xpcom18a4\ipc\ipcd subdirectory to the old version (of year 2008, the changes patch to IPCD is about 70 KB in size). Then VboxXPCOMIPCD.exe become to remain demonized when I start VBoxSVC.exe. So the problem is, very likely, here. And even more -- today I reduced the problem footprint to a file: it is sufficient to revert only src\libs\xpcom18a4\ipc\ipcd\client\src\ipcdclient.cpp file, so, the problem seems to be here.