Server 2003 Cluster Administrator will not start

Posted on 2011-10-04
Medium Priority
Last Modified: 2012-11-07
Running a 2-node Exchange cluster on Server 2003.  The passive node Cluster Administrator will not start.  Fails with the Error ID: 1130 (0000046a)  "An error occurred attempting to open cluster node "servername."  Not enough server storage is available to process this command.
Other errors occurring:
Event ID: 1009  Cluster service could not join an existing server cluster and could not form a new server cluster.  Cluster services has terminated.
Event ID: 118  The driver for device  \Device\RaidPort 1 performed a bus reset upon request.
Event ID: 1209  Cluster service is requesting a bus reset for device \Device|ClusDisk 0
Thanks in advance for assistance.

Additional information:  The Heartbeat and Public Network Interfaces (on the bad node) are showing unavailable in Cluster Administrator ( on the good node).  Can ping the addresses showing unavailable from the good node.
Question by:rstorm1
  • 3
  • 2
LVL 22

Expert Comment

ID: 36913400
Is this a new cluster or the issue happened of the blue?

Author Comment

ID: 36913892
No, the issue happened when another tech. was in the midst of patching/rebooting the cluster nodes.  I don't know exactly what might have been done, just stuck with trying to troubleshoot and recover.
LVL 22

Expert Comment

ID: 36918230
So the primary node is operational?

If so evict the standby node complete patching etc, then run the following command "CLUSTER /CLUSTER:cluster-name NODE / Force
then join the evicted node back to the cluster.

Accepted Solution

rstorm1 earned 0 total points
ID: 36921043
Resolved the issue.  It appears that someone had applied a security policy to one of the nodes and increased the security of that node making it incompatible with the other node/Cluster Administrator.
The following settings had security increased within secpol.msc Security Settings\Local Policies\Security Options:

Network security: LAN Manager authentication level
Network security: Minimum session security for NTLM SSP based (including secure RPC) clients
Network security: Minimum session security for NTLM SSP based (including secure RPC) servers

Settings were corrected by comparing bad node to known functional Exchange server cluster node and changing settings to match.

Author Closing Comment

ID: 38575291
Problem was solved by further troubleshooting the issue, not from comments.

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many of us need to configure DHCP server(s) in their environment. We can do that simply via DHCP console on server or using MMC snap-in on each computer with Administrative Tools installed in a network. But what if we have to configure many DHCP ser…
Experts-Exchange users below are the steps you can follow to upgrade your Lync server to latest CU's or cumulative updates. Note: Perform it during non-production hours.   Step 1: Backup your lync and SQL server database. Follow below article: h…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question