Managing database servers for Web hosts, VPS hosts, etc, and resolving the issues related to it are a major chunk of the Server Management Services that we offer at Bobcares. We receive a number of SQL-related support requests as a part of it. To fix SQL error 5023 is one among them.
This error in general triggers while starting the SQL server. At times users wonder what triggered it.
Today, let’s discuss the top reasons behind this SQL error and it fixes.
What causes the SQL error 5023?
As we discussed earlier the error 5023 triggers normally during a restart operation on Microsoft SQL Server or SQL Server Agent. At times due to incompatibility of the TLS version or the permission issue of the user account, the service may fail to start with the following error message:
Windows could not start SQL Server on Local Computer. For more information, review the System Event Log.
If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5023.
The major reasons for this error include:
- Incompatibility issue of TLS version with SQL server. For example, TLS 1.2 is not supported by SQL server 2014.
- Permission issue of the user account
- SSL 3.0 and/or TLS 1.0 have been disabled.
Let us now look at the different fixes for this error message:
How to fix the SQL error 5023?
As this error is commonly triggered due to the incompatibility of TLS versions, trying to start that SQL server after disabling the encryption may help to start the SQL service. Steps for it include:
- First, click Start, then in the Microsoft SQL Server program group, point to Configuration Tools.
- Then, click on the SQL Server Configuration Manager.
- Expand SQL Server Network Configuration, right-click the “protocols for SQL Server” and then click Properties.
- Finally, on the Flags as well as Certificate tab, disable any encryption applicable.
We can then try starting the SQL server again. Since the incompatible TLS versions are disabled, the SQL server will be started now.
Another possible reason for this error message is the permission issue of the user account. To confirm this, we can try to change the account to a Local System built-in one. The steps to perform it include:
- Go into SQL Server configuration manager and select the SQL Server service.
- Right-click and select Properties.
- Set the account to the Local System built-in account.
Once the account is switched, we can try to start the SQL Server. If it works fine, then it is indeed a user account permission problem. Thus we will need to correct the permission of the user account to fix the issue.
[ Need help resolving email errors in your sites? Get assistance from our server experts at affordable rates. ]
Conclusion
In short, the SQL error 5023 triggers while starting the SQL server. It happens due to the incompatibility of the TLS version, the permission issue of the user account etc. Today, we discussed how our Support Engineers fix this error.
Hi,
While trying to change the account to a Local System built-in one, i’m getting a error pop-up saying “The Group or Resource Is Not In The Correct State To Perform The Requested Operation”
What does this mean?
Damaged and corrupted system files on the OS can results in the group or resource is not in the correct state to perform the requested operation error.
If you are still facing such issues, we are be happy to talk to you on chat.
I am still facing the group resource error . help plz?
Hi,
Please contact our support team through live chat (click on the icon at right-bottom).
Still we are facing the same error
Hello,
Our experts can help you with the issue.we will be happy to talk to you through our live chat(click on the icon at right-bottom).
We have encountered this often when upgrading a Windows 7 system with SQL 2008 to Windows 10.
The proper solution, of course, would be to upgrade the version of SQL Server. This isn’t always possible, so here’s registry settings that will get older SQL to start while ensuring .Net and such use PCI Compliant ciphers
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings” /v SecureProtocols /t REG_DWORD /d 0x00000AA8 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings” /v SecureProtocols /t REG_DWORD /d 0x00000AA8 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp” /v DefaultSecureProtocols /t REG_DWORD /d 0x00000A00 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp” /v DefaultSecureProtocols /t REG_DWORD /d 0x00000A00 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server” /v DisabledByDefault /t REG_DWORD /d 0x00000000 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server” /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 128/128” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 40/128” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\RC4 56/128” /v Enabled /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727” /v SystemDefaultTlsVersions /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727” /v SystemDefaultTlsVersions /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727” /v SchUseStrongCrypto /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v2.0.50727” /v SchUseStrongCrypto /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” /v SystemDefaultTlsVersions /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319” /v SystemDefaultTlsVersions /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319” /v SchUseStrongCrypto /t REG_DWORD /d 0x00000001 /f
reg add “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319” /v SchUseStrongCrypto /t REG_DWORD /d 0x00000001 /f
Hello,
Please contact our support team via live chat(click on the icon at right-bottom).