Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Harshavardhan Putta (Harshavardhan)
OCBC Bank
Harshavardhan Putta
OCBC Bank
US
Harshavardhan Member since 2015 5 posts
OCBC Bank
Posted: Apr 26, 2016
Last activity: Jan 6, 2017
Posted: 26 Apr 2016 1:21 EDT
Last activity: 6 Jan 2017 10:26 EST
Closed

Virtual Box Error

Hi,

Im trying to up the Decision Management Virtual Machine through Virtual Box as mentioned in configuration PDF given in that course,


After installation of virtual box, Virtual Box-Host Only Network adapter is created in ( Network and Internet>Network Connections ) of my machine,

but when I started virtual box and trying to open VM , facing this error :


" Failed to open session for the virtual machine Pega Marketing Enablement 7.13 ML9 "
" Failed to open/create the internal network
'HostInterfaceNetwrking-VirtualBox Host-Only Ethernet Adapter' (VERR_SUPDRV_COMPONENT_NOT_FOUND)
Fialed to attach the network LUN
(VERR_SUPDRV_COMPONENT_NOT_FOUND)
 

Result Code : E_Fail ( 0x80004005)
Component: ConsoleWrap "

 

Please any one can help me out in this issue,
Thanks in advance
 

To see attachments, please log in.
Pega Academy

Posted: 8 years ago
Posted: 26 Apr 2016 3:02 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

Harshavardhan,

In addition, please make sure you did setup the "VirtualBox Network Preferences" as specified on page 5 of the "Quick Start Guide":

http://pegasystems2.http.internapcdn.net/pegasystems2/exercise_guides/PA_Virtual_Machine_Quick_Start_Guide_12_14_15.pdf

Marco.

To see attachments, please log in.
Posted: 8 years ago
Posted: 26 Apr 2016 3:34 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

Harshavardhan,

Thanks a lot for the additional information you are using Windows 10. The following might be your solution:

--

Apparently there are some some issues with NDIS6 driver in Windows 10, I don’t know the details as well however there are a whole bunch of discussions with this breaking virtual machines network.

Uninstalling then re-installing VirtualBox with the parameter NETWORKTYPE=NDIS5 fixed this teething issue for me.

  • Open PowerShell command line
  • Navigate to the directory where you download VirtualBox 5 installer
  • Run: .\VirtualBox-5.0.10-104601-Win.exe -msiparams NETWORKTYPE=NDIS5
  • Follow the installations as usual
  • Try to re-run vagrant up and it’ll be all good.

--

http://www.codingepiphany.com/2015/11/22/virtualbox-5-host-only-error-failed-to-attach-the-network-lun/

Marco.

Show More

Harshavardhan,

Thanks a lot for the additional information you are using Windows 10. The following might be your solution:

--

Apparently there are some some issues with NDIS6 driver in Windows 10, I don’t know the details as well however there are a whole bunch of discussions with this breaking virtual machines network.

Uninstalling then re-installing VirtualBox with the parameter NETWORKTYPE=NDIS5 fixed this teething issue for me.

  • Open PowerShell command line
  • Navigate to the directory where you download VirtualBox 5 installer
  • Run: .\VirtualBox-5.0.10-104601-Win.exe -msiparams NETWORKTYPE=NDIS5
  • Follow the installations as usual
  • Try to re-run vagrant up and it’ll be all good.

--

http://www.codingepiphany.com/2015/11/22/virtualbox-5-host-only-error-failed-to-attach-the-network-lun/

Marco.

 


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 28 Apr 2016 3:31 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

Tushar,

Thanks a lot for your post.

Please share a bit more information regarding your situation:

  • What is your exact error message?
  • What machine to do you have?
  • What version of the operating system?
  • Is this the first time you use VirtualBox on your system?
  • Does it also fail with other exercise systems?

Marco.

To see attachments, please log in.
Posted: 8 years ago
Posted: 26 Apr 2016 3:50 EDT
Paul Hirszowicz (HIRSP) Director, Software Engineering
Pegasystems Inc.
GB

Hi,

If the reinstall as suggested by Marco does not work  could you also try

vboxmanage list -l hostonlyif

You wil find the vboxmanage program in Oracle\virtualbox directory

This may help to identify the issue.

 

Paul

 

 

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 0:11 EDT
Bharath Balasubramanian (BHARATHB)
Cisco Systems
Engineer, IT
Cisco Systems
IN

Having the above issue when i try to set up the VM for SSA course in the Windows 7 machine.Appreciate your help on this

