After setting SQL Server 2005 yesterday, the service cannot be started. Later, you can view the log:
2008-09-05 08:40:17. 82 server a self-generated certificate was successfully loaded for encryption.
08:40:17. 82 server error: 17182, severity: 16, status: 1.
2008-09-05 08:40:17. 82 server tdssniclient initialization failed with error 0x7e, status code 0x60.
08:40:17. 82 server error: 17182, severity: 16, status: 1.
2008-09-05 08:40:17. 82 server tdssniclient initialization failed with error 0x7e, status code 0x1.
08:40:17. 82 server error: 17826, severity: 18, status: 3.
2008-09-05 08:40:17. 82 server cocould 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.
08:40:17. 82 server error: 17120, severity: 16, status: 1.
2008-09-05 08:40:17. 82 server SQL Server cocould not spawn fruncm thread. Check the SQL Server Error Log and the Windows event logs for information about possible related problems.
Then I checked the relevant information on the Internet and finally found that I enabled the "via protocol" and disabled the "via protocol" to solve the problem.
"Via protocol" Deactivation method: start-> Program-> Microsoft SQL Server 2005-> Configuration tool-> SQL Server Configuration Manager-> open and find "SQL Server 2005 network configuration"-> protocol of MSSQLServer attribute on the right in the properties box, disable the "via protocol!
I hope to provide some help to my friends who have encountered the same problem!