Sqlserver service manager cannot start the service

Sql2000 error 1053 causes service startup failure solution

Symptoms:

1. The service manager cannot start the service. The error 1053 is displayed #
2. Open mssql Enterprise Manager and prompt that msvcp71.dll is missing

Solution:

Download msvcp71.dll and msvcr71.dll from the attachment to system32.

The SQL SERVER 2005 + SP3 version suddenly fails to start the service.

Error code

18:12:40. 61 server error: 17182, severity: 16, status: 1.
2010-09-12 18:12:40. 61 server TDSSNIClient initialization failed with error 0x2, status code 0xd.
18:12:40. 61 server error: 17182, severity: 16, status: 1.
2010-09-12 18:12:40. 61 server TDSSNIClient initialization failed with error 0x2, status code 0x1

Cause analysis:

According to the prompts in this article, the red part of the error code prompts are more useful, the reason is that SQL server Configuration Management-> SQL SERVER 2005 network configuration-> The enabling and configuration of TCP/IP under MSSQLSERVER protocol. When the preceding error occurs, TCP/IP cannot be started.

When you open its properties, you find that in the "protocol" column, only "keep active", and none of the other three. In the "IP address" column, IPALL is missing. The solution to this problem is to add a missing entry for TCP/IP in the registry.

Solution:

1. Start-> Run-> regedit, find HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerMSSQL.1MSSQLServerSuperSocketNetLibTcp

1) add "Enabled", type dword, value: 1.

Add IPALL items and add items

SQLserverAgent cannot be started on the SQL Server

Data Backup on servers is one of the most important tasks of network administrators in their daily work. The SQLServerAgent service allows us to use the SQL database
The maintenance plan function is used to automatically back up data, but recently I found that the SQLServerAgent service on the server cannot be started. In retrospect, the most recent operation was due to my
The server access permission of the Builtin/Administrators account in SQL is disabled, because the existence of this account is not safe for SQL, but does not want to delete it.
Therefore, the permission is disabled. As a result, the SQLServerAgent service cannot be started.
The solution is simple. You only need to delete this account, create a user with both system management and SQL management permissions, and then use this user to start
You can use the SQLServerAgent service. The procedure is as follows:
1. Open the Enterprise Manager, open the instance on the left-> Security-> log on, right-click the blank area on the right, select "New logon", and click the button on the right of "name,
Many account names will appear. Select a user with windows Super Administrator permissions (such as Administrator), click "add", and then click the "server role" tab.
Check "System Administrators" and click OK.
2. Open "manage" on the left of Enterprise Manager, right-click "SQLServer proxy", select Properties-> General-> service startup account, select "this account", and enter
The account and password (for example,./Administrator) you just created. The password is the password of this user. OK.
3. Finally, right-click "SQLServer proxy" and select "start". The Agent is successfully started.

The SQL server cannot be started and cannot be connected to (LOCAL).

First, you just need to find the server to start up in the service. I think this method is probably good and easy to operate. However, the check is not very serious, MSSQLSERVER (yes, of course) is not found. Only one SQLSERVERAGENT is found. It cannot be started when it is enabled. It must be that MSSQLSERVER is not started first.

It fails to establish a connection with (local)
 
The reason is that SQL cannot be logged on:
 
1. You have modified the windows administrator password and user name, but you forgot to modify the SQL. Naturally, you cannot log on. Modify the password and synchronize it!
 
2. Accidentally deleted Administrator users (SQL windows logon accounts BUILTINAdministrators and Administrator)
Use the following methods:
 
You need to re-run the SQL SERVER installation program, select "Advanced options" in the "installation options" interface, and then select "registry reconstruction". The next step is similar to the installation process, note: When selecting "authentication mode", select "hybrid mode" to make the sa account valid. After reconstruction, log on with the query analyzer, log on with the sa account, and execute sp_grantlogin 'builtinadministrators 'in the query analyzer'
In this way, the windows Authentication is restored.

If only BUILTINAdministrators is deleted, but the administrator is not active, you can open it through the query analyzer,
Connect with sa, and then sp_grantlogin 'builtinadministrators 'to run