← Back to Knowledge Base

KB #240092: SQL Server does not start when adding APIs during upgrade

⏱️ 1 min read
 

Type:

Information
Summary:
If you are upgrading to a new version of Encryptionizer you may not be able to install APIs during the upgrade process if you have an encrypted Master database.

 

Additional Information:
When installing APIs, the Setup needs to start the SQL instance. If you have an encrypted Master database, the Setup may not be able to start SQL. This is because while the new drivers on now on disk, the old drivers are still in memory. If you cannot install APIs during the upgrade process, complete the Setup (bypassing installing APIs). Then reboot the machine and then install the APIs.

You can run the API installer by selecting frm the Main Menu program:
Install APIs

Alternatively, navigate to the Encryptionizer install directory and run the utility: xpadmin.exe

The Encryptionizer install directory is usually:
  C:Program FilesNetLibSecSQL
or
  C:Program Files (x86)NetLibSecSQL

Was this article helpful?

Related Articles

KB #240104: Event IDs and Error Codes

Type: Information Summary: Below are listed some of the Events that Encryptionizer writes to the…

KB #240139: Third Party Backup Software

Type: Information Summary: You are using third-party backup software to backup your databases, and want…

KB #240058: Event ID for the system log entries for nlemsql are “not found”

Type: Known Issues Summary: You have secured your SQL instance with Encryptionizer and have selected…

Still need help?

Our support team is here to assist you.

NetLib Security
AI Assistant · Online
Hi! I'm the NetLib Security assistant. I can answer questions about our encryption solutions, HIPAA compliance, Encryptionizer, and more. How can I help you today?