Unable to launch SAS Uni Edition using VirtualBox

[ehis]

Failed to open a session for the virtual machine SAS University Edition.

The virtual machine 'SAS University Edition' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\Ufa\VirtualBox VMs\SAS University Edition\Logs\VBoxHardening.log'.

Result Code:	E_FAIL (0x80004005)
Component:	MachineWrap
Interface:	IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}

[ChrisBrooks]

This is a VirtualBox error which might be something to do with a Windows update as here -> https://forums.virtualbox.org/viewtopic.php?f=6&t=85336 are you running the latest version of VirtualBox?

[ehis]

Hi Chris, I actually did start with 5.2.6 version of VirtualBox which did not show the SAS logo, and did not launch SAS, only ended up showing a number of scripts before the black blank screen. There was no error indicated as the one I showed in my earlier posting.

Many thanks for checking with me. Any assistance will be highly appreciated.

[ChrisBrooks]

In your VM settings in VirtualBox what do you have for Network Adaptor on the Network tab? It should be set to NAT, if not that might be the issue.

[ehis]

Hi ChrisBrooks,

I have checked. It was set to NAT.

[ChrisBrooks]

I think at this point the easiest thing to do would be to delete and reinstall both VirtualBox and SAS UE after re-downloading the VM from SAS. That seems to fix 99% of all problems.

[ehis]

Hi ChrisBrooks, Many thanks for your continious efforts to help me find a solution. I have deleted and reinstall both softwares. It did not resolve the problem. The same problem still persist. Kind regards, Ehis

[ChrisBrooks]

That really is a puzzle - as I said reinstalling usually solves the vast majority of issues. You could try raising a track with SAS Support which you can do here http://support.sas.com/ctx/supportform/createForm or try raising it on the Virtual Box forums here https://forums.virtualbox.org

[ehis]

Hi ChrisBrooks,

Many thanks. Will followup with your suggestions, and keep you updated.

Kind regards,

Ehis

[nahideraha]

Hi,

I was facing the same error and all I did is just updated my VM box to the latest version 5.2.8. That seems to solve my error.

Thanks