none
SQL 2005 TDSSNIClient initialization failed with error 0x32, status code 0x1c (Clustered environment)

    Question

  • I've seen other posts on this topic, but not with error 0x32.

    I was attempting to change a CLUSTERED instance of SQL 2005 from dynamic port to static port and in the process have somehow messed it up to the point it will no longer start.    Version is 9.00.2047.00

    The ERRORLOG has the following

    2007-01-31 15:02:05.77 spid9s      Starting up database 'model'.
    2007-01-31 15:02:05.77 Server      Error: 17182, Severity: 16, State: 1.
    2007-01-31 15:02:05.77 Server      TDSSNIClient initialization failed with error 0x32, status code 0x1c.
    2007-01-31 15:02:05.77 Server      Error: 17182, Severity: 16, State: 1.
    2007-01-31 15:02:05.77 Server      TDSSNIClient initialization failed with error 0x32, status code 0x1.
    2007-01-31 15:02:05.77 Server      Error: 17826, Severity: 18, State: 3.
    2007-01-31 15:02:05.77 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.
    2007-01-31 15:02:05.77 Server      Error: 17120, Severity: 16, State: 1.
    2007-01-31 15:02:05.77 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.

    The values have only been changed using SQL Server Configuration Manager (no direct registry changes have been made). 

    Thanks for you help.

    Wednesday, January 31, 2007 8:23 PM

Answers