SQL server08 (MSSQLServer) cannot be started

Error Log:

SQL Server cannot generate fruncm threads. Check the SQL Server Error Log and Windows event log to obtain information about possible problems.

The network library cannot be started because of an internal error in the network library. To determine the cause, check the errors that are located before the error in the error log.

Tdssniclient initialization failed, error 0x7e, statusCode0x1. Cause: the initialization fails and the Infrastructure error occurs. Check for previous errors. The specified module cannot be found.

Tdssniclient initialization failed with error 0x7e and status code 0x60. Cause: the via listener cannot be initialized. The specified module cannot be found.

SQL Server Cannot initialize via support library [qlvipl. dll]. This usually indicates that the via support library does not exist or is damaged. Fix or disable the via network protocol. Error: 0x7e.

Network reprint:

We can determine that the problem may be the following:

1. The IP address configuration may be incorrect. Solution-bottom:

Open SQL Server Configuration Manager under Microsoft SQL Server 2005 Configuration tool, select MSSQLServer protocol, double-click the TCP/IP in the right window, and check the IP configuration in the pop-up window.

Generally, the default ip2 is 127.0.0.1. For example, the service cannot be started if the ping from port 1433 of the first IP address fails. You can set 127.0.0.1-to IP1. The service can be started normally regardless of whether the port of ip2 can be pinged or not. You can also set-IP1 to the IP address of the current machine and ensure that the port of-IP address can be pinged.

2. It may be because the via protocol is enabled. Solution:

Open SQL Server Configuration Manager under Microsoft SQL Server 2005 Configuration tool, select MSSQLServer protocol, and then right-click the window on the right to disable it, and click "OK. In this case, start the S-qlserver service again. If not, you can restart the computer. If not, I can disable it or not. After the computer is restarted, it can be used!

In addition, changing the administrator password will also cause the sqlserve-r service to fail to start. The solution is as follows:

Open SQL Server Configuration Manager under Microsoft SQL Server 2005 Configuration tool, open SQL Server properties,

Change the password of this account to the administrator password after you change it. Click "OK. At this time, the SQL Server service should be able to start normally.

I am using via because it has no application. It can be disabled later. However, because the machine name has been changed, it is not logged on now. Continue ......