Type:
Fixed
Affected Operating Systems:
Windows Server 2016 and later, Windows 10 and later.
Summary:
After a system reboot, the “NetLib Encryptionizer Key Manager” Service (KMS) randomly gets stuck in Start Pending status making encrypted databases appear as Suspect or in Recovery Pending.
Additional Information:
After reboot the NetLib Encryptionizer Key Manager Service (KMS) randomly gets stuck in “Start Pending” status. The KMS is responsible for delivering encryption key(s) at runtime to the Secured instance of SQL Server. Since the encryption key(s) are not delivered to the Secured instance of SQL Server, that means that SQL cannot access the encrypted database files so they will appear in Recovery Pending or Suspect.
Confirm that this is the source of the problem: Open a Command Window as Administrator and run the following command:
SC QUERY NLCBTASK
The status will show as one of the following:
- RUNNING
- STOPPED
- START_PENDING
If that status is not START_PENDING then this is not the cause of the problem. Research other KB articles or contact NetLib Support.
Fix
This issue has been fixed in the 2018.1102 version and later of Encryptionizer. Customers current on Maintenance and Support may contact NetLib Support for the latest version.
Related Topics:
240102: Cannot start SQL Server or encrypted database is inaccessible when profile is on a remote machine