“ 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. #SQL STUDIO TAKE OFFLINE WINDOWS#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 Corrupt or missing model database filesīefore diving into the various possible causes, we’ll start with some basic troubleshooting steps that will help identify the cause.Corrupt or missing master database files. #SQL STUDIO TAKE OFFLINE PASSWORD#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |