The second issue was about a two-node SQL Server cluster down.
1) Users cannot connect to any of the databases, no database is available;
2) Cluster is gone as cluster service down locally on each node (cluster administrator);
Check & confirmation:
Error “1075 The dependency service does not exist or has been marked for deletion.” reported while attempting to manually re-start the cluster service. Rebooting the nodes does not fix the issue either.
The Windows Time service on which the cluster service depends disappeared from both nodes, as shown in the screen-shot(in which the Windows Time service actually presents).
Windows Time service uses w32time.exe and w32time.dll. And these two needs to be repaired or replaced by WFP (Windows File Protection) to get the Windows Time service back. WFP is from %windir%\system32\dllcache, and a Windows Administrator needs to run from a command prompt on both nodes for the reparation:
Detailed information about WFP may be found from:
Once the foregoing command executed successfully, go back to the services panel to start the Windows Time service first (if not started) and then bring back on the cluster service on both nodes.
The next few tasks are for a DBA to bring online the database resources; verify the health of the databases; check connectivity both internal and external; and check OS event logs. A clean reboot then is demanded for both nodes, provided that all the DBA checks and verifications are clean.
The very last step is a reallocation of the databases to move them to their preferred nodes.
By now a healthy cluster is back in service again.