MSSQLSERVER Service Failed To Start, TDSSNIClient initialization failed with error 0x34, SQL Server could not spawn FRunCM thread
Problem
The MSSQLSERVER service failed to start when you update Microsoft SQL Server Service Pack 1 or 2.
You will get the following error messages in the event logs.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17182
Description:
TDSSNIClient initialization failed with error 0x34, status code 0x1e.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17182
Description:
TDSSNIClient initialization failed with error 0x34, status code 0x1.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17826
Description:
Could not start the network library because of an internal error in the network library.
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17120
Description:
SQL Server could not spawn FRunCM thread.
Solution
- Login as "Administrator".
- Go to "Start > Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager"
- Click "SQL Server 2005 Network Configuration > Protocols for MSSQLSERVER"
- Double click "TCP/IP" in the right side.
- Change "Listen All" to "Yes" in the popup window.
- Click "Ok" button
- Start your MSSQLSERVER service
Related Resources
Navigator
Other Knowledgebase Articles
Basic SQL Hosting
# of Domains:
4
# of SQL Server Databases:
4
Disk Space:
50GB
Bandwidth:
Unmetered
SQL Server 2016
Monthly:
$4.99
Express Hyper-V Hosting
Dedicated Memory:
2GB
Disk Space:
120GB
Bandwidth:
Unmetered
Windows 2016/2012:
Free
Monthly:
$11.99
Dedicated SQL Server
CPU:
Quad-Core X3440 CPU
RAM:
16GB RAM
Disk:
2x120GB SSD + 300GB SATA
RAID:
RAID 1
Bandwidth:
Unmetered
Windows 2016/2012:
Free
Monthly:
$79.00