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.
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.
Last Comment
65td
Is this a new cluster or the issue happened of the blue?
ASKER
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.
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.
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.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Problem was solved by further troubleshooting the issue, not from comments.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
