none
WiFi / WEC 7 / headless system exception in eapcfg due to dependency on netui.dll RRS feed

  • Question

  • We have an NDIS 5.1 WiFi adapter that works only with WEP.

    We are porting our arm device from WEC6 to WEC7.  Our device is headless.  We are trying to track down an exception in eapcfg due to user authentication request on a system image that has no shell.  The issue seems to be a dependency on netui.dll.  

    We have tried removing the UI elements out of netui.dll however so far it did not have the desired effect.

    Any thoughts?


    • Edited by WEC67 Friday, June 22, 2018 4:06 PM
    Friday, June 22, 2018 1:08 AM

Answers

  • It appears that you must have a shell in WEC7 to use WiFi and EAP.  WEP works without it.  This has been verified by Microsoft.  

    Here is the stack trace when the UI shows up.  As you can see it is being queued off a worked thread and that it seems to be a retry based off a timeout.  

    EAPPCFG!EapLm::Peer::LegacyEapMethodConfig::ShimEapPeerInvokeIdentityUI(_EAP_METHOD_TYPE * 0x003a11c8, unsigned long 0x00040080, HWND__ * 0x00000000, unsigned long 0x00000048, const unsigned char * 0x003ab8f0, unsigned long 0x00000000, const unsigned char * 0x00000000, unsigned long * 0x002afa1c, unsigned char * * 0x002afa18, wchar_t * * 0x002afa10, _EAP_ERROR * * 0x002afa20)  line

    EAPPCFG!EapLm::Peer::LegacyEapMethodConfig::InvokeIdentityUi(unsigned int 0x003ab8f0, const ConstBuffer & {...}, const ConstBuffer & {...}, HWND__ * 0x002afa1c, TempBuffer<0> & {...}, BasicSimpleString<unsigned short> & {...})  line 403 + 112 bytes

    EAPPCFG!EapHostPeerInvokeInteractiveUI(HWND__ * 0x00000000, unsigned long 0x002afc14, const unsigned char * 0x002afc24, unsigned long * 0x0026b4f8, unsigned char * * 0x00000082, _EAP_ERROR * * 0x0026b4f8)  line 312

    ONEX!OneXShowUI(HWND__ * 0x0000000c, unsigned long 0x01dc0034, _ONEX_UI_REQUEST * 0x00000000, _ONEX_UI_RESPONSE * * 0x00000000)  line 248

    WLANSVC!CeHandleOneXUIRequest(_L2_UI_REQUEST * const 0x00000001, _WLAN_UI_REQUEST * const 0x002afdf8, MSMSEC_UI_REQUEST * const 0x0011c4d0)  line 223 + 20 bytes
    WLANSVC!IntfRetryUIRequest(void * 0x40ac427c)  line 7670 + 12 bytes
    WLANSVC!IntfTimeoutCallback(_WLAN_TIMER_CONTEXT * 0x00118b50)  line 6432
    WLANSVC!TmWrkTimeoutHandler(void * 0x00000102)  line 162
    WLANSVC!SVSThreadPool::Worker(void * * 0x40090bf8)  line 2951
    WLANSVC!SVSThreadPool::SVSThreadPoolWorkerThread(void * 0x00000000)  line 2972
    COREDLL!40039a70()

    • Marked as answer by WEC67 Tuesday, June 26, 2018 12:16 AM
    Tuesday, June 26, 2018 12:16 AM

All replies

  • Thanks IoTGirl,

    I am now wondering if it is due to our NDIS 5.1 wifi adapter:  https://social.msdn.microsoft.com/Forums/en-US/b72ce861-dd99-457b-bbfc-158d6b03cfa5/wifi-driver-in-wec7?forum=winembplatdev

    Friday, June 22, 2018 4:06 PM
  • Sounds plausible.  Have you reached out to the hardware / custom driver supplier for support?
    Friday, June 22, 2018 5:33 PM
    Moderator
  • It appears that you must have a shell in WEC7 to use WiFi and EAP.  WEP works without it.  This has been verified by Microsoft.  

    Here is the stack trace when the UI shows up.  As you can see it is being queued off a worked thread and that it seems to be a retry based off a timeout.  

    EAPPCFG!EapLm::Peer::LegacyEapMethodConfig::ShimEapPeerInvokeIdentityUI(_EAP_METHOD_TYPE * 0x003a11c8, unsigned long 0x00040080, HWND__ * 0x00000000, unsigned long 0x00000048, const unsigned char * 0x003ab8f0, unsigned long 0x00000000, const unsigned char * 0x00000000, unsigned long * 0x002afa1c, unsigned char * * 0x002afa18, wchar_t * * 0x002afa10, _EAP_ERROR * * 0x002afa20)  line

    EAPPCFG!EapLm::Peer::LegacyEapMethodConfig::InvokeIdentityUi(unsigned int 0x003ab8f0, const ConstBuffer & {...}, const ConstBuffer & {...}, HWND__ * 0x002afa1c, TempBuffer<0> & {...}, BasicSimpleString<unsigned short> & {...})  line 403 + 112 bytes

    EAPPCFG!EapHostPeerInvokeInteractiveUI(HWND__ * 0x00000000, unsigned long 0x002afc14, const unsigned char * 0x002afc24, unsigned long * 0x0026b4f8, unsigned char * * 0x00000082, _EAP_ERROR * * 0x0026b4f8)  line 312

    ONEX!OneXShowUI(HWND__ * 0x0000000c, unsigned long 0x01dc0034, _ONEX_UI_REQUEST * 0x00000000, _ONEX_UI_RESPONSE * * 0x00000000)  line 248

    WLANSVC!CeHandleOneXUIRequest(_L2_UI_REQUEST * const 0x00000001, _WLAN_UI_REQUEST * const 0x002afdf8, MSMSEC_UI_REQUEST * const 0x0011c4d0)  line 223 + 20 bytes
    WLANSVC!IntfRetryUIRequest(void * 0x40ac427c)  line 7670 + 12 bytes
    WLANSVC!IntfTimeoutCallback(_WLAN_TIMER_CONTEXT * 0x00118b50)  line 6432
    WLANSVC!TmWrkTimeoutHandler(void * 0x00000102)  line 162
    WLANSVC!SVSThreadPool::Worker(void * * 0x40090bf8)  line 2951
    WLANSVC!SVSThreadPool::SVSThreadPoolWorkerThread(void * 0x00000000)  line 2972
    COREDLL!40039a70()

    • Marked as answer by WEC67 Tuesday, June 26, 2018 12:16 AM
    Tuesday, June 26, 2018 12:16 AM