We are trying to install and setup the first node of cluster, however the
setup fails when the Cluster Wizard attempts to start the Cluster Service.
When analyzing the ClCfgSrv.log file, it is apparent that the cluster
installation wizard successfully finds all the necessary resources, inclduing
Network resources, disk resources, Cluster Service Account Info, creates the
Cluster Hive, etc., but fails as soon as the wizard attempts to start the
Cluster service. The Cluster service actaully attempts to start twice and
produces the following errors in the ClCfgSrv.log file (See excerpt below).
Any ideas why?
2006-06-06 11:55:06.107 [INFO] [BC] The 'ClusSvc' service has been
successfully created.
2006-06-06 11:55:06.107 [INFO] [BC] Setting the Cluster service account
information.
2006-06-06 11:55:06.138 [INFO] [BC] Setting the Cluster service failure
actions.
2006-06-06 11:55:06.154 [INFO] [BC] Setting the Cluster service parameters.
2006-06-06 11:55:06.154 [INFO] <SERVER_NAME>: Creating the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E0-7E05-402C-81AA-1C3F1D782031}, 0, 2, 1), (null)
2006-06-06 11:55:06.154 [INFO] <SERVER_NAME>: Creating the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E0-7E05-402C-81AA-1C3F1D782031}, 0, 2, 1), (null)
2006-06-06 11:55:06.169 [INFO] <SERVER_NAME>: Creating the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E0-7E05-402C-81AA-1C3F1D782031}, 0, 2, 2), (null)
2006-06-06 11:55:06.169 [INFO] <SERVER_NAME>: Creating the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E0-7E05-402C-81AA-1C3F1D782031}, 0, 2, 2), (null)
2006-06-06 11:55:06.169 [INFO] <SERVER_NAME>: Starting the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E4-7E05-402C-81AA-1C3F1D782031}, 0, 102, 0), (null)
2006-06-06 11:55:06.169 [INFO] <SERVER_NAME>: Starting the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E4-7E05-402C-81AA-1C3F1D782031}, 0, 102, 0), (null)
2006-06-06 11:55:06.185 [INFO] [BC] Attempting to start the 'ClusSvc'
service.
2006-06-06 11:55:06.982 [INFO] <SERVER_NAME>: Starting the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E4-7E05-402C-81AA-1C3F1D782031}, 0, 102, 1), (null)
2006-06-06 11:55:06.982 [INFO] <SERVER_NAME>: Starting the cluster service
(hr=00000000, {7C5F0774-1611-42B5-AF3C-6E124AC4D36B},
{3ABE14E4-7E05-402C-81AA-1C3F1D782031}, 0, 102, 1), (null)
2006-06-06 11:55:09.982 [INFO] [BC] The service has returned error 0x00042b
to query service status. Throwing an exception.
2006-06-06 11:55:09.982 [INFO] [BC] Error 0x00042b occurred trying to start
the 'ClusSvc' service.
2006-06-06 11:55:13.747 [INFO] [BC] Cluster Service Win32 Exit Code= 0x00042b
2006-06-06 11:55:13.747 [INFO] [BC] Cluster Service Specific Exit Code=
0x000057
2006-06-06 11:55:13.747 [INFO] [BC] Caught exception during commit.
I found MS KB article 890761 (
http://support.microsoft.com/?kbid=890761)
which makes reference to NTLM being to strict, but I have confirmed that this
is not our issue. I was not able to find anything that details what the
'Win32 Exit Code= 0x000057' error is about though.
As for hardware and configuration, the servers are IBM BladeCenter HS20
servers running W2K3 Ent Ed and booting from the SAN. All nodes are powered
off except for the node we are trying to establish the cluster on. We have
enabled the MS "ManageDisksOnSystmBuses" registry hack as well. The SAN
storage resides on an IBM ESS 800 Shark and is presented via an SVC (Ver
3.1). We are using IBM SDDDSM (2.1.0.3, I think) with the Qlogic Storport
driver (9.0.1.93) and are able to see all of our storage appropriately. Any
and all help would be appreciated. Thanks!