How to Fix SQL Server Error 1067?
Error 1067 is a common error you may encounter in SQL Server databases. This error may appear with different messages, such as:
- Could not start the program services on local computer
- The SQL Server (MSSQLSERVER) service terminated with service-specific error (1067).
- The SQL Server (MSSQLSERVER) service terminated with the following service-specific error: The process terminated unexpectedly.
Such an error message means that the SQL Server service failed to start.
Let’s discuss the causes that may lead to this error and the different ways to fix the issue.
Causes of the Error 1067
The following causes can produce the error 1067 in SQL Server:
- Incorrect configuration
- System files are damaged and corrupted
- Insufficient system resources
What to do if you see this error?
Here are some solutions you can follow to troubleshoot and fix the error.
Check the Event Viewer
You can start with checking the Event Viewer. The Event Viewer shows common errors in the system and applications, including SQL Server. You can check for critical errors and verify if some of them are responsible for the error.
Right-click on Applications and select Filter Current Log to filter the errors.
Try to filter critical error messages and look for MSSQLServer errors.
You can also check other errors.
Check the Error Log
SQL Server also includes an Error Log. To open it, in SSMS, go to Object Explorer.
In Object Explorer, go to the Management folder and SQL Server Logs.
You can see the log files there.
You can double-click the current log to read all the log messages. You may find the causes of the error there.
Use the SQL Server Configuration Manager
Verify that the SQL Server service is configured to start automatically.
- In the SQL Server Configuration Manager, go to SQL Server Services and verify if the Start Mode is Automatic.
- Verify that the account has the necessary permissions to start the service.
- If you suspect that the problem is with the account, try to restart the service with a different account. To do so, double-click the service name and go to the Log On tab. Browse and select any other account to check if the service works with a different account.
Repair Corrupted Files
Sometimes, the files in the installation directory get corrupted. In such a case, go to the SQL Server installation wizard and try to fix the problem using the setup.
Open the setup.exe and go to the Maintenance tab. Press the Repair option and follow the wizard to repair the files.
Check for Memory Problems
Sometimes, the error occurs due to lack of memory. You can use the Task Manager or the Performance Monitor to verify the memory available in the server.
If a lot of memory is used by other programs, close the ones that are not being used. Make sure that the memory usage is below 90%. If you do not have applications and processes opened, then you may need to increase the RAM used by the server or the virtual machine.
Check Disk Space
Sometimes, the problem is just the disk space. You can use Windows Explorer to check the space in your disk.
If the space is not enough, you may need to remove some programs to increase the space or move the data files to a different disk. In some cases, you may need to add more disks to your machine and migrate some data from the disk to another one.
The attach database statement can be used in this situation. You may need to detach your database first and then attach it to a new location to freeze some disk space.
- To detach a database, right-click on it and go to Properties > Files and check the path.
- Once you know the path of the data file and log file, right-click the database and select Tasks > Detach.
You can use the Windows Explorer to copy and paste the data files and log files to the new disk.
- To attach the (detached) database, right-click the database node and select Attach.
- Press the Add button and look for your data and log files. Finally, press the OK button. You will have your database at the new location.
What if the SQL Server database is corrupt?
If your SQL database is corrupt, a third-party SQL database repair software, such as Stellar Repair for MS SQL can help you to fix your database in a quick and simple way. It is a simple and intuitive software that can be used to repair corrupt or damaged .mdf files in SQL Server.
The software can recover any objects, such as tables, views, stored procedures, synonyms, etc. It also supports the recovery of large databases. This software is compatible with MS SQL Server 2019, 2017, and lower versions.
In this article, we discussed different ways to troubleshoot and fix the SQL Server error 1067. You can check the Event Viewer or the Error log, check the service and permissions using the SQL Server Configuration Manager, or use the Task Manager to check the memory. In case the database is corrupt, you can use Stellar Repair for MS SQL to repair the database.