KB #240021: “Invalid Driver” or “Can’t load encryption driver” message
Type:
Information
Summary:
This article discusses when and why you may see “invalid driver” or “can’t load encryption driver” message and how to fix it.
Additional Information:
This is typically due to one of the following situations:
Improper Encryptionizer registry entries.
Simply copying Encryptionizer files to a machine is not enough. You must run our Setup program, or build the correct registry keys into your installation script. Refer to inst*.pdf for the appropriate registry entries. Contact us if you need these instructions (available only to owners of distribution or OEM license).
Note: After adding the registry entries, you must reboot the system for them to take effect.
Missing or misplaced driver
The driver file, nlem*.sys or nlem*.drv, is missing or has been placed in the wrong directory. You must run our Setup program, or specify the correct directory in your installation script. Refer to inst*.pdf for more information.
Note: After copying in the driver file, you must reboot the system for it to be loaded.
Incorrect Unlock Code or No unlock Code entered at installation
Encryptionizer for SQL Server production software must be “unlocked” with a registration key in order to load.
Expired evaluation
The evaluation version of Encryptionizer may have expired. If you have purchased Encryptionizer, make sure you are not accidentally using the old evaluation files.
Reboot required
After installing Encryptionizer (through our setup or your install package), you must reboot the system for the driver to be loaded and for the registry entries to take effect.
Note: New registry entries or a new driver (nlem*.sys or nlem*.drv) requires a reboot. However, updating any other files (DLLs, EXEs, etc.) does not require a reboot.
