The installation is progressing, however, it's failing in new and
exciting ways. I'm encountering two different errors in my System
Event Log:

Cluster resource 'SQL Network Name (XXXXXXX)' in clustered service or
application 'SQL Server (XXXXXXX)' failed. Source: FailoverClustering
EventID: 1069

Then I get this error:
Cluster network name resource 'SQL Network Name (XXXXXXX)' failed to
create its associated computer object in domain 'plex.com' for the
following reason: Unable to update password for computer account.

The text for the associated error code is: Access is denied.


Please work with your domain administrator to ensure that:
- The cluster identity 'XXXXXXX' can create computer objects. By
default all computer objects are created in the 'Computers' container;
consult the domain administrator if this location has been changed.
- The quota for computer objects has not been reached.
- If there is an existing computer object, verify the Cluster Identity
XXXXXXX' has 'Full Control' permission to that computer object using
the Active Directory Users and Computers tool.

I have verified that all of the objects related to the SQL Cluster I'm
trying to build are in the same OU, and they have full control rights
to the SQL Server resource I'm trying to bring online.

When I investigate the detail log of the installation it would appear
there is a problem with some of the x64 components registering or
returning the desired results so things don't wrap up correctly. Here
are a couple samples from the detail log:

2009-07-21 10:17:25 Slp: Error: Action
"ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_ inst_Cpu64_Install_Finalize_finalize"
failed during execution.
2009-07-21 10:17:25 Slp: Action
"cluster_group_cluster_finalconfig_Cpu64" will return false due to the
following conditions:
2009-07-21 10:17:25 Slp: Condition "Feature dependency condition for
action: cluster_group_cluster_finalconfig_Cpu64 The condition tests
feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10
dependant features. The feature is tested for results: ValidateResult,
Result, CleanupResult." did not pass as it returned false and true was
expected.
2009-07-21 10:17:25 Slp: Condition is false because the required
feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in
result Result
2009-07-21 10:17:25 Slp: Error: Action
"cluster_group_cluster_finalconfig_Cpu64" failed during execution.
2009-07-21 10:17:25 Slp: Action
"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_in st_Cpu64_Install_Finalize_finalize"
will return false due to the following conditions:
2009-07-21 10:17:25 Slp: Condition "Feature dependency condition for
action:
ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_ins t_Cpu64_Install_Finalize_finalize
The condition tests feature:
MPT_AGENT_CORE_CNI_sql_engine_core_inst_Cpu64. There are 2 dependant
features. The feature is tested for results: ValidateResult, Result,
CleanupResult." did not pass as it returned false and true was
expected.
2009-07-21 10:17:25 Slp: Condition is false because the required
feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in
result Result
2009-07-21 10:17:25 Slp: Error: Action
"ConfigEvent_MPT_AGENT_CORE_CNI_sql_engine_core_in st_Cpu64_Install_Finalize_finalize"
failed during execution.
2009-07-21 10:17:25 Slp: Action
"ConfigEvent_SQL_Replication_Core_Inst_sql_engine_ core_inst_Cpu64_Install_Finalize_finalize"
will return false due to the following conditions:
2009-07-21 10:17:25 Slp: Condition "Feature dependency condition for
action:
ConfigEvent_SQL_Replication_Core_Inst_sql_engine_c ore_inst_Cpu64_Install_Finalize_finalize
The condition tests feature:
SQL_Replication_Core_Inst_sql_engine_core_inst_Cpu 64. There are 3
dependant features. The feature is tested for results: ValidateResult,
Result, CleanupResult." did not pass as it returned false and true was
expected.
2009-07-21 10:17:25 Slp: Condition is false because the required
feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in
result Result
2009-07-21 10:17:25 Slp: Error: Action
"ConfigEvent_SQL_Replication_Core_Inst_sql_engine_ core_inst_Cpu64_Install_Finalize_finalize"
failed during execution.
2009-07-21 10:17:25 Slp: Action
"ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_I nstall_Finalize_finalize"
will return false due to the following conditions:
2009-07-21 10:17:25 Slp: Condition "Feature dependency condition for
action:
ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_In stall_Finalize_finalize
The condition tests feature: SQL_FullText_Adv_sql_fulltext_Cpu64.
There are 3 dependant features. The feature is tested for results:
ValidateResult, Result, CleanupResult." did not pass as it returned
false and true was expected.
2009-07-21 10:17:25 Slp: Condition is false because the required
feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in
result Result
2009-07-21 10:17:25 Slp: Error: Action
"ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_I nstall_Finalize_finalize"
failed during execution.
2009-07-21 10:17:26 Slp: Sco: Attempting to set feature configuration
state Configured for feature SQL_DTS_Full
2009-07-21 10:17:26 Slp: Sco: Attempting to set feature flag
ConfigurationState for machine , feature SQL_DTS_Full

