← 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 #240084: SQL will not start. The System cannot find the file specified

Type Information Summary: SQL Server does not start and the System Event log has an…

KB #240103: Log Shipping with Encryptionizer (driver v2010.201.10 and later)

Type: Information Summary: Encryptionizer for SQL FIPS 140-2 Validated supports Log shipping using an AES…

KB #240047: Encrypted values in var char column are randomly decrypting incorrectly

Type: Tip Summary: Values in a varchar column are, seemingly randomly, not decrypting to the…

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?