Aruba Apps

last person joined: yesterday 

The HPE Aruba Networking Apps board is designed to address questions, comments, and feature requests for all HPE Aruba Networking mobile Apps
Expand all | Collapse all

ISAKMP stack could not be initialized

This thread has been viewed 6 times
  • 1.  ISAKMP stack could not be initialized

    Posted Jun 01, 2018 07:45 AM

    Hi,

     

    We have a customer with a Aruba Wireless Controller 3400. They use the Aruba VIA client. After upgrading their laptops to Windows 10 a few of the users get the message "ISAKMP stack could not be initialized". The preshared key is set in the setup. The customer is reimaging the laptops to solve it, but this is just a workaround. Any idea how to solve this without a reimage?

     

    Thanks.



  • 2.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 01, 2018 09:10 AM

    Did they try uninstalling and then reinstalling the client?



  • 3.  RE: ISAKMP stack could not be initialized

    Posted Jun 19, 2018 07:39 AM

    With reimaging the complete laptop is being reinstalled. So yes, the VIA client is reinstalled. This fixes the problem, but the client wants to know if this can be solved without reinstalling.



  • 4.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 19, 2018 08:42 AM

    To be clear:

     

    Your customer upgrades the OS of a computer from Windows 7 to Windows 10 and the VIA client fails to work?



  • 5.  RE: ISAKMP stack could not be initialized

    Posted Jun 19, 2018 08:44 AM

    They use SCCM to reimage the laptops. All content is deleted and reinstalled. Including the VIA Client. Exept some VIA clients give the message "ISAKMP stack could not be initialized".



  • 6.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 19, 2018 08:58 AM

    You mentioned reimaging with SCCM works but upgrading from 7 to 10 does not work.  Is that correct?



  • 7.  RE: ISAKMP stack could not be initialized

    Posted Jun 19, 2018 09:01 AM

    Upgrading OS works fine. Its just the VIA Client. After installing they try to connect with the VIA Client and then they get the error message "ISAKMP stack could not be initialized" inside the VIA Client



  • 8.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 19, 2018 09:07 AM

    It is entirely possible that the VIA client installs libraries on Windows 7 that do not work on Windows 10.



  • 9.  RE: ISAKMP stack could not be initialized

    Posted Jun 19, 2018 09:12 AM

    Most of the devices work fine on Windows 10. Just a few aren't working. But the customer wants a solution without reinstalling.



  • 10.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 19, 2018 09:15 AM

    Let me check with Engineering to see if this is possible.



  • 11.  RE: ISAKMP stack could not be initialized

    EMPLOYEE
    Posted Jun 19, 2018 09:53 AM

    If the customer does this upgrade again and it fails, they should open a TAC case.  Engineering says there is no known issue with this, as long as you are running the 3.2 version of the VIA client.