Here are the corresponding entries from the summary log:

Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x1C2074D8@1216@1
Configuration error description: The cluster resource 'SQL Server
(XXXXXXX)' could not be brought online. Error: The resource failed to
come online due to the failure of one or more provider resources.
(Exception from HRESULT: 0x80071736)
Configuration log: C:\Program Files\Microsoft SQL Server
\100\Setup Bootstrap\Log\20090721_091855\Detail.txt

Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x1C2074D8@1216@1
Configuration error description: The cluster resource 'SQL Server
(XXXXXXXX)' could not be brought online. Error: The resource failed
to come online due to the failure of one or more provider resources.
(Exception from HRESULT: 0x80071736)
Configuration log: C:\Program Files\Microsoft SQL Server
\100\Setup Bootstrap\Log\20090721_091855\Detail.txt

Feature: Full-Text Search
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x1C2074D8@1216@1
Configuration error description: The cluster resource 'SQL Server
(XXXXXXX)' could not be brought online. Error: The resource failed to
come online due to the failure of one or more provider resources.
(Exception from HRESULT: 0x80071736)
Configuration log: C:\Program Files\Microsoft SQL Server
\100\Setup Bootstrap\Log\20090721_091855\Detail.txt


If you should have any advice or require any further details to help
me defuse the situation, I'd appreciate the help.

Drew Flint
Plex Systems

Have you confirmed that the cluster proxy account has the rights in AD to
join a computer with the SQL Virtual Server name to the domain? We ran into
this problem because our network group had created a computer with that name
in the domain, but hadn't granted rights to join it to the right account. Our
cluster runs as SQL_Cluster_Proxy (note - not SQL_Proxy, the account the runs
the actual SQL service), and granting rights to this user allowed it to join
the domain successfully.

This is new to SQL 2008/Server 2008, BTW - earlier versions of Windows or
SQL just needed to create the Virtual Server name in DNS - the new versions
actually need to add a machine in AD.

On Jul 22, 11:52*am, Ryan McCauley
<RyanMcCau... (AT) discussions (DOT) microsoft.com> wrote:
Ryan:

Thanks for the suggestion. It's something good to check. If I'm
understanding you correct. The account that the SQL Server Service
runs as has to have rights to add a computer account to the domain. In
our case the Computers OU. I created a test account for the SQL
Server Service that was in the domain admins group for the domain in
question. I then ran the installation and things still failed.
Am I understanding your suggestion correctly? Please advise. I
really do appreciate the suggestion. Thanks again.

Drew Flint
Plex Systems

There are two accounts involved - in your case, they might be one AD account
that does both things, but in ours, it's two different accounts.

On one of the cluster nodes, in the "Services" admin tool, check to see
which account "Cluster Service" is running as. This is the account that will
need rights to add a computer to the domain.

If you check the account "SQL Server (YourInstanceName)" is running as,
that's the SQL Service account. It doesn't need rights to add a computer to
AD (and it shouldn't, since best practices says this account should be least
privileged), but it won't hurt anything if it does.

It's the first account I'm asking about - can that account join a computer
to the domain?

On Jul 23, 6:10*pm, Ryan McCauley
<RyanMcCau... (AT) discussions (DOT) microsoft.com> wrote:

We're using a Windows 2008 Failover Cluster configuration and the
Cluster Service has to run as the local system account or it won't
start properly. That appears to be a best practice for the Windows
2008 Failover Clustering according to some of the posts I've come
across in the Windows 2008 clustering forums. I tried to change the
account the Cluster Service runs as from the local system to a domain
account and it gives the following error:

Error 1297: A privilege that the service requires to function properly
does not exist in the service account configuration. You may use the
Services Microsoft Management Console (MMC) snap-in (services.msc) and
the Local Security Settings MMC snap-in (secpol.msc) to view the
service configuration and the account configuration.

I've been trying to follow the SQL Server 2008 Failover Clustering
white paper that was published June 2009. I found it at this link:

http://blogs.msdn.com/petersad/archi...published.aspx

It doesn't indicate as a pre-requisite that I can find of altering
the Cluster Service to run as a domain account. Perhaps there is
something incorrect in the white paper. The computer account does
appear in AD and the permissions on it appear to inherit that of the
parent OU, which seems proper.
Thanks so much for continuing to help me out. I've done clusters
with Windows 2003 Server and SQL 2005 without incident. I'm having a
difficult time addressing all the differences.

Drew Flint
Plex Systems