ID #1108

Error Messages of SQL Server 2005 Start Up Failure(Part 1)

Part I - Read correct error info and find the exact error status code. 

 

you will see following sentence in ERRORLOG if server fail to start:

 

2012-04-20 18:42:26.10 Server      Error: 26055, Severity: 16, State: 1.
2012-04-20 18:42:26.10 Server      The SQL Server failed to initialize VIA support library [QLVipl.dll]. This normally indicates the VIA support library does not exist or is corrupted. Please repair or disable the VIA network protocol. Error: 0x7e.

2012-04-20 18:42:26.15 Server      Error: 17182, Severity: 16, State: 1.
2012-04-20 18:42:26.15 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x60.

2012-04-20 18:42:26.15 Server      Error: 17182, Severity: 16, State: 1.
2006-04-20 18:42:26.15 Server      TDSSNIClient initialization failed with error 0x7e, status code 0x1.
2006-04-20 18:42:26.15 Server      Error: 17826, Severity: 18, State: 3.
2006-04-20 18:42:26.15 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.
2006-04-20 18:42:26.15 Server      Error: 17120, Severity: 16, State: 1.
2006-04-20 18:42:26.15 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.

 

1. The *Pink* part is optional, which means, sometimes you will not see it, since it is specific error info that server dump only for certain scenarios. Therefore, if the pink part is avaliable, it is veryyo decriptive to tell you what was wrong with server, in this example, it indicate that server load VIA provider module fail since you might enabled VIA.

 

2. The *Blue* and *Green* parts are always present.

The *Green* Part is general error info, they occured in each fail scenario, you can tell from those keywords that I marked with underscore.

1) Error: 17182 ... status code 0x1    0x01 is general status code

2)  Error: 17826, Severity: 18, State: 3 and statement

3)  Error: 17120, Severity: 16, State: 1 and statement

Therefore, *Green* part is ignorable, or not key point for troubleshooting start up failure.

 

3. The *Blue* part is most important and the key to address your problem. To summary, when server start up fail,

Step 1: find the *first line* with " Error 17182 ";

Step 2: find the key words "TDSSNIClient initialization failed with error <xxx>" , <xxx> is the OS error, by typing " net helpmsg xxx", you will get clue. In above example, 0x7e = 126 (decimal )

C:\>net helpmsg 126

The specified module could not be found.

Step 3: find the status code that followed: status code <xxx>, here is 0x60.

Tags: -

Related entries:

You cannot comment on this entry