Код ошибки 5023 sql server

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:

  1. First, click Start, then in the Microsoft SQL Server program group, point to Configuration Tools.
  2. Then, click on the SQL Server Configuration Manager.
  3. Expand SQL Server Network Configuration, right-click the “protocols for SQL Server” and then click Properties.
  4. 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:

  1. Go into SQL Server configuration manager and select the SQL Server service.
  2. Right-click and select Properties.
  3. 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.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Источник
  • Remove From My Forums

  • Question

  • Hi,

    I searched a lot but did not found any solution. So, now I am here.

    I´m trying to install MS SQL 2014 Failover Cluster on a WindowsServer 2012 R2. In test environment everything went fine, now in the prod environment we are running into a failure.

    The installation is nearly complete up to the point «BringAgentResoucreOnlineAction». It fails with following error message:

    TITLE: Microsoft SQL Server 2014 Setup
    ——————————

    The following error has occurred:

    The cluster resource ‘SQL Server Agent’ could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
    to perform the requested operation.
    .

    Click ‘Retry’ to retry the failed action, or click ‘Cancel’ to cancel this action and continue setup.

    Error Log gives following details:

    (01) 2018-03-09 16:04:07 Slp: —————————————-
    (01) 2018-03-09 16:04:07 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2018-03-09 16:04:07 Slp: Inner exceptions are being indented
    (01) 2018-03-09 16:04:07 Slp:
    (01) 2018-03-09 16:04:07 Slp: Exception type: Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException
    (01) 2018-03-09 16:04:07 Slp:     Message:
    (01) 2018-03-09 16:04:07 Slp:         The cluster resource ‘SQL Server Agent’ could not be brought online.  Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status
    code: 5023. Description: The group or resource is not in the correct state to perform the requested operation.
    (01) 2018-03-09 16:04:07 Slp:         .
    (01) 2018-03-09 16:04:07 Slp:     HResult : 0x86d8003a
    (01) 2018-03-09 16:04:07 Slp:         FacilityCode : 1752 (6d8)
    (01) 2018-03-09 16:04:07 Slp:         ErrorCode : 58 (003a)
    (01) 2018-03-09 16:04:07 Slp:     Data:
    (01) 2018-03-09 16:04:07 Slp:       resourceName = SQL Server Agent
    (01) 2018-03-09 16:04:07 Slp:       errorMessage = There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The group or resource is not in the correct state
    to perform the requested operation.
    .
    (01) 2018-03-09 16:04:07 Slp:       WatsonData = Microsoft.SqlServer.Configuration.Cluster.ResourceOnlineException@58
    (01) 2018-03-09 16:04:07 Slp:       DisableRetry = true
    (01) 2018-03-09 16:04:07 Slp:     Inner exception type: Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException
    (01) 2018-03-09 16:04:07 Slp:         Message:

    (01) 2018-03-09 16:04:07 Slp:                 There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5023. Description: The
    group or resource is not in the correct state to perform the requested operation.
    (01) 2018-03-09 16:04:07 Slp:                 .
    (01) 2018-03-09 16:04:07 Slp:         HResult : 0x86d70002
    (01) 2018-03-09 16:04:07 Slp:                 FacilityCode : 1751 (6d7)
    (01) 2018-03-09 16:04:07 Slp:                 ErrorCode : 2 (0002)
    (01) 2018-03-09 16:04:07 Slp:         Data:

    (01) 2018-03-09 16:04:07 Slp:           ExceptionMessage = Generic failure

    (01) 2018-03-09 16:04:07 Slp:           StatusCode = 5023
    (01) 2018-03-09 16:04:07 Slp:           Description = The group or resource is not in the correct state to perform the requested operation.

    (01) 2018-03-09 16:04:07 Slp:           WatsonData = Microsoft.SqlServer.Configuration.Cluster.ClusterProviderDetailedException@2
    (01) 2018-03-09 16:04:07 Slp:         Stack:

    (01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp:                 at Microsoft.SqlServer.Configuration.Cluster.ClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp:         Inner exception type: System.Management.ManagementException
    (01) 2018-03-09 16:04:07 Slp:             Message:

    (01) 2018-03-09 16:04:07 Slp:                         Generic failure
    (01) 2018-03-09 16:04:07 Slp:             HResult : 0x80131501
    (01) 2018-03-09 16:04:07 Slp:             Data:

    (01) 2018-03-09 16:04:07 Slp:               WmiErrorCode = Failed
    (01) 2018-03-09 16:04:07 Slp:               WatsonData = Failed@5023
    (01) 2018-03-09 16:04:07 Slp:               Description = The group or resource is not in the correct state to perform the requested operation.

    (01) 2018-03-09 16:04:07 Slp:               ErrorType = 1
    (01) 2018-03-09 16:04:07 Slp:               Operation = ExecMethod
    (01) 2018-03-09 16:04:07 Slp:               ParameterInfo = MSCluster_Resource.Name=»SQL Server Agent»
    (01) 2018-03-09 16:04:07 Slp:               ProviderName = WinMgmt
    (01) 2018-03-09 16:04:07 Slp:               StatusCode = 5023
    (01) 2018-03-09 16:04:07 Slp:             Stack:

    (01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
    (01) 2018-03-09 16:04:07 Slp:                         at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject
    inParameters, InvokeMethodOptions options)
    (01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.WMIInterop.Resource.BringOnline(UInt32 TimeOut)
    (01) 2018-03-09 16:04:07 Slp:                         at Microsoft.SqlServer.Configuration.Cluster.WmiClusterResource.Online(Int32 timeout)
    (01) 2018-03-09 16:04:07 Slp: —————————————-

    SQL Server is up and running, the SQL Server Agent cannot be started due to the above mentioned error.

    We already tried to re-create DNS entry, re-create AD object, compared the permissions between prod and test system. But we don´t see any differences.

    So, now I am hoping anyone of you have an idea.

    Regards,
    Helen

    PS: I can test again on Monday CET.

Answers

  • Finally we found the problem.

    The service owner had no local admin rights on the server… giving the user the correct rights, everything worked fine.

    I had hoped, that the error message would inidcate that kind of error, something with missing rights.

    The Windows Event Log was a good hint, because there was a message, that a specfic file could not be read due to missing access rights.

    Best regards,

    Helen

    • Marked as answer by

      Monday, March 12, 2018 12:42 PM

Источник
  • Remove From My Forums

  • Общие обсуждения

  • Добрый день, помогите с проблемой!!!!

    До этого момента нормально существовала SQL Server 2000 Desktop Engine — без каких либо проблем.

    Теперь потребовался SQL Server 2005 Express. MSDE был успешно удален.

    Но при установке SQL Server 2005 Express (SP3) — возникла ошибка: «Запуск службы SQL Server не удался. Дополнительные сведения см. в электронной документации по SQL Server, разделы «Как: посмотреть файлы журнала установки SQL Server 2005» и «Запуск SQL Server вручную».
    Ошибка 5023 Группа или ресурс не находятся в нужном состоянии для выполнения требуемой операции.»

    Поиск решения не увенчался успехом. В том числе http://social.technet.microsoft.com/Forums/it-IT/sqlru/thread/8e84701c-4913-4bd7-8a36-a902f2e560de

    В логах сама ошибка:

    Setting status of unmanaged components and removing unmanaged resources
    Do_sqlScript
    SqlScriptHlpr
    Start service MSSQL$SQLEXPRESS

    Error Code: 5023
    MSI (s) (78:BC) [16:02:02:740]: Running as a service.
    Ошибка 29503. Запуск службы SQL Server не удался. Дополнительные сведения см. в электронной документации по SQL Server, разделы «Как: посмотреть файлы журнала установки SQL Server 2005» и «Запуск SQL Server вручную».
    Ошибка 5023 Группа или ресурс не находятся в нужном состоянии для выполнения требуемой операции.

    <Func Name=’GetCAContext’>
    <EndFunc Name=’GetCAContext’ Return=’T’ GetLastError=’203′>
    Doing Action: Do_sqlScript
    PerfTime Start: Do_sqlScript : Fri Oct 02 16:03:28 2009
    Service MSSQL$SQLEXPRESS with parameters ‘-m SqlSetup -Q -qCyrillic_General_CI_AS -T4022 -T3659 -T3610 -T4010’ is being started at Fri Oct 02 16:03:28 2009
    Service failed unexpectedly (5023)
    Error Code: 0x8007139f (5023)
    Windows Error Text: Группа или ресурс не находятся в нужном состоянии для выполнения требуемой операции.
    Source File Name: sqlsetuplibservice.cpp
    Compiler Timestamp: Sat Oct 25 08:47:19 2008
    Function Name: sqls::Service::Start
    Source Line Number: 301

    • Изменен тип

      25 февраля 2011 г. 13:47
      Отсутствие активности пользователя

Источник

I am going to assume you are looking for the definition and the root cause of these events.

From How It Works: SQL Server 2005 SP2 Security Ring Buffer – RING_BUFFER_SECURITY_ERROR (archive):

SQL Server 2005 SP2 added new ring buffer entries (sys.dm_os_ring_buffers) for various security errors. The reason the ring buffer entries were added was to provide the DBA with more details as to why a client is receiving a failed login or other such error.

You state that you have no failed login entries in the event log nor in the error log. Instead you can query this ring buffer directly:

SELECT CONVERT (varchar(30), GETDATE(), 121) as runtime,
dateadd (ms, (a.[Record Time] - sys.ms_ticks), GETDATE()) as [Notification_Time],
a.* , sys.ms_ticks AS [Current Time]
FROM
(SELECT
x.value('(//Record/Error/ErrorCode)[1]', 'varchar(30)') AS [ErrorCode],
x.value('(//Record/Error/CallingAPIName)[1]', 'varchar(255)') AS [CallingAPIName],
x.value('(//Record/Error/APIName)[1]', 'varchar(255)') AS [APIName],
x.value('(//Record/Error/SPID)[1]', 'int') AS [SPID],
x.value('(//Record/@id)[1]', 'bigint') AS [Record Id],
x.value('(//Record/@type)[1]', 'varchar(30)') AS [Type],
x.value('(//Record/@time)[1]', 'bigint') AS [Record Time]
FROM (SELECT CAST (record as xml) FROM sys.dm_os_ring_buffers
WHERE ring_buffer_type = 'RING_BUFFER_SECURITY_ERROR') AS R(x)) a
CROSS JOIN sys.dm_os_sys_info sys
ORDER BY a.[Record Time] ASC

The notification time might shed some light on the root cause.

I think you will find that the date/time of the entries will line up with login failure entries in the errorlog similar to:

«Login failed for user ‘domainuser’. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: ] Error: 18456 Severity: 14 State: 11.»

From Troubleshooting specific Login Failed error messages (archive) :

State 11 corresponds to “Valid login but server access failure” which indicates that the login is valid but is missing certain security privileges which would grant it access to the instance.

  1. Check if that login is directly mapped to one of the SQL Server logins by looking in the output of sys.server_principals.
  2. If the login is directly mapped to one of the available logins in the SQL instance, then check if the SID of the login matches the SID of the Windows Login.

If someone dropped the login at the Windows/AD level, and added it back, it will get a new SID which won’t match the SID SQL has stored in its system catalog and it will fail.

Источник

Hello, our windows server had automatic updates set on. The last update did something and on a couple machines SQL Server will not start. When trying to start the service we receive the error:

Windows could not start SQL Server (ourSQL) 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 event:

The SQL Server (ourSQL) service terminated with service-specific error 5023 (0x139F).

I have tried starting the service from service manager, SQL configuration tool, and command line.

Any suggestions?

Thank you.

[edit]SQL server 2008 standard, Windows 2008 standard

We have narrowed it down to Windows 2008 standard boxes. The Windows 2008R2 boxes are okay[/edit]

DennisPost

SSCrazy

Points: 2691

Perhaps this MS Connect issue will help.

Turn off automatic updates 😛

djj

SSCoach

Points: 18831

First thing the systems guy did.

mr_belpitt

SSC Enthusiast

Points: 121

Are you running the service with a useraccount, and if so, is it locked out?

djj

SSCoach

Points: 18831

We used user (with sys admin rights), the network sys admin and the system sys admin accounts. None worked.

Restored without updates finally worked. Bad thing is it was the computer controlling backups.:-)

Источник

Возможно, вам также будет интересно:

  • Код ошибки 502 окко как исправить
  • Код ошибки 50 пфр сзв стаж
  • Код ошибки 502 на мегафоне что это значит
  • Код ошибки 50 отчет сзв стаж
  • Код ошибки 502 мегафон что это значит

    • Понравилась статья? Поделить с друзьями:
    0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии