Skip to content
WordsOnTech
  • Home
  • MS SQL Server
    • SSRS
    • Always ON
    • Failover Cluster
    • Performance Tuning
    • Replication
  • AWS
  • Azure
  • Scripts
  • About Us
  • Join Us

Error: 17120

TDSSNIClient initialization failed with error 0xd

January 30, 2023 by Ravi Agarwal

Hi All, Recently I faced an issue while trying to update the certificate used for SQL server connection encryption. When I updated the thumbprint value of certificate in following registry key and restarted SQL services I got below error. Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.x\MSSQLServer\SuperSocketNetLib\Certificate Error Message: I checked and verified that SQL server service account … Read more

Share this:

  • Click to share on X (Opens in new window) X
  • Click to share on Facebook (Opens in new window) Facebook
  • Click to share on LinkedIn (Opens in new window) LinkedIn
  • Click to share on WhatsApp (Opens in new window) WhatsApp
  • Click to share on Pinterest (Opens in new window) Pinterest
  • Click to print (Opens in new window) Print
  • Click to share on Reddit (Opens in new window) Reddit
  • Click to share on Telegram (Opens in new window) Telegram
  • Click to share on Pocket (Opens in new window) Pocket
  • Click to share on Tumblr (Opens in new window) Tumblr

Like this:

Like Loading...
Categories Encryption, MS SQL Server Tags Could not start the network library because of an internal error, Error: 17120, Error: 17182, Error: 17826, Initialization failed with an infrastructure error, SQL Server could not spawn FRunCommunicationsManager thread, The data is invalid

Recent Posts

  • Out of memory exception in SQL Server Management Studio (SSMS) while opening ‘restore database’ page March 7, 2024
  • Using Snapshot Replication for Schema Transfer/Refresh Only March 7, 2024
  • Cleanup Log-shipping configuration through TSQL March 7, 2024
  • Configure non-default PostgreSQL instance for automatic start on machine start in RHEL March 4, 2024
  • Código de error: 22903, texto: “Ya hay otra conexión ejecutando ‘sp_replcmds’ para la captura de datos modificados en la base de datos actual.” March 4, 2024

AlwaysOn Amazon Web Services AWS AWS CLI AWS EC2 CDC Cloud costs Commvault cost monitoring cost optimization AWS encrypted backup Encryption Error 912 error 3417 Error 15151 Error 20011 Error 22017 Error 22307 Error 22903 HIGH CPU USAGE High Memory Issue Index optimization Login Failed LogShipping MS SQL Server MS_SSISServerCleanupJob Ola Hallengren Performance Tuning PowerShell Replication Replication Jobs S3 script Security SQL Server SQL Server 2017 SQL server 2019 SQL Server Backup SQL Server hacks SSIS_hotfix_install TDE TLOG Backups TSQL wait statistics Wait types

© 2025 WordsOnTech • Built with GeneratePress
%d
    We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.Ok