Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. SQL Server services using domain credentials fail to start

SQL Server services using domain credentials fail to start

View products that this article applies to.

Symptom

After you restart SQL Server, the SQL Server services fail to come online and the startup log contains the following errors: 17182, 17826, or 17120.

Notes

  • This issue only occurs on a SQL Server instance that runs under a domain account.
  • In the log, you see messages that are similar to the following sample entries:
      
    Time stamp spid9s Error: 17182, Severity: 16, State: 1.
Time stamp spid9s TDSSNIClient initialization failed with error 0xffffffff, status code 0x80. Reason: Unable to initialize SSL support.
Time stamp spid9s Error: 17182, Severity: 16, State: 1.
Time stamp spid9s TDSSNIClient initialization failed with error 0xffffffff, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors.
Time stamp spid9s Error: 17826, Severity: 18, State: 3.
Time stamp spid9s 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.
Time stamp spid9s Error: 17120, Severity: 16, State: 1.
Time stamp spid9s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

     

↑ Back to the top

Cause

This issue occurs because the permissions that are usually granted to a SQL Service account are missing. The user rights for the SQL Server startup account that must be present are:

  1. Log on as a service (SeServiceLogonRight).
  2. Replace a process-level token (SeAssignPrimaryTokenPrivilege).
  3. Bypass traverse checking (SeChangeNotifyPrivilege).
  4. Adjust memory quotas for a process.

↑ Back to the top

Resolution

To resolve the issue, grant the missing permissions to the SQL Service domain account. For more information about service permissions, see the Service Permissions section in the article Configure Windows Service Accounts and Permissions.

↑ Back to the top

Keywords: kb, SQL Server services fail to come online, SQL services with domain credentials can’t lunch, “17182”, “17826” or “17120” error messages

↑ Back to the top

Article Info
Article ID : 3006856
Revision : 22
Created on : 2/26/2019
Published on : 2/27/2019
Exists online : False
Views : 319