Invalid NETAPI.DLL Error with LM22a/b client for OS/2

RESOLUTION

Remove the reference from the LIBPATH= section and from any other paths in CONFIG.SYS that point to the location of a different NETAPI.DLL. For example, an IBM OS/2 client running IBM's Extended Edition may have these path entries in CONFIG.SYS:

LIBPATH=C:\LANMAN\NETLIB;C:\OS2\DLL;C:\SQLLIB\DLL;C:\CMLIB\DLL;
   C:\;C:\MUGLIB\DLL;
SET PATH=C:\LANMAN\NETPROG;C:\OS2;C:\SQLLIB;C:\CMLIB;C:\OS2\SYSTEM;
   C:\OS2\INSTALL;C:\;C:\BINP;C:\MUGLIB;
SET DPATH=C:\LANMAN\NETPROG;C:\OS2;C:\CMLIB;C:\OS2\SYSTEM;
   C:\OS2\INSTALL;C:\;C:\MUGLIB\DLL;
				

When those references are removed this example reads:

LIBPATH=C:\LANMAN\NETLIB;C:\OS2\DLL;C:\SQLLIB\DLL;C:\CMLIB\DLL;C:\;
SET PATH=C:\LANMAN\NETPROG;C:\OS2;C:\SQLLIB;C:\CMLIB;C:\OS2\SYSTEM;
   C:\OS2\INSTALL;C:\;C:\BINP;
SET DPATH=C:\LANMAN\NETPROG;C:\OS2;C:\CMLIB;C:\OS2\SYSTEM;
   C:\OS2\INSTALL;C:\;
				

If you are running IBM OS/2 Extended Edition (EE) you may not be able to run the NetWare Requester or some EE components (such as COMM Manager) that need the special NETAPI.DLL installed in the MUGLIB directory. OS/2 architecture allows only a single .DLL of a given name, so you must decide whether you want to run COMM Manager or the NetWare Requester. If you use the Requester, you must rename or delete the existing NETAPI.DLL in the MUGLIB directory.