The [SQL Server] (MSSQLSERVER) service cannot find the specified module. Stop a service due to a specific service error

Status: After SQL SERVER 2008 is installed some time ago, check whether it is normal and then install VS2010 and VS2012. Copy the data on the server to the local test yesterday. The result shows that the local instance can be connected remotely and cannot be opened.

Step 1: Check the configuration management tool: SQL SERVER service error: Remote Call failed.

Baidu search: After VS2012 is installed, SQL server 2012 express loacldb is installed, which is in conflict with SQL SERVER 2008. Therefore, the SQL SERVER 2012 component is deleted. Check whether the service has been detected. I am glad that it is too early to start several services such as SQL SERVER. View windows logs

View the log files that come with SQL SERVER:

08:01:27. 96 server A self-generated certificate was successfully loaded for encryption.
08:01:28. 01 spid13s The Service Broker protocol transport is disabled or not configured.
08:01:28. 03 spid13s The Database processing ing protocol transport is disabled or not configured.
08:01:27. 99 server error: 26055, severity: 16, status: 1.
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 already upted. please repair or disable the VIA network protocol. error: 0x7e.
08:01:28. 03 spid13s Service Broker manager has started.
08:01:28. 03 server error: 17182, severity: 16, status: 1.
08:01:28. 03 server TDSSNIClient initialization failed with error 0x7e, status code 0x60. Reason: The VIA listener cannot be initialized. The specified module cannot be found.


08:01:28. 07 server error: 17182, severity: 16, status: 1.
08:01:28. 07 server TDSSNIClient initialization failed with error 0x7e, status code 0x1. Reason: initialization failed with infrastructure error. Check for previous errors. The specified module cannot be found.


08:01:28. 07 server error: 17826, severity: 18, status: 3.
08:01:28. 07 server cocould 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.
08:01:28. 07 server error: 17120, severity: 16, status: 1.
08:01:28. 07 Server SQL Server cocould not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

If the VIA Protocol fails, it is disabled.

Go to SQL server configure manager, click SQL server network configuration (non-SQL native client configuration), and disable the VIA protocol.

Start the SQL Server service again.