This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(144, 40%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
Core component of SQL Server for storing, processing, and securing data
Did you also try to start SQL Server from the SQL Server Configuration Manager? That's the normal place to start SQL Server services.
If that also fails, the next step is to check out the SQL Server errorlog, which would be in C:\Program Files\Microsoft SQL Server\MSSQLnn.SQLEXPRESS\MSSQL\LOG\ERRRORLOG, assuming a default installation. (nn is a number that depends on the version of SQL Server.)
Pay attention to the date of the file - does it agree with your most recent attempt to start SQL Server? If it does not, the error occurs before SQL Server starts writing to the errorlog. If the date does agree, the errorlog should give further information. Feel free to attach it here. You will have to rename it to ERRORLOG.txt to be able to upload it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 79%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDY%3C/text%3E%3C/svg%3E)
Hi @Jeremy Sandlin ,
Thank you for reaching out to the Microsoft SQL Q & A Forum.
Please refer below Q & A forum threads.
https://learn.microsoft.com/en-us/answers/questions/1503206/sql-server-wont-start-service-error-1067
I hope this information helps. Please do let us know if you have any further queries.
Regards,
Dinesh
Hi @Jeremy Sandlin ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. And, if you have any further query do let us know.
Regards,
Dinesh
Hi Jeremy,
I suggest you to change service account with a more privileged account. For example "local system" or any other account that you create.
No, don't to this. It may resolve the issue, but in such case it is not the correct resolution. SQL Server should not run under a privileged service account, least of all LocalSystem.