When opening a Bridgemate .bws file in Bridgemate Control Software, an error appears containing the message "Error loading in DLL" and error number 48.
When Bridgemate Control Software is executed from the scoring program, or a Bridgemate .bws file is manually opened, the following error appears:
Trying to open the file again by clicking Yes does not help, and the file cannot be opened in Bridgemate Control Software.
This error typically occurs on 64-bit versions of Microsoft Windows. One or more of the Windows system database driver files have been damaged or removed. This may be a result of a anti-virus program, anti-malware or anti-spyware removal program. The exact cause is unknown at this stage.
Fixing the registry
To fix this error, try the following solution first:
- Download the file Error48RegistryFix.zip
- Open the zip file. Inside you will see a .reg file. Run this file by double clicking on it. To run this file, you must be logged into your PC as administrator with full administrator rights.
- After the file has been successfully applied to the Windows registry, you should reboot your PC.
- You should now be able to run the program properly.
If this did not solve the problem, then the most likely reason is that the file was not allowed to run properly. Make sure the file is not blocked by Windows User Account Control or other software. You must have full rights to apply changes to the Windows system files.
If the problem still persists, there is some severe damage to the Windows system files. As last resort, the problem may be resolved by running a Windows Repair action from the Windows installation disc. This will repair all Windows system files and restore the database driver files. If you do no have a Windows installation disc, please consult your computer supplier for how to run the Windows Repair function. (note: the Windows Repair function is not the same as a system recovery which may not resolve this issue).
There is no additional information available for this article.
No further references available for this article.
03-09-2014 - Article published
30-09-2014 - Added the registry fix