SQL SERVER – Event 17058 – initerrlog: Could not Open Error Log File

If you have ever interacted with me or taken my services, you would notice that I always ask for ERRORLOG in almost all of my contact with my client. Once of my friend contacted me and when I asked for ERRORLOG, he informed that there is no ERRORLOG file and SQL is not getting started.  I suggested him that we should analyze event log for further details, after interestingly, we found the following details in the event 17058 about initerrlog: Could not Open Error Log File.

Log Name: Application
Source: MSSQLSERVER
Event ID: 17058
Task Category: Server
Level: Error
Description:
initerrlog: Could not open error log file ”. Operating system error = 3(The system cannot find the path specified.).

Solarwinds

We finally found that the error occurs due to the insufficient privilege of SQL Server Service Account in the Log directory: E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Log

Here is the fix of the issue.

  1. Start SQL Server Configuration manager.
  2. Click to select ‘SQL Server Services’ from the left menu options.
  3. On the right panel, right click on ‘SQL Server (MSSQLSERVER)’ and click ‘Properties’. You may want to choose correct service.
  4. Click ‘Startup Parameters’ tab.
    SQL SERVER - Event 17058 - initerrlog: Could not Open Error Log File initerrlog-01
  1. Note the location after -e parameter.
  2. Browse the Log location ” E:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER \MSSQL\Log”.
  3. Right click on the folder “Log” and click Properties and then to visit to “Security” tab. Now, check SQL Server service account permission on this folder and give proper access to this folder.
  4. Now, Restart the SQL Server service. If you face the same error again, try to change highly privileged service account like “Local System”.

After giving permission, we were able to start the SQL Service. Have you faced a similar error?

Reference: Pinal Dave (https://blog.sqlauthority.com)

Solarwinds
, , ,
Previous Post
SQL SERVER – DMVs to Detect Performance Problems in SQL Server – Notes from the Field #135
Next Post
SQL SERVER – Error: 14258 – Cannot perform this operation while SQLServerAgent is starting. Try again later

Related Posts

8 Comments. Leave new

Leave a Reply

Menu