大网数据广告活动
数据库与应用安全

Event ID 33565 and SQL Server doesn't start

· 52CE 我爱测

This article provides resolutions for the problem where SQL Server fails to start and event ID 33565 is logged in the Application event log.

Applies to:   SQL Server

Symptoms

In Microsoft SQL Server Configuration Manager, you provision a server-side certificate and enable the encryption. When you use Service Control Manager to start the SQL Server service, the service doesn't start, and you receive the following error message:

Windows could not start the SQL Server (MSSQLSERVER) 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 -2146885628.

Resolution

  1. Check the Application event log and verify that you see two event entries that resemble the following:

    Log Name:      Application  
    Source:        MSSQLSERVER  
    Date:          <Datetime>  
    Event ID:      26010  
    Task Category: Server  
    Level:         Information  
    Keywords:      Classic  
    User:          N/A  
    Computer:      <Server name>  
    Description:  
    The server could not load the certificate it needs to initiate an SSL connection.
    It returned the following error: 0x8009030d. Check certificates to make sure they are valid.
    
    Log Name:      Application  
    Source:        MSSQLSERVER  
    Date:          <Datetime>  
    Event ID:      33565  
    Task Category: Server  
    Level:         Error  
    Keywords:      Classic  
    User:          N/A  
    Computer:      <Server name>  
    Description:  
    Found the certificate [Cert Hash(sha1) "<Cert Hash number>"] in the local computer store but the SQL Server service account does not have access to it.
    
  2. If you see both Events 26010 and 33565, follow these steps:

    [!NOTE]

    • The two events indicate that the SQL Server service account doesn't have permissions to the certificate that's provisioned in Configuration Manager. You must assign the required permissions to the service account to fix this issue.
    • If you don't see both Event 26010 and 33565, you might be experiencing a different issue that's not addressed in this article.
    1. Select Start > Run, enter mmc, and then open Certificate Snap-in in the MMC console.

    2. On the Console menu, select Add/Remove Snap-in.

    3. Select Add > Certificates, and then select Add again.

      [!NOTE] You're prompted to open the snap-in for the current user, service, or computer account.

    4. Select the computer account.

    5. Select Local computer, and then select Finish.

    6. In the Add Standalone Snap-in dialog box, select Close.

    7. In the Add/Remove Snap-in dialog box, select OK.

      [!NOTE] Your installed certificates are in the Certificates folder in the Personal container.

    8. Right-click the certificate, select All Tasks > Manage Private Keys, and then grant full permissions to the SQL Server service account.

Reference

Enable encrypted connections to the Database Engine

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors (upstream author metadata: aartig13). Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
See source applicability · Source date 05/08/2025
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。