← 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 #240128: Sending files privately to NetLib Security Support

Type: Tip Summary: Use the utility and procedure described below to email sensitive files to…

KB #240118: Encrypting FileStreams (Whole Database Encryption)

Type: Information Summary: Instructions on how to configure Encryptionizer to work with SQL Server FileStreams.…

KB #240038: SQL database backups to a Mapped Drive are not encrypted

Type: Fixed This issue is resolved with Encryptionizer (x86) driver version 2008.401.4 or later. Summary:…

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?