Home → Guides :: Symphony OCR → Troubleshooting Tips and Tricks → Worldox API (WDAPI32, WBAPI) crashing
Symphony OCR uses the Worldox API to interact with your Worldox document repository. This API consists of a DLL called WDAPI32.DLL and an executable called WBAPI.EXE. If these libraries are loaded from the server (instead of local to the Symphony workstation), any network interruption can cause the Worldox API to crash. This will not completely bring Symphony OCR down, but it does cause problems, and it is generally best to load those libraries from the local C drive of the Symphony machine.
Symphony OCR uses the workstation's system path to determine the location it should load libraries from. Worldox sets the system path appropriately whenever Worldox, WDMirror or WDIndex are launched. If you launch Worldox or WDIndex directly from your file server, then the system path will be configured pointing at the file server. If you use WDMirror, then the system path will be configured to point at the local C:\Worldox folder of the workstation. This later is what you want.
On the Symphony workstation, check all of the shortcuts you use to launch Worldox or WDIndex ande confirm that they are using WDMIRROR.EXE to launch. If you find any shortcuts that are launching worldox.exe, wdindex.exe, wbindex.exe (or any other executable besides wdmirror.exe), replace them with equivalent wdmirror.exe commands.
For example, here is the correct way to launch Worldox:
<network path to Worldox>\wdmirror.exe
or
C:\Worldox\wdmirror.exe
And here is the correct way to launch WDINDEX:
<network path to Worldox>\wdmirror.exe /wdindex
After you fix the shortcuts (remember to check the Start->Startup shortcuts also!!):