This error usually indicates a bad BDE install or a corrupt BDE. Also a possibility that not all of the language drivers are installed.

1. Open the Registry.
   • Click Start.
   • Click Run.
   • Type in Regedit and hit Enter.
2. Navigate to HKLM>Software>Borland.
   • Note: if 64bit processor, Navigate to HKLM>Software>WOW64Node>Borland
3. Check the path of the DLLPath and Configfile01.

1. Test to see if this resolves the issue.

1. Navigate to the BDE folder on the server(usually C:\Program Files\Cyrious\Common\BDE).
2. Double click on the BDE Administrator.
3. Check the properties of the BDE Administrator by navigating to the “Configuration” folder, then expand “Drivers”, “Navigation”, “Paradox”.
4. Click the drop-down next to the “LangDriver” option to the right.
   • If only one language driver is available, this reflects a bad install.
   • The BDE should be reinstalled under these circumstances and the properties should be checked for validity with regard to the language drivers.

1. See if Sharing tab is available on the Cyrious folder
2. If not go to the Services in the Control Panel
3. Turn on the Server services
4. Confirm the Sharing tab appears
5. If not, open the registry
6. Navigate to

HKEY_CLASSES_ROOT\CLSID\{f81e9010-6ea4-11ce-a7ff-00aa003ca9f6}\InProcServer32\

1. Set (Default) = ntshrui.dll
2. If already set to that, set (Default) = Null
3. Hit refresh
4. Set (Default) = ntshrui.dll
5. Refresh
6. Turn on the Server services
7. Reshare Cyrious properly (see sms1_-_setting_permissions_on_cyrious_folder)
8. Test the SSLIP Database Administration Group connections
9. If all work but the SMS Group, see Procedure/Walk-Through 1 above

One common manifestation of the problem is when someone tries to open the BDE Admin. while another copy of Cyrious is active on the network. An “unable to initialize Borland Database Engine” error produces on the screen. Conversely, if someone tries to open a copy of Cyrious on the network while the BDEAdmin is running, then an “Invalid Operation” error will produce.

1. Try installing Cyrious on the problematic machine so new registry entries will be created in case there is possible corruption on the bad machine.
2. Or see borland_registry_installation for manual installation of the regeistry entries

1. If you are getting the error on all computers - dbrebuild