In SQL Server 2000, "this operation cannot be performed when the SQLServerAgent is being started. Please try again later ." Error

An error occurred while running the scheduled task with the SQL Server proxy (SQLServerAgent) Today. "This operation cannot be performed when the SQLServerAgent is being started. Please try again later ."

There are two solutions on the Internet:

I. csdn solution: cancel the Windows NT fiber configuration of the database server and restart the SQL Server server.

2. Backing up data on servers is one of the most important tasks of network administrators in their daily work. The SQLServerAgent service enables us to use the "Database Maintenance Plan" function on SQL to automatically back up data, however, I recently discovered that the SQLServerAgent service cannot be started on the server. I thought back to the recent operations because I put the SQL
Builtin/administrators: the server access permission of this account is forbidden, because the existence of this account is not safe for SQL, but you do not want to delete it, so the permission 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:

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 select "System Administrators" in the "server role" tab, OK.

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.

Because the problematic server has multiple CPUs, the option to use Windows NT fiber is previously configured. After this option is canceled, the problem is solved. solution 2 has not been tried, I wonder if it is correct.