[SQL Server] (MSSQLSERVER) service because the specified module could not be found. Service-specific error stopped

Status: Install SQL SERVER 2008 earlier, check Normal, and then install VS2010 and VS2012. Yesterday, copying the data on the server to the local test, the results found that can be connected to remote, unable to open the local real example.

First step: View the Configuration management tool: SQL SERVER Service error: Remote call failed.

Baidu Search: VS2012 installation will install SQL Server EXPRESS loacldb, and SQL Server 2008 conflicts. Therefore, remove the components of SQL SERVER 2012. Check service found out, happy or too early. Several services, such as SQL SERVER, have been unable to start. View Windows Logs

To view a log file that comes with SQL SERVER:

2014-06-06 08:01:27.96 Server A self-generated certificate is successfully loaded for encryption.
2014-06-06 08:01:28.01 spid13s The Service Broker protocol transport is disabled or not configured.
2014-06-06 08:01:28.03 spid13s The Database Mirroring protocol transport is disabled or not configured.
2014-06-06 08:01:27.99 Server error: 26055, severity: 16, State: 1.
2014-06-06 08:01:27.99 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.
2014-06-06 08:01:28.03 spid13s Service Broker Manager has started.
2014-06-06 08:01:28.03 Server error: 17182, severity: 16, State: 1.
2014-06-06 08:01:28.03 Server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: Could not initialize VIA listener. The specified module could not be found.


2014-06-06 08:01:28.07 Server error: 17182, severity: 16, State: 1.
2014-06-06 08:01:28.07 Server TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: Initialization failed with infrastructure error. Please check for previous errors. The specified module could not be found.


2014-06-06 08:01:28.07 Server error: 17826, severity: 18, State: 3.
2014-06-06 08:01:28.07 Server Could not start the network library because of a internal error in the network library . To determine the cause, review the errors immediately preceding this one in the error log.
2014-06-06 08:01:28.07 Server error: 17120, severity: 16, State: 1.
2014-06-06 08:01:28.07 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.

Via protocol error, simply forbidden.

Enter SQL Server Configure Manager to disable the VIA protocol by opening the SQL Server network configuration (non-SQL Native Client configuration).

Start the SQL Server service again, successfully.