Re: Problem: SQL Server 2005 Setup requires administrator permissions on every cluster node

Tech-Archive recommends: Speed Up your PC by fixing your registry


SQLSetup0001_xxxxxx_Core(Local).log

Error: Action "LaunchLocalBootstrapAction" threw an exception during
execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe"
finished and returned: 1602
Aborting queue processing as nested installer has completed
Message pump returning: 1602


Error: Action "InvokeSqlSetupDllAction" failed during execution.
Action "AnalyzeInstallStage" will be skipped due to the following
restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed."
returned false.
Action "PrepareForChainingStage" will be skipped due to the following
restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed."
returned false.
Action "SequenceChainingActionsStage" will be skipped due to the
following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed."
returned false.
Action "InstallChainedPackagesStage" will be skipped due to the
following restrictions:
Condition "Action: InvokeSqlSetupDllAction has finished and passed."
returned false.
Running: ReportChainingResults at: 2009/2/28 20:2:47
Error: Action "ReportChainingResults" threw an exception during
execution.
DwLaunchMsiExec() returned : 1602
Error Code: 0x80070642 (1602)
Windows Error Text: User cancelled installation.

Source File Name: sqlchaining\sqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 2992

Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode"
{"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name:
SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Failed to create CAB file due to datastore exception
Source File Name: datastore\cachedpropertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:49 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "watsonFailedActionErrorCode"
{"SetupStateScope", "", ""} in cache
Source File Name: datastore\propertycollection.cpp
Compiler Timestamp: Fri Jul 29 01:13:50 2005
Function Name:
SetupStateScope.watsonFailedActionErrorCode
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
Message pump returning: 1602


On Sat, 28 Mar 2009 13:36:23 -0400, Bill Golem
<bill_golem_nospam@xxxxxxxxxxx> wrote:

TITLE: Microsoft SQL Server Setup
------------------------------

SQL Server 2005 Setup requires administrator permissions on every
cluster node. To continue, update permissions for the account
currently running Setup, or log in with an account that has
administrator permissions on every cluster node, and then run SQL
Server Setup again.

For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28076

Hello

Setting up a new W2K8 x64 Two Node Cluster A/P. I have the cluster
built and the cluster fails over from node to node with no problems.
Cluster validation passed 100% on all items. I have create a sql
installation account, and added that domain account to the local Admin
group on each node. I have the two installation CD copied to the C
drive on the primary node. When logged in as the installation
account on the second node I can access the installation files.
\\<servername\c$\ I have also changed the local policy on both
nodes and added the sql installation account granting log on as
service and act as part of the operating system rights. Windows
firewall is disabled on both nodes for the installation. I have
looked at the SQL logs but nothing is jumping out at me as to the
cause of the problem.
.

Relevant Pages

  • Re: SQL 2005 Cluster install Error
    ... Source File Name: datastore\cachedpropertycollection.cpp ... then the components installed successfully until "SQL server ... Installation of package: "patchRS2000" failed due to a precondition. ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL Set to System Account - Sharepoint Question
    ... > Administration", not System Account) account. ... > after the installation there isn't normally any reason to ... > SQL, don't use an instance being used for anything else. ... > the App Support people why SA is required. ...
    (microsoft.public.windows.server.sbs)
  • Re: SQLSetup0001_xxxxxx_Core(Local).log
    ... Windows Error Text: User cancelled installation. ... Source File Name: datastore\cachedpropertycollection.cpp ... SQL Server 2005 Setup requires administrator permissions on every ... update permissions for the account ...
    (microsoft.public.sqlserver.clustering)
  • Re: Service Pack 2 Installation Error
    ... This is a clustered installation though I'm not sure my problem is cluster related, so I hope I posted in the right place. ... I started to install SQL Server 2005 SP2. ... I've tried the domain admin account as well as all of the other accounts that are even possibly the correct one, but each time I try, I'm given an error that says. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Failed to modify security permissions on WMI namespace
    ... The account you logged in as has administrator privileges on both nodes. ... AD or the installation account has permission to create them during the ... Here I enclosed a piece of my failed SQL 2005 installation. ... SQL Server Setup failed to modify security permissions on WMI ...
    (microsoft.public.sqlserver.clustering)