Server 2003 Cluster Administrator will not start

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.
LVL 4
rstorm1Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

65tdRetiredCommented:
Is this a new cluster or the issue happened of the blue?
0
rstorm1Author Commented:
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.
0
65tdRetiredCommented:
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.
0
rstorm1Author Commented:
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.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rstorm1Author Commented:
Problem was solved by further troubleshooting the issue, not from comments.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.