Incorrect version of shared files

Several files are shared by different variants of Infor BW. It is possible that an incorrect version (or no version at all) of such a shared file exists on your system. For example after several actions (like install, update, uninstall) related to several variants (Baan IVc, LN) of Infor BW. In that case, remove or rename the incorrect file by hand and run the installer of the Infor BW variant which contains the desired version of the file.

The shared files are stored in the directory:

C:\Windows\Baan\bin

Each shared file can be accompanied by an identically named Program Debug Database file with the .pdb extension, e.g. becs.exe may be accompanied by becs.pdb. Both files of such a pair must be of the same date and time. An inconsistency between the date and time of the two files in a pair does not influence the normal functionality of the software. It is only of influence on the informational messages which may be composed during the handling of exceptional runtime errors. When such an inconsistency is observed, remove or rename the complete pair and run the installer of the Infor BW variant which contains the desired version of the file.

A file which is in use, cannot be removed. To find out which program is using a particular file, especially the file ShellExt.dll is difficult This dll contains the software for the Infor Properties tab which has been added to the Properties dialog. See How to determine version information.

ShellExt.dll is loaded as soon as for any file its Properties dialog is shown (even when for that particular file the Properties dialog does not have an Infor Properties tab), In general the dll is not unloaded during the rest of the life time of the process. The best known program which uses this dll is the Windows Explorer.Other programs however also use it, for example. in the standard Open File or Save As dialog. Even when all visible Windows Explorer windows are closed, an explorer.exe process can exist which keeps the ShellExt.dll loaded. In such a case, the safest way to force unloading of ShellExt.dll is to log off. After logging in again, remove ShellExt.dll and reinstall it before viewing the Properties dialog of any file.