search

borsitsb / virtualboxservice

Automatically exported from code.google.com/p/virtualboxservice
GNU General Public License v3.0
1 stars 1 forks source link

Add support for 4.2.x #4

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Can support be added for VirtualBox 4.2.x

Original issue reported on code.google.com by a...@trajano.net on 26 Dec 2012 at 9:58

GoogleCodeExporter commented 8 years ago 
Is this service working with 4.2.6?

Original comment by jewelers...@gmail.com on 9 Jan 2013 at 2:39

GoogleCodeExporter commented 8 years ago 
It is working for med with 4.2.6. Just installed it. :)

Original comment by martin.i...@gmail.com on 10 Feb 2013 at 2:57

GoogleCodeExporter commented 8 years ago 
How about 4.2.12? Any issues?

Original comment by van...@gmail.com on 22 May 2013 at 10:45

GoogleCodeExporter commented 8 years ago 
API should be stable for each major release. So if it works on 4.2.x it should 
work on 4.2.12, too. Notice, however, that 4.2.x is currently not officially 
supported. I think I can fix that in a few months and if 4.3.x comes out until 
then, this will be supported, too.

Original comment by Felix.Ru...@gmail.com on 24 May 2013 at 5:13

GoogleCodeExporter commented 8 years ago

Original comment by Felix.Ru...@gmail.com on 24 May 2013 at 5:23

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Running VBox 4.2.12 r84980 on a windows 2011 SBS server and when trying to 
start the service I get this in the eventviewer and a message pops up informing 
me that the service was started but stopped right afterwards:

Der Dienst kann nicht gestartet werden. 
System.Runtime.InteropServices.COMException (0x80080005): Die 
COM-Klassenfactory für die Komponente mit CLSID 
{B1A7A4F2-47B9-4A1E-82B2-07CCD5323C3F} konnte aufgrund des folgenden Fehlers 
nicht abgerufen werden: 80080005 Starten des Servers fehlgeschlagen (Ausnahme 
von HRESULT: 0x80080005 (CO_E_SERVER_EXEC_FAILURE)). bei 
System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, 
Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, 
Boolean& bNeedSecurityCheck) bei System.RuntimeType.CreateInstanceSlow(Boolean 
publicOnly, Boolean skipCheckThis, Boolean fillCache) bei 
System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean 
skipVisibilityChecks, Boolean skipCheckThis, Boolean fillCache) bei 
System.Activator.CreateInstance(Type type, Boolean nonPublic) bei 
VBoxWrapper.COMInterface.ComMachineProxyListBuilder.initVirtualBox() bei 
VirtualBoxService.Service.configureVBoxWrapper() bei 
VirtualBoxService.Service.startMachineController(...

There are some german words in there, if needed I can try to translate it to 
complete english.

Am I doing something wrong?

regards
Michael

Original comment by tcwardr...@gmail.com on 18 Jun 2013 at 2:01

GoogleCodeExporter commented 8 years ago 
On this page, you can find a description of the error and some possible 
solutions: http://blogs.msdn.com/b/adioltean/archive/2005/06/24/432519.aspx

I must admit, that I currently don't have an idea by what this could be caused.
Some things you can try:
1) Close Virtualbox and force close the VBoxSVC.exe (this is the COM-Server) 
before starting the service.
2) Check the Logon-Credentials of the service. The account you use must have 
local admin rights.
3) Try an earlier version of Virtualbox. According to the comment #2 4.2.6 
should work.

Original comment by Felix.Ru...@gmail.com on 18 Jun 2013 at 9:42

GoogleCodeExporter commented 8 years ago 
It's up to V4.3.x right now

I wonder if it is just a matter of setting up the permissions of the COM-Server 
to match the one used by VirtualBox.  Still haven't figured it out myself.

Original comment by a...@trajano.net on 31 Jan 2014 at 10:08