Shulou(Shulou.com)05/31 Report--

This article mainly introduces the sqlserver can not start to report 26024 error how to do, has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

2018-01-03 10 4715 32.93 Server Microsoft SQL Server 2012-11.0.5058.0 (X64)

May 14 2014 18:34:29

Copyright (c) Microsoft Corporation

Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 (Build 7601: Service Pack 1) (Hypervisor)

2018-01-03 10 Server 47 Server (c) Microsoft Corporation.

2018-01-03 10 Server All rights reserved.

2018-01-03 10 Server Server process ID is 47. 32. 93.

2018-01-03 10 Server System Manufacturer: 'VMware, Inc.', System Model:' VMware Virtual Platform'.

2018-01-03 10 Server Authentication mode is MIXED.

2018-01-03 10 Server Logging SQL Server messages in file'C:\ Program Files\ Microsoft SQL Server\ MSSQL11.MSSQLSERVER\ MSSQL\ Log\ ERRORLOG'.

2018-01-03 10 Administrator'. 47 Server The service account is' H3TEST-SER\ Administrator'. This is an informational message; no user action is required.

2018-01-03 10 4715 32.93 Server Registry startup parameters:

-d C:\ Program Files\ Microsoft SQL Server\ MSSQL11.MSSQLSERVER\ MSSQL\ DATA\ master.mdf

-E C:\ Program Files\ Microsoft SQL Server\ MSSQL11.MSSQLSERVER\ MSSQL\ Log\ ERRORLOG

-l C:\ Program Files\ Microsoft SQL Server\ MSSQL11.MSSQLSERVER\ MSSQL\ DATA\ mastlog.ldf

2018-01-03 10 4715 32.93 Server Command Line Startup Parameters:

-s "MSSQLSERVER"

2018-01-03 10 cores per socket and 47 cores per socket and 33.13 Server SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

2018-01-03 10 Server SQL Server is starting at normal priority base 47 33.13 (= 7). This is an informational message only. No user action is required.

2018-01-03 10 Server Detected 47. 33. 13 MB of RAM. This is an informational message; no user action is required.

2018-01-03 10 Server Using conventional memory in the memory manager.

2018-01-03 10 Server This instance of SQL Server last reported using a process ID of 4733.22 Server This instance of SQL Server last reported using a process ID of 4316 at 2018-1-3 10:42:34 (local) 2018-1-3 2:42:34 (UTC). This is an informational message only; no user action is required.

2018-01-03 10 Server Node configuration: node 0: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2018-01-03 10 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2018-01-03 10 Server Software Usage Metrics is disabled.

2018-01-03 10 4715 33.24 spid5s Starting up database 'master'.

2018-01-03 10 spid5s 4733.26 spid5s 20 transactions rolled forward in database 'master' (1:0) This is an informational message only. No user action is required.

2018-01-03 10 master' 47 spid5s 33.27 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.

2018-01-03 10 Server CLR version 4715 33.33 loaded v4.0.30319.

2018-01-03 10 functionality initialized using CLR version 4733.37 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\ Windows\ Microsoft.NET\ Framework64\ v4.0.30319.

2018-01-03 10 spid5s Resource governor reconfiguration succeeded 4733.42.

2018-01-03 10 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.

2018-01-03 10 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.

2018-01-03 10 sa 47 spid5s SQL Trace ID 33.44 1 was started by login.

2018-01-03 10 spid5s Server name is' H3TESTMUR server. This is an informational message only. No user action is required.

2018-01-03 10 spid13s 47. 33. 63 A self-generated certificate was successfully loaded for encryption.

2018-01-03 10 SQLLocal 47 SQLLocal 33.63 spid13s Server local connection provider is ready to accept connection on [\.\ pipe\ SQLLocal\ MSSQLSERVER].

2018-01-03 10 sql 47 sql 33.63 spid13s Server local connection provider is ready to accept connection on [\.\ pipe\ sql\ query].

2018-01-03 10 Server: error: 26024, severity: 16, status: 1.

2018-01-03 10 4715 33.63 Server Server failed to listen on 'any' 1434. Error: 0x277a. To proceed, notify your system administrator.

2018-01-03 10 Server Dedicated admin connection support was not started because of error 0x277a, status code: 0x1. This error typically indicates a socket-based error, such as a port already in use.

2018-01-03 10 spid13s SQL Server is now ready for client connections. This is an informational message; no user action is required.

2018-01-03 10 for the SQL Server service 47 for the SQL Server service 33.64 Server SQL Server is attempting to register a Service Principal Name (SPN). Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.

2018-01-03 10 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [MSSQLSvc/h4test-ser] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.

2018-01-03 10 spid14s A new instance of the full-text filter daemon host process has been successfully started 4733.77.

Viewing the application from the Syslog reports an error as follows:

The server cannot listen on 'any' 1433. Error: 0x277a. To continue, notify your system administrator.

TDSSNIClient initialization failed with error 0x277a, status code 0xa. Reason: Unable to initialize the TCP/IP listener. The requested service provider could not be loaded or initialized.

Finally, through the normal server comparison, it is found that the configuration is different in this place, the normal server is no here, and here is "yes". Since all monitoring is enabled, it is also one of them, so the question here is changed to "No".

Thank you for reading this article carefully. I hope the article "what to do if sqlserver cannot start to report 26024 errors" shared by the editor will be helpful to everyone. At the same time, I also hope that you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.