← 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 #240049: Error 5172 ‘FILE SIZE Property is incorrect’ when attaching a database

Type: Fixed Summary: Under certain conditions you may get the following error when attempting to…

KB #240081: SQL Trace Files are being Encrypted

  Type: Information Summary: If you check the “Encrypt New” check box when Securing an…

KB #240119: Encrypted Databases Not Accessible After Reboot but are Accessible After Manually Restarting SQL Server

Type: Workaround Summary: Encrypted databases may be inaccessible after reboot (listed as Suspect or Recovery…

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?