dbTalk Databases Forums  

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

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Problem: SQL Server 2005 Setup requires administrator permissions on every cluster node in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Bill Golem
 
Posts: n/a

Default Problem: SQL Server 2005 Setup requires administrator permissions on every cluster node - 03-28-2009 , 11:36 AM






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?LinkI...&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.

Reply With Quote
  #2  
Old   
Bill Golem
 
Posts: n/a

Default Re: SQLSetup0001_xxxxxx_Core(Local).log - 03-28-2009 , 06:58 PM







infor from 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


rror: 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:erform
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 (AT) bwdsb (DOT) on.ca> wrote:

Quote:
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?LinkI...&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.

Reply With Quote
  #3  
Old   
Bill Golem
 
Posts: n/a

Default Re: Problem: SQL Server 2005 Setup requires administrator permissions on every cluster node - 03-28-2009 , 06:58 PM




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:erform
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 (AT) bwdsb (DOT) on.ca> wrote:

Quote:
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?LinkI...&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.

Reply With Quote
  #4  
Old   
Bill
 
Posts: n/a

Default Re: Problem: Fixed SQL Server 2005 Setup - 04-01-2009 , 09:21 AM




FYI

I was able to resolve my problem by stopping the Terminal Services
service on each node and using the <domain>\Administrator account. An
domain user account with local admin rights wasn't enough nor was an
account with domain rights.

I also noticed that during the SQL 2005 installation I didn't get the
warning about requiring SQL SP2 for support on Windows 2008. I did
get later during the install the warning about needing to apply SP1
for VS 2005.

Hope this helps someone else that was in the same boat as me.

Bill

On Sat, 28 Mar 2009 13:36:23 -0400, Bill Golem
<bill_golem_nospam (AT) bwdsb (DOT) on.ca> wrote:

Quote:
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?LinkI...&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.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.