SQL (MSSQLSERVER) service startup error code 3414 workaround _mssql

A customer contacted me, said their front system error, sent me a picture of the error. The first sight of the error is that the database is out of the problem and cannot be connected to SQL Server.

Although know that the database is a problem, but the beginning of the time did not open SQL Server, can not be remote control, the first thing to do is to check the customer's front desk IP is not a problem, because the previous IP address set to automatically obtain, resulting in inaccessible. After checking, these configurations are fine. Then, the user can only be networked, remote operation. SQL Server failed to start, prompting for error messages:

This problem has been encountered several times before, mainly because some of the services in SQL Server failed to start. To open the Configuration Manager for SQL Server, first set the options in the MSSQLSERVER protocol in the SQL Server network configuration as follows:

The SQL Server (MSSQLSERVER) service in SQL Server service is then started.

Normally, the SQL Server service can be started, but it will not work if an abnormal situation occurs. The client side of the server will not be able to start because his server has an abnormal power outage, causing the file corruption in SQL Server. Therefore, when you start the SQL Server (MSSQLSERVER) service, you are prompted with a 3414 error .

Workaround:

1, from the installation of SQL and the normal operation of the computer to copy a file, to find the database installation path, such as my installation path is: C:\Program Files\Microsoft SQL Server\mssql.1\mssql\data, Copy Model.mdf and Modellog.ldf;

2, the copy of the file placed in the wrong computer installation path (with the above), replace the original problem of the file can be.

Summary:

SQL Server is essential to our development projects, so it is important to have a good command of his operational skills. There is in the face of problems, do not rush to solve, to analyze what has been done after the errors caused, so that both can avoid similar errors, but also to our solution to bring great convenience.

This is a complete case for troubleshooting SQL (MSSQLSERVER) service startup errors, and I hope that you can get help from it.