Some sort of .net based failure

[Robert Plummer]

The microsoft .net frame work fails when I go to import a license key for this accounting software that we use. The software's name is SageMaster Builder. I've tested the software of both windows xp & sbs 2003, both with .net 1.1 2.0 3.0 & 3.5 installed and fully patched.

I've spend hours on the phone with Sage and they say that the root is VirtualBox. I've used reflector to peak at the code, but I can't seem to find the class. The error details are found in the attached files.

[Robert Plummer]

Here is the error from the Windows Guest

Event Type: Error Event Source: Sage.Sage.Licensing.LicenseStore Event Category: None Event ID: 0 Date: 3/31/2009 Time: 8:36:09 PM User: N/A Computer: SAGESERVER Description: Invalid license data. Details: Object reference not set to an instance of an object.

For more information, see Help and Support Center at ​http://go.microsoft.com/fwlink/events.asp.

Event Type: Error Event Source: Sage.Sage.Licensing.LicenseStore Event Category: None Event ID: 0 Date: 3/31/2009 Time: 8:36:09 PM User: N/A Computer: SAGESERVER Description: Invalid license data. Details: Object reference not set to an instance of an object.

For more information, see Help and Support Center at ​http://go.microsoft.com/fwlink/events.asp.

[Frank Mehnert]

I've removed your last comment. Please Attach the VBox.log file.

[Robert Plummer]

VBox Log File

[Robert Plummer]

Is there anything else that I need to do? This is my first time submitting a ticket. I'm a developer, just not familiar with the framework that virtualbox uses...

[Sander van Leeuwen]

Could you properly enable VT-x in your computer's BIOS and try again? It could be that the piracy prevention mechanism in the application tries to determine if you're using a debugger. This will fail with software virtualization, but works with VT-x.

[Robert Plummer]

I had it enabled, I added nested mode and I received the same issue. Is it possible that there is something else linked to VT-x that needs to be enabled as well? What other things should I try?

[Sander van Leeuwen]

Your BIOS didn't enable VT-x properly, so VirtualBox can't use it. You should check your BIOS settings and if that doesn't help, try to find an update.

[Robert Plummer]

How do you know that it failed? Are you referring to the virtual system's bios or the server? How should I detect if it failed?

[Sander van Leeuwen]

I'm referring to your host (non-virtual/real) system. I can tell, because of the log file entries related to VT-x. You can check yourself by hovering the mouse pointer over the 'V' status icon in the VM window or by checking the VM information dialog.

[Robert Plummer]

What do you think the setting would be called in the server's bois? It's a newer dell server, quad core xeon based. I'm not in front of the system but will check on that as soon as I am.

[Frank Mehnert]

No response, closing.