"Ordinal <x> Could Not Be Located in the Dynamic Link Library <y>" Errors
Ordinal not found errors (for example, the ordinal 203 could not be located in the dynamic link library CWBSV.DLL) are the result of a corrupted Client Access installation. The error implies that one Client Access executable or dynamic link library (DLL) is at a different version or service pack level than another dependant DLL.
Resolving the problem
Ordinal not found errors (for example, the ordinal 203 could not be located in the dynamic link library CWBSV.DLL) are the result of a corrupted Client Access installation. The error implies that one Client Access executable or dynamic link library (dll) is at a different version or service pack level than another, dependant DLL.
The usual cause of the error is that a Client Access exe or DLL file has been copied into another directory. For example, a user may mistakenly copy a file such as rmtcmd.exe or rtopcb.exe to their own directory rather than copy a shortcut to the file. When Client Access is upgraded, the installation code will not locate or upgrade files outside of the normal installation path, and this older file may fail to run.
A second cause of the problem involves developers distributing applications that use Client Access APIs. They may mistakenly redistribute the Client Access files that are used by the application. In this situation, the application setup program installs a duplicate or overwrites one or more existing Client Access files.
A third problem involves shared runtime files that are re-distributed by Client Access. These may include files such as the Microsoft Data Access Components (MDAC) or Microsoft Visual Studio C run-time libraries. The setup program for another application may mistakenly downlevel the DLL or the user's load path may contain an older version of the same DLL.
The problem can also be caused by anti-virus programs that prevent the installation of a file during the Client Access setup or restore an older version of the same file.
To resolve the problem, first search all hard drives for any duplicates for the exe or DLL file reporting the error. Delete any duplicate files stored in user directories. This resolves most problems.
If the problem involves a shared runtime DLL (typically a file without the cwb name that resides in the windows system directory), verify that the Windows path does not include a duplicate. Check the application directory and the current directory for the application for a duplicate. See the Microsoft Platform SDK documentation for further details on the search path that is used.
If the problem persists, a reinstallation of Client Access may be required. First un-install the Client Access product. After a reboot, search all hard drives for any file of the type cwb*.*. Delete any files that are found. Next, verify that any anti-virus program is disabled and that the Windows user ID used for the installation is a member of the Administrators group and has all the required rights, NTFS permissions, and registry permissions. Finally, re-install Client Access, and re-install the service pack.
Finally, it may be necessary to walk the dependency tree of the failing executable and check each file for the proper version and for duplicates.
|Operating System||IBM i 6.1|
|Operating System||IBM i 7.1|
More support for:
Access for Windows
Software version: 4.4.0, 4.5.0, 5.1.0, 5.2.0, 5.3.0, 5.4.0, 6.1, 6.1.0, 7.1
Operating system(s): IBM i
Reference #: N1016848
Modified date: 04 November 2012