Condividi tramite

SQL Server Startup Issue related to TDSSNIClient error 0x7e status 0x60

  • Articolo

Just thought I would jot down some interesting information I ran across while trying troubleshoot securing down SQL Server 2005.

Symptoms:
TDSSNIClient initialization failed with error 0x7e, status code 0x60.
TDSSNIClient initialization failed with error 0x7e, status code 0x1.
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.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Problem:
If you inadvertantly enable the VIA protocol (even though it is last in the order) without the proper configuration SQL Server will not load at all.  In my situation I did not need the VIA protocol so disabling it fixed the problem above, or should I say stopped the errors from occuring since no need to load the protocol.  By default (at least in my installation) it is not enabled by default.

I hope this helps.

Comments

  • Anonymous
    July 03, 2006
    thanks

  • Anonymous
    December 18, 2006
    Yes, this post helped me.

  • Anonymous
    March 07, 2007
    ditto... eternally grateful.

  • Anonymous
    April 12, 2007
    awsome...Going thru this post saved lot of time. thanx a lot

  • Anonymous
    April 25, 2007
    Thanks a lot. This has saved a lot of time for me too.

  • Anonymous
    May 30, 2007
    Thank You.

  • Anonymous
    June 05, 2007
    Hi:  My server environment are 2 server runnung win2003 EE with sql server 2005 cluster,and  I have a some problem with this article,but when I stop the via protocal in sql server configuration manager,and bring online the sql group again,the sql server and sql server agent resource still fail to start and VIA protocal enable automatic,couldn't anyone help me? manay thanks.

  • Anonymous
    July 17, 2007
    Thanks so much.  I had the same error and this fixed it.

  • Anonymous
    February 09, 2008
    Thanks a lot. It helped me out.

  • Anonymous
    September 10, 2008
    Can you kindly help me ,i am getting the below error.I tried diabling VIA Prot.Still i am getting the same. 2008-09-10 17:32:54.23 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 3) 2008-09-10 17:32:54.23 Server      (c) 2005 Microsoft Corporation. 2008-09-10 17:32:54.23 Server      All rights reserved. 2008-09-10 17:32:54.23 Server      Server process ID is 1456. 2008-09-10 17:32:54.23 Server      Logging SQL Server messages in file 'D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2008-09-10 17:32:54.23 Server      This instance of SQL Server last reported using a process ID of 1788 at 9/10/2008 5:31:02 PM (local) 9/10/2008 1:31:02 PM (UTC). This is an informational message only; no user action is required. 2008-09-10 17:32:54.23 Server      Registry startup parameters: 2008-09-10 17:32:54.23 Server       -d D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2008-09-10 17:32:54.23 Server       -e D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2008-09-10 17:32:54.23 Server       -l D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2008-09-10 17:32:54.24 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2008-09-10 17:32:54.24 Server      Detected 2 CPUs. This is an informational message; no user action is required. 2008-09-10 17:32:54.60 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required. 2008-09-10 17:32:54.65 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2008-09-10 17:32:54.71 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted.  If you would like distributed transaction functionality, please start this service. 2008-09-10 17:32:54.71 Server      Database Mirroring Transport is disabled in the endpoint configuration. 2008-09-10 17:32:54.71 spid5s      Starting up database 'master'. 2008-09-10 17:32:55.35 spid5s      SQL Trace ID 1 was started by login "sa". 2008-09-10 17:32:55.46 spid5s      Starting up database 'mssqlsystemresource'. 2008-09-10 17:32:56.42 spid5s      Server name is 'LP00187'. This is an informational message only. No user action is required. 2008-09-10 17:32:56.43 spid9s      Starting up database 'model'. 2008-09-10 17:32:56.84 Server      A self-generated certificate was successfully loaded for encryption. 2008-09-10 17:32:56.84 Server      Error: 17182, Severity: 16, State: 1. 2008-09-10 17:32:56.84 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x60. 2008-09-10 17:32:56.84 Server      Error: 17182, Severity: 16, State: 1. 2008-09-10 17:32:56.84 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x1. 2008-09-10 17:32:56.84 Server      Error: 17826, Severity: 18, State: 3. 2008-09-10 17:32:56.84 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. 2008-09-10 17:32:56.84 Server      Error: 17120, Severity: 16, State: 1. 2008-09-10 17:32:56.84 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.

  • Anonymous
    June 16, 2009
    PingBack from http://topalternativedating.info/story.php?id=11902