← Back to Knowledge Base

KB #240070: Error “The specified file is not encrypted” when starting SQL

⏱️ 1 min read

Type:

Information

Summary:

You secured the instance of SQL specifying “Master must be encrypted” and either master.mdf is not encrypted, or Encryptionizer could not access master.mdf.

Additional Information:

First, use the Encrypt/Decrypt Wizard to verify that master.mdf is actually encrypted. If it is, that means that Encryptionizer cannot access the directory that master.mdf is located in (permissions issue for the startup account).

Start Control Panel, Administrative Tools, Services (or run services.msc). Locate the Service entry for your instance of SQL Server. This is usually MSSQL$instance_name if a named instance, or MSSQLSERVER if the default instance.

Select the Log On tab. If the “this account” button is selected, make sure that the account specified has at least Read access to the SQL Data directory (or whichever directory master.mdf is located in, if different.)

Special Tip for SQL Express

By default, SQL Express uses the NETWORKSERVICE account. We recommend that you change this to the Local System Account or other privileged account.

Was this article helpful?

Related Articles

KB #240124: Using Encryptionizer for SQL on a Cluster

Type: Information Summary: Encryptionizer for SQL is cluster safe, but the installation and configuration are…

KB #240154: Upgrade Operating System on a machine with EKM installed (v2018.1204.32022.1181)

Type: Information Summary: You are upgrading the operating system of a machine in place, and…

KB #240111: Encryptionizer for SQL FIPS 140-2 Release Notes for FIPS 801.1 upgrades

Type: Tip Summary: Below are the enhancements and fixes available in Encryptionizer for SQL FIPS…

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?