I wanted to post about a new walkthrough that we have to help in troubleshooting an Event 1135 on a Failover Cluster. As a bit of a background, Failover Clustering sends a heartbeat from and to each node of a Cluster to determine its health and if it responding. If it does not respond in certain time period, it is considered down and will be removed from Cluster membership. 
In the System Event Log of the remaining nodes, an Event 1135 will be triggered stating that the non-responding node was removed. There is now a guided walkthrough to step you through troubleshooting and aiding in determining the cause.
The walkthrough will cover a number of things including Cluster networks, Antivirus, etc. Check it out and see what you think. Try it out the next time to see if it helps. Troubleshooting cluster issue with event ID 1135. • Memory Management, Performance, Printing, Terminal Server • Debugging, Hangs, Tools • DFSR, Certificates, Group Policy • Espanol, Portugues • SMS MOM • Scalable Networking, OCS, Communications Server • Windows Essential Business Server • Microsoft Application Virtualization, SoftGrid, Softricity • DPM related issues • BDD Team • Vista Team Blog • Microsoft GTSC Bucharest / Covering topics such as: Windows Server, Failover Clustering, Performance, Printing, Core OS, AD, Deployment, WSUS, SCOM/SCCM Product Team Blogs.
The RHS.exe process in a Windows Server 2008 Failover Cluster crashes unexpectedly when running Storage Foundation for Windows (SFW) 5.1 SP1. The crash information points to vxres.dll as the possible cause. RHS is the Failover Cluster's monitoring process which continually checks the health/status of all resources that are configured in the cluster to ensure the resources remain in their proper state (i.e. Online); this includes the 'Volume Manager Diskgroup' resource which is represented by vxres.dll. Errors: Below is a list of errors that are reported to the Event Logs. Where to buy pilsner urquell. Cause: An issue was found with the Volume Manager Diskgroup resource (vxres.dll) which resulted in the RHS crash.
Event ID 1541 — Backup and Restore Functionality in a Cluster. ID: 1541: Source: Microsoft-Windows. Tools, and then click Failover Cluster. Aug 09, 2005 Event ID 1146 and 1069 - strange failover scenario. Node cluster, windows server 2003. The description of event id 1146 is: The cluster.
Solution: This issue has been identified and a private fix is available from Veritas Enterprise Technical Support. To obtain the private fix, contact Veritas Support and reference this article during the call. A support representative will be available to assist in troubleshooting this issue.
If it is determined that the private fix addresses the problem, the support representative will further assist in obtaining the private fix. For a complete list of Veritas Enterprise Technical Support contact numbers, go to Note: This fix specifically addresses the problem identified above.
It has not been fully tested and should be applied in a test environment before placing into production. If the systems are not critically impaired, it is recommended to delay the installation of this private fix until the next scheduled maintenance release. Before applying this private fix, systems may be required to be upgraded to the latest code base. The support representative will help in determining the best course of action. Update: • Since the publication of this article, the solution provided in the private fix above has been incorporated into Storage Foundation for Windows (SFW) 5.1 SP2.
• However, there have been cases where SFW 5.1 SP2 also exhibits this behavior. • Another fix was provided in Storage Foundation for Windows 5.1 SP2 Cumulative Patch 14 (CP14) that completely resolves this issue.
• Veritas's best-practice recommendation is to upgrade your SFW 5.1 SP1 installation(s) to SFW 5.1 SP2 and apply the latest Cumulative Patch (at least CP14 or above). • See article (000016935), linked in the Related Articles section below, for a list of available Cumulative Patches. Related Articles References.