Additional SQL Server features and topics not covered by specific categories
Error 1067 means the SQL Server service tried to start and then terminated unexpectedly. The generic Services message is not enough; the exact cause must be taken from the SQL Server error log and Windows Event Viewer.
Follow these steps to diagnose and fix it:
- Check the exact startup error
- Open Event Viewer → Windows Logs → Application.
- Filter for Source = MSSQLSERVER (or the name of the SQL instance, e.g.
MSSQL$SQLEXPRESS). - Note the first error that appears at the time you try to start the service. That message (for example, missing file, access denied, invalid startup option, protocol issue, TLS/certificate issue) determines the fix.
- Check common SQL Server startup problems
Use the error text from Event Viewer and compare with these common cases:
- “The dependency service or group failed to start” – follow the guidance in the article referenced under that message in the SQL startup errors table.
- “Error 1069: The service did not start due to a logon failure” – indicates the SQL Server service account credentials are wrong.
- “Error 1067: The process terminated unexpectedly” – often appears when SQL Server cannot access required files (data, logs, error log) or when a path is invalid.
- Verify the SQL Server binary and paths
- If the Windows System log shows Event ID 7000 with text similar to “The system cannot find the file specified” for
MSSQLSERVER, check thatSqlservr.exestill exists in the SQL Server installation folder. - If
Sqlservr.exeis missing or renamed, repair the SQL Server installation using the documented repair procedure.
- If the Windows System log shows Event ID 7000 with text similar to “The system cannot find the file specified” for
- Check for invalid startup options (Error 17112)
- If the error log or Event Viewer shows Event ID 17112 with text like “An invalid startup option was supplied,” open SQL Server Configuration Manager → SQL Server Services → right‑click the instance → Properties → Startup Parameters.
- Ensure only valid parameters are present, each separated correctly, and remove any invalid or malformed entries.
- Check for protocol/TLS/certificate issues (Error 17120 and related)
- If Event Viewer shows Event ID 17120 or messages about background communication tasks or TLS, follow these checks:
- Confirm SQL Server protocols (TCP/IP, Named Pipes) are correctly configured.
- Ensure TLS configuration on the server matches the SQL Server version requirements.
- If a certificate is configured, verify it is valid, correctly bound, and accessible to the SQL Server service account.
- If Event Viewer shows Event ID 17120 or messages about background communication tasks or TLS, follow these checks:
- Check for access denied to SQL folders (Error 5 / Event ID 7000)
- If the error text includes “Access is denied” when starting the SQL Server service, the service account likely lacks permissions on the SQL Server installation or data folders.
- Grant the SQL Server service account appropriate NTFS permissions on the SQL Server installation and data directories, then retry starting the service.
- After fixing the root cause
- Retry starting the SQL Server service from Services or SQL Server Configuration Manager.
- Then rerun the program installer that depends on SQL Server.
If the service still fails with 1067, the next step is to capture and review the exact MSSQLSERVER error message from Event Viewer or the SQL Server error log and then apply the matching article from the SQL Server startup errors list.
References:
- MSSQLSERVER_17120
- SQL Server startup errors on a standalone server
- "Access is denied" error and SQL Server doesn't start
- MSSQLSERVER_17112
- Event ID 7000 and SQL Server doesn't start
- Event ID 17058 and SQL Server doesn't start
- How to resolve error 1067, unable to start SQL server (sqlexpress) service on local computer - Microsoft Q&A
- SQL SERVER (MSSQLSERVER) ERROR 1067 - Microsoft Q&A
- How to fix the SQL server to start - error logs " Master data"? - Microsoft Q&A
- SQL server 2014 for Calypso - Microsoft Q&A
- How do I fix an SQL Server issue - Microsoft Q&A