The ordinal 13194 could not be located in the dynamic link library

First of all, uninstall Smartwatch from your pc, then RIGHT-CLICK the START button on your pc. Next, click on POWERSHELL (ADMIN), then type in the following command: sfc /scannow then hit the ENTER key. Allow the System File Checker (SFC) to check for errors. It should normally repair any hiccups for you. When this has finished, enter this command line:
chkdsk c: /r (FYI, this translates as CHECK DISK C: then REPAIR any other errors). You may see a prompt, advising that the disk is currently "locked", and will ask if you want to run this command at next reboot, offering a Y/N scenario. Type Y at this point, then click to RESTART your computer. CHKDSK should now run a 5-stage repair/check of the disk. This may take a bit of time, so chill out with a cuppa at this stage. Once CHKDSK has finished, your pc will reboot to the normal login screen. Once logged in, try reinstalling SmartSwitch. Hopefully, it will now run as expected.

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

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Component":"Access Client Solutions Windows Application Package","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"Version Independent","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]

The 'Ordinal not sound' error message can come accompanied by different messages making diagnostics somewhat tricky. It's usually accompanied by a number (ordinal XXX) and sometimes includes a specific DLL message. Here are the steps you can try to resolve this error.

1: Install the Latest Visual Runtime Files

Microsoft Visual C++ Redistributable Package contains the run-time components of Visual C++ Libraries needed for running applications on a PC without Visual C++ installed. Most DLL errors are because of a missing runtime.

You have two choices here. You can try the official Microsoft Visual C++ Redistributable Package, and that should work for most people.

The other option that might work if your problem is with an older app or game is to use a bundle that includes all of the Visual C++ files. We'd only try this is the official pack failed you. The Visual C++ Redistributable Runtimes AIO Repack is a good choice.

2: Check for and Install the Latest Windows Updates

We've seen Windows Updates waiting for a reboot cause this problem. Check Windows updates.

One of the best tricks anytime Windows Updates won't install, or gets what we called stuck, is to delete pending Windows Updates by deleting or renaming the Software Distributions folder. By removing this folder, Windows will recreate it after a reboot and begin to download any pending Windows Updates.

If you prefer, here's a step-by-step video guide on deleting pending Windows Updates.

You can also follow the steps at How-To Delete Pending Windows Updates.

3: Install OpenSSL for Windows

This fix is for last because it assumes your error message names LIBEAY32.DLL as the culprit. Ironically, OpenSSL relies on Visual C++ libraries mentioned in the first step.

You can download the latest OpenSSL at https://wiki.openssl.org/index.php/Binaries.

Note there are two packages. One includes Visual C++ runtimes, and one does not. If you already completed the first step, download the one without them. The last we checked, the first download listed included the runtimes and the second did not.

Similar:

How do you fix ordinal not found?

How do I fix ordinal 12404 not found for Samsung Smartswitch?

What is the ordinal 345?