Search Knowledge Base
KB #240084: SQL will not start. The System cannot find the file specified
SQL Server does not start and the System Event log has an entry from the Service Control Manager: “The system cannot find the file specified.” This can be caused by a few issues. See below for more information.
Failure of SQL to autostart after reboot, or to start after a manual request, can be caused by several factors. This article references issues where the Service Control Manager reports “The system cannot find the file specified”.
- Proxy Profile: When configuring Encryptionizer for the SQL instance, you indicated to store the encryption key profile to an alternate location. However, either the Alternate location is not accessible (permissions, mapping error), or the alternate key profile has been deleted/renamed.
see the following KB article for more information:
KB240040: Cannot start SQL Server when proxy profile is on a remote machine
- The installer is adding the ImagePath for the NLCBTASK Service without surrounding quotes.
KB240091: NLCBTASK Service fails to start with error “The system cannot find the file specified”
SQL Server may not start for other reasons with different error messages. Articles related to SQL not starting are listed below.
240017: Cyclic Redundancy Check Error (CRC) When Starting SQL Server or MSDE
240040: Cannot start SQL Server or encrypted database is inaccessible when profile is on a remote machine
240082: Secured Instance of SQL Server does not AutoStart if McAfee On Access Scanning is enabled
240061: SQL does not start – Error: Another version of the product is already installed.
240070: Error “The specified file is not encrypted” when starting SQL
240077: Error “Another version of this product is already installed” when starting SQL
240091: NLCBTASK Service fails to start with error “The system cannot find the file specified”
Last modified: 1/29/2016