DLink GWL-G630 Entry Point Problem - wlanapi.dll

Discussion in 'Wireless Networks' started by Duckysan1, May 6, 2008.

  1. Duckysan1

    Duckysan1 Guest

    Since upgrading my Acer laptop (Travelmate 2300) to XP SP3, I cannot use the
    Dlink utility. I receive the following error:

    'The procedure entry point apsGetInterfaceCount could not be located in the
    dynamic link library wlanapi.dll'
    I have removed and re-installed the drivers/software, but no improvement.
    Web search suggests compatibility problem with Dlink driver/dll.
    Whilst I still have wireless connectivity, the Dlink utilities do not work.
    It seems this is an SP3 issue - other users report the issue is resolved if
    they revert back to SP2.
    There must be a better resolution!
     
    Duckysan1, May 6, 2008
    #1
    1. Advertisements

  2. Duckysan1

    Barb Bowman Guest

    either use Windows native WZC features to manage the wireless
    (uninstall the utility and keep the wireless) or contact D-Link
    support/search their downloads for a fixed version.

    --

    Barb Bowman
    MS-MVP
    http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
    http://blogs.digitalmediaphile.com/barb/
     
    Barb Bowman, May 6, 2008
    #2
    1. Advertisements

  3. Duckysan1

    Duckysan1 Guest

    Thanks for the comments.
    It seems XPSP3 adds a new version of wlanapi.dll that conflicts and replaces
    the Dlink DLL. I have written to Dlink, but am not holding my breath. The
    following appears on the 'Tech ARP' site:

    "Windows XP SP3 introduces a new .dll file that is named Wlanapi.dll.
    Certain device driver installations for some third-party wireless network
    adapters also install a Wlanapi.dll which will be replaced by SP3 resulting
    in errors.

    This error message will appear during every restart after you install
    Windows XP Service Pack 3 : "The procedure entry point apsSearchInterface
    could not be located in the dynamic link library wlanapi.dll"

    Impact : Low – Obtaining updated drivers for the WLAN device resolves this
    issue
    KB Content : KB 950720"

    I'll check it out.
     
    Duckysan1, May 6, 2008
    #3
  4. Duckysan1

    Pavel A. Guest

    Wlanapi.dll is part of the new wireless API introduced quite long
    ago in KB918997, and now integrated into SP3.

    The Dlink package could include some other version of this dll,
    because the Microsoft's wlanapi.dll does not have export
    function named "apsSearchInterface".
    IMHO Dlink should work with MS to resolve this issue.

    Regards,
    --PA
     
    Pavel A., May 6, 2008
    #4
  5. Duckysan1

    Barb Bowman Guest

    It isn't just D-Link, that utility is supplied by the wireless
    chipset manufacturer and customized by multiple folks using that
    chipset. When they get bits from the source...

    --

    Barb Bowman
    MS-MVP
    http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
    http://blogs.digitalmediaphile.com/barb/
     
    Barb Bowman, May 7, 2008
    #5
  6. ciccio formaggio, May 9, 2008
    #6
  7. Duckysan1

    ciccio Guest

    The solution is here
    http://kb.cadzow.com.au:15384/Cadzow/details.aspx?ID=1898

    The D-Link AirPlus Utility does not work with Windows XP Service Pack 3. Upon loading, it displays: “AirGCFG.exe - Entry Point Not Found. The procedure enry point apsGetInterfaceCount could not be located in the dynamic link library wlanapi.dll.”.
    A workaround is to use the pre-SP3 version of wlanapi.dll and place it in the appropriate directories. Upon loading, this version of the file will be used instead of the version in the System32 directory.

    xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\D-Link\AirPlus G"
    xcopy %Windir%\$NtServicePackUninstall$\wlanapi.dll "%ProgramFiles%\ANI\ANIWZCS2"
     
    ciccio, May 9, 2008
    #7
  8. Duckysan1

    Pavel A. Guest

    in message
    Again, the "pre-SP3 version" makes no sense. This DLL conflict can occur
    even on SP2 with KB KB918997, so whoever maintains AirGCFG.exe is
    going to rename their DLL, or, at least, install it into their app dir
    instead of system32.

    Regards,
    --PA
     
    Pavel A., May 10, 2008
    #8
  9. Duckysan1

    rmsanangelo Guest

    can you please post the exact steps to fix this? I need help, thanks!
     
    rmsanangelo, Jun 2, 2008
    #9
  10. Duckysan1

    Sergey U. Guest

    Unfortunately for my DI-624 did not work.
     
    Sergey U., Jun 15, 2008
    #10
  11. Duckysan1

    Barb Bowman Guest

    Barb Bowman, Jun 15, 2008
    #11
  12. Duckysan1

    Sergey U. Guest

    Sorry, I put wrong data : indeed I have a wireless card DWL-G520 rev.B, with
    which the problem is associated ( on top of that, yes, I have a router DI-624
    but it does not relates to the issue :) ).

    I updated DWL-G520 rev.B driver to version 4.40 ,as prescribed on
    www.dlynk.com, for SP3 upgrades, and I still got two messages:

    AirPlusCFG.exe Entry Point Not found apsGetInterfaceCount not located in the
    dynamic link library wlanapi.dll

    WZCSLDR2.exe Entry Point Not found aosInitialize not located in the dynamic
    link library wlanapi.dll

    So, the problem looks to be same as described above.

    I tried to copy files as suggested above , did not work...
     
    Sergey U., Jun 15, 2008
    #12
  13. Duckysan1

    Barb Bowman Guest

    you don't actually need the DLink utility to manage the wireless.
    you can use Windows built in features to do that. you can uninstall
    the AirPlus config utility.

    --

    Barb Bowman
    MS-MVP
    http://www.microsoft.com/windowsxp/expertzone/meetexperts/bowman.mspx
    http://blogs.digitalmediaphile.com/barb/
     
    Barb Bowman, Jun 15, 2008
    #13
  14. Duckysan1

    turfsurf Guest

    "...could not be located in the dynamic link library wlanapi.dll"
    I had this same problem after upgrading to sp3.I have a D-Link AirPlus G DWL-G510 Wireless pci adapter.(DESKTOP PC)
    A very simple fix is to:

    1.Boot in safemode with networking (F8 on start up)
    2.Go to C:\WINDOWS\system32
    3.You will probably find two "wlanapi.dll"
    that is: wlanapi.dll and wlanapi(2).dll
    4.wlanapi(2).dll is from sp3 (didn't overwrite
    previous one.)
    5.Delete wlanapi.dll and rename wlanapi(2).dll to
    wlanapi.dll and reboot.
    6.Worked fine for me
     
    turfsurf, Oct 22, 2008
    #14
  15. Duckysan1

    Pavel A. Guest

    Get the SP3 compatible update for your D-Link software/driver.
    For details, search archive of this NG, this has been already discussed
    here.

    Regards,
    --PA
     
    Pavel A., Oct 22, 2008
    #15
  16. Duckysan1

    leyland Guest

     
    leyland, Nov 25, 2008
    #16
  17. Duckysan1

    leyland Guest

    On booting up I am shown the WZCSLDR2/WLANAPI.DlL/apsGetReady. I've tride to
    remove this no joy. I then discover that there are spyware companies claiming
    to be able to remove this, of course for a fee. Do these work ?.
    Just what is Windows doing to resolve this problem. Are they working on this
    as we speak. Come on Windows you must be aware of this problem, give us an
    answer.
     
    leyland, Nov 25, 2008
    #17
  18. Duckysan1

    R. McCarty Guest

    Not a Windows/Microsoft issue at all. You have a support applet for
    a Wireless card that is attempting to start at boot. Either the .Dll is not
    found or the registration for it is missing/incorrect.
    Several options - either use Windows Native Wireless to control the
    device or check your card's vendor website for an updated driver &
    support applet.
     
    R. McCarty, Nov 25, 2008
    #18
  19. Actually it is a Microsoft/Windows issue. They rewrote a dll file, that Dlink was using, with the
    issue of SP3.
    The new dll file is not compatible with the DLink drivers.
    However DLink should now have a patch, or new driver, for their card. But seems they don't care
    about some older cards.
    Going to "msconfig" and turning off the DLink monitoring software stops the nag window and does not
    stop the card operation.

    | Not a Windows/Microsoft issue at all. You have a support applet for
    | a Wireless card that is attempting to start at boot. Either the .Dll is not
    | found or the registration for it is missing/incorrect.
    | Several options - either use Windows Native Wireless to control the
    | device or check your card's vendor website for an updated driver &
    | support applet.
    |
    | | >
    | > On booting up I am shown the WZCSLDR2/WLANAPI.DlL/apsGetReady. I've tride
    | > to
    | > remove this no joy. I then discover that there are spyware companies
    | > claiming
    | > to be able to remove this, of course for a fee. Do these work ?.
    | > Just what is Windows doing to resolve this problem. Are they working on
    | > this
    | > as we speak. Come on Windows you must be aware of this problem, give us an
    | > answer.
    | >
    |
    |
     
    Richard in AZ, Nov 25, 2008
    #19
  20. Duckysan1

    R. McCarty Guest

    Thanks for the additional info, wasn't aware of the circumstances of the
    ..Dll.
     
    R. McCarty, Nov 25, 2008
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.