TDSSNIClient initialization failed with error 0xd, status code 0x36.

I've seen this problem posted a couple times on the MSDN forums so I'm including the problem and the solution here.  The MSDN SQL Server Data Access Forum is available at: https://forums.microsoft.com/msdn/ShowForum.aspx?ForumID=87.

If you see the following error messsages in your SQL Server ERRORLOG:

2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x36.
2005-10-30 15:35:44.79 Server Error: 17182, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server TDSSNIClient initialization failed with error 0xd, status code 0x1.
2005-10-30 15:35:44.79 Server Error: 17826, Severity: 18, State: 3.
2005-10-30 15:35:44.79 Server 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.
2005-10-30 15:35:44.79 Server Error: 17120, Severity: 16, State: 1.
2005-10-30 15:35:44.79 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Check what network protocols are enabled for SQL Server in the SQL Configuration Manager application.  If the VIA protocol is enabled disable it and then try starting the SQL Server service again. 

Hope this helps,
Vaughn