sqlserver无法启动报26024错误怎么办-创新互联

这篇文章主要介绍了sqlserver无法启动报26024错误怎么办，具有一定借鉴价值，感兴趣的朋友可以参考下，希望大家阅读完这篇文章之后大有收获，下面让小编带着大家一起了解一下。

2018-01-03 10:47: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:47:32.93 Server      (c) Microsoft Corporation.

2018-01-03 10:47:32.93 Server      All rights reserved.

2018-01-03 10:47:32.93 Server      Server process ID is 1980.

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

2018-01-03 10:47:32.93 Server      Authentication mode is MIXED.

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

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

2018-01-03 10:47: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:47:32.93 Server      Command Line Startup Parameters:

          -s "MSSQLSERVER"

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

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

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

2018-01-03 10:47:33.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:47:33.22 Server      Node configuration: node 0: CPU mask: 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:47:33.23 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:47:33.23 Server      Software Usage Metrics is disabled.

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

2018-01-03 10:47:33.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:47:33.27 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.

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

2018-01-03 10:47:33.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:47:33.42 spid5s      Resource governor reconfiguration succeeded.

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

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

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

2018-01-03 10:47:33.44 spid5s      Server name is 'H3TEST-SER'. This is an informational message only. No user action is required.

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

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

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

2018-01-03 10:47:33.63 Server      错误: 26024，严重性: 16，状态: 1。

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

2018-01-03 10:47:33.63 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:47:33.64 spid13s     SQL Server is now ready for client connections. This is an informational message; no user action is required.

2018-01-03 10:47:33.64 Server      SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. 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:47:33.64 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:47:33.77 spid14s     A new instance of the full-text filter daemon host process has been successfully started.

从系统日志查看应用程序报错如下：

服务器无法在 'any' 1433 上侦听。错误: 0x277a。若要继续，请通知您的系统管理员。

TDSSNIClient 初始化失败，出现错误 0x277a，状态代码 0xa。原因: Unable to initialize the TCP/IP listener. The requested service provider could not be loaded or initialized.

最后通过正常的服务器对比发现，在这个地方，配置不同，正常服务器此处为否，而这里是“是”。由于启动了全部监听，那么也是其中，所以问题在这里将此处改为“否”

感谢你能够认真阅读完这篇文章，希望小编分享的“sqlserver无法启动报26024错误怎么办”这篇文章对大家有帮助，同时也希望大家多多支持创新互联，关注创新互联-成都网站建设公司行业资讯频道，更多相关知识等着你来学习!