sqlserver 10013 服务启动失败

sqlserver日志排查：

D:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG

023-02-13 10:57:05.22 spid22s     A self-generated certificate was successfully loaded for encryption.
2023-02-13 10:57:05.22 spid22s     Error: 26023, Severity: 16, State: 1.
2023-02-13 10:57:05.22 spid22s     Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
2023-02-13 10:57:05.22 spid22s     Error: 17182, Severity: 16, State: 1.
2023-02-13 10:57:05.22 spid22s     TDSSNIClient initialization failed with error 0x271d, status code 0xa. Reason: Unable to initialize the TCP/IP listener. An attempt was made to access a socket in a way forbidden by its access permissions. 
2023-02-13 10:57:05.22 spid22s     Error: 17182, Severity: 16, State: 1.
2023-02-13 10:57:05.22 spid22s     TDSSNIClient initialization failed with error 0x271d, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. An attempt was made to access a socket in a way forbidden by its access permissions. 
2023-02-13 10:57:05.22 spid22s     Error: 17826, Severity: 18, State: 3.
2023-02-13 10:57:05.22 spid22s     Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2023-02-13 10:57:05.22 spid22s     Error: 17120, Severity: 16, State: 1.
2023-02-13 10:57:05.22 spid22s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.

Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.

 

解决： 

 

具体操作： 

1、开启防火墙，再重新开启防火墙

2、禁用tcp/ip

 

 

 3、禁用tcp/ip后启动sqlserver 服务

 

 

 4、服务启动完毕

 

 

 5、再开启tcp/ip

 

 

 

 完成.

 

日志查看D:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\Log\ERRORLOG.1

2023-02-13 11:01:09.00 spid22s     A self-generated certificate was successfully loaded for encryption.
2023-02-13 11:01:09.00 spid22s     Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2023-02-13 11:01:09.00 spid22s     Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2023-02-13 11:01:09.01 Server      Server is listening on [ ::1 <ipv6> 18402].
2023-02-13 11:01:09.01 Server      Server is listening on [ 127.0.0.1 <ipv4> 18402].
2023-02-13 11:01:09.01 Server      Dedicated admin connection support was established for listening locally on port 18402.
2023-02-13 11:01:09.01 spid22s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2023-02-13 11:01:09.01 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.
2023-02-13 11:01:09.01 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/DESKTOP-9QG2Q88 ] for the SQL Server service. Windows return code: 0xffffffff, state: 63. 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.