Unable to install Sqlserveragent job and sqlserver2000

SQL Server SQLserverAgent cannot be started solution SQL2000 cannot be installed solution favorites SQL Server SQLserverAgent cannot be started solution for server data backup work is the most important work of network administrators in daily work one, the SQLServerAgent service allows us to use the "Database Maintenance Plan" on SQL"

SQL Server SQLserverAgent cannot be started solution SQL2000 cannot be installed solution favorites SQL Server SQLserverAgent cannot be started solution for server data backup work is the most important work of network administrators in daily work one, the SQLServerAgent service allows us to use the "Database Maintenance Plan" on SQL"

How to solve the problem that SQLserverAgent cannot be started on SQL Server & how to install SQL2000

Solution to SQL Server Agent failure

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 Maintenance Plan" function to automatically back up data, however, I recently discovered that the SQLServerAgent service cannot be started on the server. In retrospect, I used to recall that I disabled the server access permission for the Builtin/Administrators account in SQL, the existence of this account is not safe for SQL, but does not want to delete it. Therefore, the permission of this account is forbidden. 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 the SQLServerAgent service. The procedure is as follows:

2. Open "manage" on the left of Enterprise Manager, right-click "SQLServer proxy", select Properties-> General-> Service Startup account, and select "this account ", then enter the account and password (for example :. \ Administrator). The password is the password of this user. OK.

3. Finally, right-click "SQLServer proxy" and select "start". The Agent is successfully started.

After the administrator password of the System user is changed, log out and log on again. the SQL Server is not started at random. Manually from Service Manager
The system prompts "the service cannot be started due to logon failure ".
Cause:
When installing SQL Server, the default logon user is used as the account for starting the SQL Server service (for the Standalone
(Usually administrator). When the user changes the user name (for example, the administrator is changed to admin) or the password is changed.
When the server is started again, the error "cannot start the service due to logon Failure" appears.
The solution is as follows:
1. Change the administrator password back to the original password;
2. Start SQLServer from the Database Service Manager;
3. Modify the administrator password from "Computer Management;
4. Open the Database Enterprise Manager and find the server to be modified in the database server list on the left. Right-click the server and choose 【
Properties. In the displayed Properties dialog box, select the "Security" Table item;
5. In the "Start Service Account" option, change the password to the new password of administrator, and click "OK ".
", The system prompts" do you want to stop and restart the server now ?", Click "yes ". The database server automatically stops and restarts.
.
Suggestions and summary:
1. If the option at "Start Service Account" is not "this account", but "System Account", the user password will not be changed
The database fails to be started;
2. The database server must be in the running status to modify its attributes. Otherwise, the database server cannot be connected. Therefore, the original password must be changed back,
Modify the database after it is started;
3. You must change the administrator password before modifying the Security Attribute of the database. Otherwise, the password cannot be modified.

Solution to SQL2000 installation failure

1. Delete the SQL installation directory under Program files (back up important data first)
C: \ Program Files \ Microsoft SQL Server \ 80 \ Tools.
C: \ Program Files \ Microsoft SQL Server \ MSSQL.

2. Delete related information in the registry:
HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ MSSQLServer.
HKEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Services \ MSDTC.

3. Find the PendingFileRenameOperations project in HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager and delete it. In this way, you can clear the temporary installation project.

4. HKEY_LOCAL_MACHINE \ SOFTWARE \ Microsoft \ Windows \ CurrentVersion \ setup
Delete predictioncomponents

There may be a lot of content in this project, and this method can be used only when the above methods are not feasible (Be sure not to delete all)
Before deleting the content, read the description.

5. The Sqlstp. log file in the Windows directory lists detailed information about the operations performed by the installer and contains all errors encountered during installation. By checking this file, you can learn in detail where the installation fails and why it fails.

6. The error message during SQL installation is stored in a Log file named Errorlog. By default, this file is stored in the Program Files \ Microsoft SQL Server \ Mssql \ Log directory. This error log contains the errors encountered by SQL-Server when the installer tries to start SQL-Server. This information can help you thoroughly check the cause of the error.

7. Another component to be checked is the Microsoft Data Access Component (MDAC) Installer which starts as part of the SQL-Server2000 installer. The SQL-Server2000 installer installs MDAC2.6. The MDAC installer creates a separate log file named Dasetup. log. You can view this log file and ensure that the MDAC installer has no problems.

------------------------------

Install SQL SERVER 2000. Unexpectedly, it would be difficult to Install SQL SERVER 2000 after uninstalling it. The "installation program configuration SERVER failed" always appears in the configuration service section starting at the last step. Refer to errors such as server error log and C: \ WINNT \ sqlstp. log, and the Enterprise Manager cannot be found in the Start-program menu.

Solution:

I checked the installation directory online and deleted the directory C: \ Program Files \ Microsoft SQL Server. The installation still failed, which is strange, is it because the specified database file directory has to be deleted, and then the Data file directory I put on the E disk is deleted. Because it was previously installed, the "MSSQL" directory exists, after this directory is deleted, the installation is successful!

In the "installation and selection" dialog box, select "advanced options", then select "Registry reconstruction", and then click OK. Everything is OK!

Tip:
? Before deleting the MSSQL directory, check whether the directory contains useful database files. If yes, back up the files to other directories.
? After you fail to reinstall SQL Server, follow these steps to install it multiple times without restarting it.
1. Enter regedit in start-> running
2. to the HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Session Manager location
3. Select File> export and save (for security reasons)
4. Right-click PendingFileRenameOperations in the right window, select Delete, and then confirm