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 How-Tos
External Windows Resources
External SQL Server Resources
External Webmaster Resources
External Developer Resources
Questions?
Please email to webmaster[$]dedicatedsqlserver.com.
Lite SQL Server
CPU: Intel Core 2 Duo E6320
CPU Speed: 1.86GHz
Cache: 4MB
RAM: 1GB RAM
Disk: 2x160B SATA
RAID: RAID 1
Bandwidth: 1000GB
Win2008 Web or Win2003 STD: Free
IP Addresses: 8
Monthly: $119.00
Detail...
Standard SQL Server
CPU: Quad-Core Xeon E5410
CPU Speed: 2.33GHz
Cache: 12MB
RAM: 2GB RAM
Disk: 2x146GB SCSI
RAID: RAID 1
Bandwidth: 1500GB
Win2008 Web or Win2003 STD: Free
IP Addresses: 8
Monthly: $259.00
Detail...
|