I’ve seen this happen when the administrator has configured the SQL Server service account to require regular password changes, and also in cases where DBAs or developers know the SQL Server service account password and sometimes use it, often to avoid “inconvenient” security policies such as those forbidding developers from having sysadmin access to the production servers. Incorrect password or service account locked or disabled The first, basic troubleshooting step complete, it’s now time to delve into the various possible causes for the failure of the SQL Server to start, and recommended solutions. This approach eliminates any flailing around, in panic, trying out random solutions without any idea of the root cause of the problem, which is a ‘methodology’ that wastes time and might do more damage in the process. I can see from the message that I have a problem with the master database and I can direct my troubleshooting efforts there. Verify your startup options, and correct or remove them if necessary. An invalid startup option might have caused the error. Reason : 15100 ) occurred while opening file 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\master.mdf' to obtain configuration information at startup. However, in this case, the error log is present and the very last message in the log reads as follows:Ģ012 - 05 - 24 18 : 43 : 36.56 Server Error 2 ( failed to retrieve text for this error.
#Mamp sql server not starting windows#
If we find nothing in the SQL error log, we need to examine the Windows Event log to find out why, and we’ll return to this eventuality in the later sections. In the second case, it has nowhere to write the log entries. In the first case, SQL Server won’t even begin the startup routine and hence won’t log anything. Either the defined location for the error log files is not there, or the SQL account does not have permission on it.The service encountered a login failure (service account password invalid or account locked or disabled).Two cases where there won’t be a relevant error log entry are if: If SQL Server at least started its startup routine before it failed, then it will have logged whatever error it encountered that prevented the service from starting completely. To find the cause of the startup failure, navigate to that folder and, in Notepad, open the latest error log file (called ERRORLOG) and scroll right to the bottom.
This is the default location for the error log for the default instance of SQL Server 2008. “ C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\”
The -e parameter is the one we need and, in my case, I can see that my error log should be in the folder: If you’re unsure of its location, check the startup parameters of the SQL Server service in SQL Server Configuration Manager, as shown in Figure 3. The SQL error log is just a text file on disk. The Windows Application Event Log will do as well, but I prefer the SQL error log, as I can see all the messages at once, and not have to click on them one by one. The first place you should start looking for the cause is the SQL Server error log. It just gives the same “Service specific error occurred” message. Oh, and just in case the message in Figure 2 raised your hopes, more help is not available by running NET HELPMSG 3547. Neither of these messages helps identify a cause for the startup failure. The first and most obvious symptom will be that the SQL Server service is not running and an error greets your attempts to restart it.Īlternatively, if you tried to start the service from the command prompt… Common Symptoms and Initial Troubleshooting
0 kommentar(er)
