| title | MSSQLSERVER_17826 | |
|---|---|---|
| description | MSSQLSERVER_17826 | |
| author | rwestMSFT | |
| ms.author | randolphwest | |
| ms.reviewer | mathoma | |
| ms.date | 02/02/2023 | |
| ms.service | sql | |
| ms.subservice | supportability | |
| ms.topic | reference | |
| helpviewer_keywords |
|
[!INCLUDE SQL Server]
| Attribute | Value |
|---|---|
| Product Name | [!INCLUDEssNoVersion] |
| Event ID | 17826 |
| Event Source | MSSQLSERVER |
| Component | SQLEngine |
| Symbolic Name | SRV_BAD_SS_EP |
| Message Text | 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. |
When SQL Server starts, one of the steps it takes is to initialize a Tabular Data Stream (TDS) listener and network libraries to accept incoming connections. If this network library initialization fails, error 17826 is raised. Typically this error is raised together with more specific errors. Those specific errors may provide more insight into the failure. Examples of such errors include MSSQLSERVER_17182 and MSSQLSERVER_17120
Review SQL Server error log located in the \Log folder for errors raised together with this error. Take action according to those more specific errors. The following articles describe commonly encountered problems with this error and the actions to take to resolve them:
-
Ensure you configure TLS correctly for SQL Server. For information on updates needed, see TLS 1.2 support for Microsoft SQL Server.