After the cluster is configured, change the startup mode of the cluster service to Auto. Usually, the cluster service automatically starts after the system is started.
Step 1 Check the status of the cluster service. Check the status and startup mode of the cluster service. It is confirmed that although the startup mode of the cluster service is Auto, the cluster service is actually not started. Try to enable the cluster service manually but the cluster service still fails to be started. A message is displayed, indicating that the cluster services on the local computer fail to be started due to a login failure and the error ID is 1069. The possible causes are: The relevant service status of the cluster service dependency is abnormal. A fault occurs during the process for logging in to the cluster service, for example, the account password is incorrect or changed.
Step 2 Check the dependency of the cluster service. If the relevant service status of the cluster service dependency is abnormal, the cluster service may fail to be started properly. Check Dependency in the cluster service properties to determine the services to be started, including Remote Processdure Call (RPC), Windows Time, and Net Logon. In computer management, make sure that the previous three services have been in the starting state and their startup modes are Auto. After that, the cluster service still fails to be started manually. Therefore, the fault is not caused by the dependency of the cluster service.
Step 3 Check the login process of the cluster service. When creating the MSCS cluster, create a user who can use the administrator account to log in to the cluster and create user cluster to manage the cluster. Its password is different from the password of user administrator. If the password of user cluster is changed or the system is abnormal, the cluster service may fail to be started. Reset user cluster. After the password is reset, the cluster service can be started manually. Therefore, the fault is caused by incorrect login password. After the fault is rectified, open the cluster manager to log in to the connected cluster. All applications of the cluster are normal.