Welcome to MSDN Blogs Sign in | Join | Help

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

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.

Published Wednesday, January 18, 2006 1:31 PM by mab

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

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

thanks
Tuesday, July 04, 2006 3:38 AM by cc

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

Yes, this post helped me.

Monday, December 18, 2006 8:12 PM by ljiang

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

ditto...

eternally grateful.

Wednesday, March 07, 2007 10:20 PM by ml

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

awsome...Going thru this post saved lot of time.

thanx a lot

Friday, April 13, 2007 6:49 AM by satish

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

Thanks a lot. This has saved a lot of time for me too.

Thursday, April 26, 2007 4:12 AM by Ramnathan

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

Thank You.

Thursday, May 31, 2007 2:27 AM by Posina

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

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.

Tuesday, June 05, 2007 8:44 AM by erictsai

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

Thanks so much.  I had the same error and this fixed it.

Tuesday, July 17, 2007 3:53 PM by Trey

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

Thanks a lot. It helped me out.

Sunday, February 10, 2008 5:34 AM by kamran wali

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

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 Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

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 Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2008-09-10 17:32:54.23 Server       -e D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2008-09-10 17:32:54.23 Server       -l D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.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.

Wednesday, September 10, 2008 9:45 AM by syousuf

# Mark Brown s Blog SQL Server Startup Issue related to TDSSNIClient | alternative dating

PingBack from http://topalternativedating.info/story.php?id=11902

Wednesday, June 17, 2009 3:43 AM by Mark Brown s Blog SQL Server Startup Issue related to TDSSNIClient | alternative dating

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker