When Error 1067 occurs, a message appears on the screen that reads similar to "Could not start the program services on local computer; Error 1067: The process terminated unexpectedly." Unfortunately, the error message does not provide in-depth information about what caused the process to terminate or what options are available to the user to try and correct the problem. Attempting to restart the SQL server and launch the program again may be successful or may result in Error 1067 again.
SQL is a programming language used in the processing of database commands. A special program known as the SQL server executes SQL commands and is a requirement for SQL programs to function properly. If the SQL server stops working or crashes, an error message may appear and declare that "Error 1067" has occurred.
Reasons for Crashing
There are several reasons that the SQL server might terminate unexpectedly. If the program is improperly configured and attempts to use more system memory than is available to it then it may crash. Having improper license information entered may also cause the program to terminate. If system files used by the program or files associated with the SQL server software itself have become corrupted or deleted then the server program may crash when trying to access those files. Corrupted user data or severe disk fragmentation may also cause unexpected program termination.
While the error message associated with Error 1067 does not provide the user with much information, most SQL software keeps a log file that is much more useful in troubleshooting the program. The exact name and location of the log file may vary from one program to another, but many programs save log files as .txt or .ini files in the main installation directory for the program. Opening the log file with a text editor such as Notepad allows you to see exactly what caused the crash so that you can change program settings or make other corrections as needed.
Reinstalling the SQL Server
If the cause of the program crash cannot be fixed by adjusting program settings, reinstallation of the SQL server may be required. This is done by uninstalling and reinstalling the program used to access the SQL server, though you should back up any user data or databases you've created before doing so. Delete any program folders that remain after you've uninstalled the program to prevent installation problems and reinstall the software with a full installation. Launch the program to confirm that it is working correctly and then restore the user data and databases you previously backed up.
- Photo Credit Thinkstock Images/Comstock/Getty Images
How to Stop the C00002a Fatal System Error
The typical error message is "The Windows Logon Process system process terminated unexpectedly with a status of 0xc0000034 (0x00000000 0x0000000)."