Cannot Start the SQL Server 2008 Database due to Request Failure or No Response from the Server

Keywords

SQL Server 2008 database, start, fail

Version Mapping

NMS	Platform	OS	Database	NE
All		Windows 2008	SQL Server 2008	Server

 

Symptom

When attempting to start the SQL Server 2008 database, the SQL Server Configuration Manager displays the error message "The request failed or the service did not respond in a timely fashion."

 

Cause Analysis

The database log file C:\MSDATA\MSSQL10.MSSQLSERVER\MSSQL\Log\ERRORLOG recorded the following errors:

2015-01-20 18:05.55 spid16s     29 transactions rolled forward in database 'omcdb' (5). This is an informational message only. No user action is required.

2015-01-20 18:05.62 spid13s     Starting up database 'tempdb'.

2015-01-20 18:05.63 server         A self-generated certificate was successfully loaded for encryption.

2015-01-20 18:05.64 server         Error: 26055, Severity: 16, State: 1.

2015-01-20 18:05.64 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.

2015-01-20 18:05.73 server         Error: 17182, Severity: 16, State: 1.

2015-01-20 18:05.73 server         TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Unable to initialize the VIA listener. The specified module could not be found.

 

2015-01-20 18:05.74 server         Error: 17182, Severity: 16, State: 1.

2015-01-20 18:05.74 server         TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The specified module could not be found.

 

2015-01-20 18:05.74 server         Error: 17826, Severity: 18, State: 3.

2015-01-20 18:05.74 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.

2015-01-20 18:05.74 server         Error: 17120, Severity: 16, State: 1.

2015-01-20 18:05.74 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.

Similar cases can be found on the Internet. This case may result from the enabled Virtual Interface Adapter (VIA) protocol. (The installed database does not support this protocol.)

Problem Identification

Protocol configuration errors on the SQL Server client and server

Solution

1.         Choose Start > All Programs > Sql Server Configuration Manager.

2.         Disable the VIA protocol.

Figure 1-1 Disabling VIA for SQL Native Client 10.0 Configuration (32bit)

 

Figure 1-2 Disabling VIA and Named Pipes for MS SQL Server

 

Figure 1-3 Disabling VIA for SQL Native Client 10.0 Configuration

 

Method:

Double-click the VIA protocol. In the VIA Properties dialog box, set Enabled to No and click OK.

 

3.         Start the database.