"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 Access Client Solutions Windows Application Package installation. The error implies that an executable or dynamic link library (dll) is at a different version or service level than another, dependent DLL.

The usual cause of the error is that a program or DLL file is copied into another directory. For example, a user might mistakenly copy a file such as rmtcmd.exe or rtopcb.exe to their own directory rather than copy a shortcut to the file. When the client is upgraded, the installation code does not locate or upgrade files outside of the normal installation path, and this older file might fail to run.

A second cause of the problem involves developers distributing applications that use Access Client Solutions APIs. They might mistakenly redistribute the files that are used by the application. In this situation, the application setup program installs a duplicate or overwrites one or more existing files.

A third problem involves shared runtime files that are redistributed by Access Client Solutions. Examples include files such as the Microsoft data access components (MDAC) or Microsoft visual studio C runtime libraries. The setup program for another application might mistakenly down level the DLL or the user's load path might 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.

Problem Resolution

To resolve the problem, first search all drives for any duplicates for the exe or DLL file reporting the error. Delete any duplicate files stored in user directories. This action 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 Access Client Solutions Windows Application Package is required. First, uninstall the client. After a reboot, search all 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, reinstall Access Client Solutions Windows Application Package.

Finally, it might be necessary to walk the dependency tree of the failing program and check each file for the proper version and for duplicates.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.