SQL error 17058 occurs due to various reasons that include insufficient privileges, corrupted log files, an issue with network policies, and permission issues.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and see how to fix it.

Different causes and fixes for the SQL error 17058

Let us take a look at the different reasons for this error to occur. Also, we shall see its respective fixes.

1. Cause: Insufficient privilege of SQL Server Service Account in the Log directory

Solution:

• First, start the SQL Server Configuration Manager.
• From the left menu options, click to select ‘SQL Server Services’.
• Then from the right panel, right-click on ‘SQL Server (MSSQLSERVER)’ and click ‘Properties’. Here, choose the correct service.
• Click on the ‘Startup Parameters’ tab and note the location after -e parameter.
• Browse for the Log location.
• Now right-click on the “Log” folder and click Properties and then access the “Security” tab.
• Now, verify the SQL Server service account permission of this folder and give proper access to this folder.
• Finally, restart the SQL Server service.
• In case, if you face the same error again, then try to change highly privileged service account like “Local System”.

2. Cause: Corrupted log file

Solution:

In order to fix the corrupted log file, rename the existing log file. Renaming will generate a new log file.

3. Cause: Issue with network policies which restrict access to the server

Solution:

Add a correct network policy. Here are the steps for doing the same:

First, open the NPS console, and double-click on Policies.

Right-click Network Policies, and click New in the console tree. Now a new Network Policy wizard opens.

You can now use the New Network Policy wizard to create a policy.

4. Cause: Permission problem for the logon account

Solution:

In order to fix this error, we need to fix the permission issue. Here are the steps to change the permissions.

Access Admin Tools >> Services

Now click on each SQL Service and change the Log On as credentials. change them to Local System Account and Allow service to interact with Desktop.

[Need any assistance in fixing SQL errors? – We’ll help you]

Conclusion

In short, this error occurs due to various reasons that include insufficient privileges, corrupted log files, the issue with network policies, and permission issues. Today, we saw the different causes and their fixes to this error.