Regards

bharath

To see attachments, please log in.
Posted: 8 years ago
Posted: 18 May 2016 12:11 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

Bharath,

Thanks a lot for your post.

So we can be of better help, it would be great if you can be as specific as possible regarding the error message you are getting?

Marco.

To see attachments, please log in.
Posted: 8 years ago
Posted: 26 Oct 2016 7:24 EDT
Sankhadeep Banerjee (_SanB4461)
Accenture Technology Services
Architect
Accenture Technology Services
IN

Hi - I am getting the attached exception on a Windows 10 machine , using Virtual Box 5.1.8 build while running Pega Marketing Enablement 7.13 ML9.Basically the error message is "Process Verification Failure - The process has more than one thread " . Please note virtualization is enabled on my laptop. I am loading the image directly by doing a machine-> Add .I have validated network settings as per quick start guide.Please help.

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 26 Oct 2016 7:28 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

SanB4461,

My recommendation is to follow the advice in the error message: "Please try reinstalling VirtualBox"

In addition, when running a Google search on "supr3hardenedwinrespawn" I found the following: http://letusexplain.blogspot.nl/2015/08/error-relaunching-virtualbox-vm-process.html

Marco.

To see attachments, please log in.
Posted: 8 years ago
Posted: 27 Oct 2016 2:00 EDT
Sankhadeep Banerjee (_SanB4461)
Accenture Technology Services
Architect
Accenture Technology Services
IN

Hi Marco - Thanks for your quick reply. I actually uninstalled and installed Virtual box and different versions also multiple times without any change in exception. As advised by the link above the solutions are 

1> Registry change : That particular entry is not available in my registry

2>Uninstalling Antivirus : Not possible in workplace !

3>Installing old Virtual box : Suggestion in this site was to roll back to Virtual Box 4.3.12 .I tried installing that but unfortunately it cannot support Windows 10 guest OS.

I am trawling the relevant forums for a solution to this, if any of you came accross a solution please let me know.

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 27 Oct 2016 3:18 EDT
Updated: 27 Oct 2016 4:02 EDT
Marco Looy (Marco Looy)
PEGA
Senior Director, 1:1 Customer Engagement and CRM Enablement Programs
Pegasystems Inc.
NL

SanB4461,

Since you are using Windows 10, please make sure you did not run into the NDIS6 driver problem.

--

Apparently there are some some issues with NDIS6 driver in Windows 10, there are a whole bunch of discussions with this breaking virtual machines network.

Uninstalling then re-installing VirtualBox with the parameter NETWORKTYPE=NDIS5 fixed this teething issue for me.

  • Open PowerShell command line
  • Navigate to the directory where you download VirtualBox 5 installer
  • Run: .\VirtualBox-5.0.10-104601-Win.exe -msiparams NETWORKTYPE=NDIS5
  • Follow the installations as usual
  • Try to re-run vagrant up and it’ll be all good.

--

http://www.codingepiphany.com/2015/11/22/virtualbox-5-host-only-error-failed-to-attach-the-network-lun/

Marco.

To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Jan 2017 9:19 EST
Sundar Raj Jaganathan (SundarRaj)
Roche Services and Solutions
Pega Senior Developer
Roche Services and Solutions
MY

Hi All,

I tried all the above options uninstalling the virtual box and install it again, My virtual box version is 5.0.10 and the latest 5.1.12 also i tried. Windows 7 64 bit version,

Same error-- Kindly help what to do

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

 

Result Code:

E_FAIL (0x80004005)

Component:

ConsoleWrap

Interface:

IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
To see attachments, please log in.
Posted: 7 years ago
Posted: 6 Jan 2017 10:26 EST
Paul Hirszowicz (HIRSP) Director, Software Engineering
Pegasystems Inc.
GB

Hi,

I am assuming you are running windows 10, please correct if this is not the case.

There a lot of posts concerning this issue.  Have you tried disabling then enabling Virtual Box NDIS6 bridged network adapter? 

If the adapter is disabled enabled, if it is enabled disable it then enable it.

You will find the adapter under Windows Network Connections when you open the property panel for the VirtualBox host only adapter.

  1. Open Windows Network Connections
  2. Right click on VirtualBox Host only adapter that created
  3. Choose properties
  4. Check "VirtualBox NDIS6 Bridged Networking driver"
  5. disable and Enable the adapter

Please email me if you have alreay tried it or it did not work.

Paul

 

 

 

 

 

 

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice