How to fix “The cluster resource could not be brought online by the resource monitor. [ERROR_RESMON_ONLINE_FAILED (0x139A)]” – Error Code 5018

Overview

In this article, we’ll focus on resolving the issue described as: “The cluster resource could not be brought online by the resource monitor. [ERROR_RESMON_ONLINE_FAILED (0x139A)]”. This error, identified by the error code Error Code 5018, can impede your system’s performance, and here’s how you can fix it.

Identifying the Problem

Error Code 5018 occurs when a cluster resource fails to be brought online. It can manifest during various system operations, including starting a cluster service or restarting a node within the cluster. The error message, “The cluster resource could not be brought online by the resource monitor,” provides a clear indication of the problem.

Common Fixes

1. Check Cluster Services:
– Verify that all essential cluster services, such as the Cluster Service (ClusSvc) and the Cluster Network Service (NetClus), are running.
– If any services are stopped, start them and check if the issue persists.

2. Restart the Cluster Service:
– Right-click on “Computer Management.”
– Expand “System Tools” and select “Cluster Manager.”
– In the “Cluster” pane, right-click on the cluster name and select “More Actions” > “Restart Cluster Service.”
– Once the service is restarted, check if the error resolves.

Advanced Troubleshooting

1. Check Cluster Logs:
– Open Event Viewer and navigate to “Applications and Services > Microsoft > Windows > Cluster.”
– Review the logs for any errors or warnings related to Error Code 5018.
– Look for indications of issues related to quorum or cluster communication.

2. Disable Anti-Virus and Firewall:
– Temporarily disable any third-party anti-virus and firewall software.
– These programs may interfere with cluster communication, causing Error Code 5018.

Conclusion

By implementing these fixes, you should be able to resolve Error Code 5018 and restore your cluster’s functionality. To prevent future occurrences, ensure that cluster services are running properly, monitor the cluster logs for potential issues, and consider disabling any external programs that may hinder cluster communication.