|
Home > Archive > MS SQL Server Clustering > December 2005 > 2005 Cluster Install Error
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
2005 Cluster Install Error
|
|
|
| I'm having problems installing 2005 Ent on my Win 2003 SP1 2 node cluster.
Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
installed. I would like to run them side by side.
installing using the setup wizard I get error about the schedule task
failing to start on the 2nd node. Looking through the log files the setup
program on the 2nd node has thrown an exception error, core.log shows this:
Complete: ParseBootstrapOption
sAction at: 2005/10/7 13:25:6, returned false
Error: Action " ParseBootstrapOption
sAction" failed during execution. Error
information reported during run:
Could not decrypt command line due to WinException.
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpa
ssword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword:
:UnprotectString
Source Line Number: 311
Running: ValidateWinNTAction at: 2005/10/7 13:25:6
Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
Running: ValidateMinOSAction at: 2005/10/7 13:25:6
Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
Running: PerformSCCAction at: 2005/10/7 13:25:6
Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
Running: ActivateLoggingActio
n at: 2005/10/7 13:25:6
Error: Action " ActivateLoggingActio
n" threw an exception during execution.
Error information reported during run:
00D7CFC8Unable to proceed with setup, there was a command line parsing
error. : -2146893822
Error Code: -2146893822
Windows Error Text: Bad Hash.
Source File Name: cryptohelper\cryptpa
ssword.cpp
Compiler Timestamp: Mon Jul 18 01:10:20 2005
Function Name: sqls::CryptPassword:
:UnprotectString
Source Line Number: 311
Delay load of action " UploadDrWatsonLogAct
ion" returned nothing. No action
will occur as a result.
Message pump returning: 2148073474
-------- END OF OUTPUT ---------------------
I've trying to work around it I have tried installing from the command line.
This gets much further with setup starting correctly on both nodes. I get as
far as installing the actual SQL Server Service instance then I'm thrown an
error. Summary.log shows:
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
--------------------------------------------------------------------------------
Machine : SERVERA
Product : SQL Server Database Services
Error : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
--------------------------------------------------------------------------------
Machine : SERVERA
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\
SQLSetup0014_LON-IMS01A_SQL.log
Last Action : Validate_ServiceAcco
unts
Error String : A domain group is missing for one or more services. To
install SQL Server 2005 as a failover cluster, domain groups must be
specified for all the clustered services being installed .To proceed, enter
the missing domain group information.
The domain group cannot be validated for the service SQL Server.
Error Number : 28130
--- END OF OUTPUT
In the GUI you get asked for Domain Groups for each service, the
documentation for the command line installer doesn't tell me what the
parameters are for this. Do I need them, is the documentation missing
something?? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
I'm putting in my domain password currently - again teh documentation isn't
too hot for this.
I'm running out of ideas. If anyone has any suggestions please let me know!
Thanks
| |
|
| I figured out the problem to the command line - why the GUI crashed I do not
know.
BOL does not document any of these parameters for the command line which are
REQUIRED for a cluster install:
SQLBROWSERACCOUNT="DOMAIN\USER"
SQLBROWSERPASSWORD="PASSWORD"
SQLCLUSTERGROUP="DOMAIN\GROUP"
AGTCLUSTERGROUP="DOMAIN\GROUP"
FTSCLUSTERGROUP="DOMAIN\GROUP"
However if you look in the template.ini file on your install cd you will
find details of how and when to use them.
A very dissapointed customer.
"Simon" wrote:
> I'm having problems installing 2005 Ent on my Win 2003 SP1 2 node cluster.
> Please note this cluster has a SQL 2000 (SP4) virtual server/instance already
> installed. I would like to run them side by side.
>
> installing using the setup wizard I get error about the schedule task
> failing to start on the 2nd node. Looking through the log files the setup
> program on the 2nd node has thrown an exception error, core.log shows this:
>
> Complete: ParseBootstrapOption
sAction at: 2005/10/7 13:25:6, returned false
> Error: Action " ParseBootstrapOption
sAction" failed during execution. Error
> information reported during run:
> Could not decrypt command line due to WinException.
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
>
> Source File Name: cryptohelper\cryptpa
ssword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword:
:UnprotectString
> Source Line Number: 311
>
> Running: ValidateWinNTAction at: 2005/10/7 13:25:6
> Complete: ValidateWinNTAction at: 2005/10/7 13:25:6, returned true
> Running: ValidateMinOSAction at: 2005/10/7 13:25:6
> Complete: ValidateMinOSAction at: 2005/10/7 13:25:6, returned true
> Running: PerformSCCAction at: 2005/10/7 13:25:6
> Complete: PerformSCCAction at: 2005/10/7 13:25:6, returned true
> Running: ActivateLoggingActio
n at: 2005/10/7 13:25:6
> Error: Action " ActivateLoggingActio
n" threw an exception during execution.
> Error information reported during run:
> 00D7CFC8Unable to proceed with setup, there was a command line parsing
> error. : -2146893822
> Error Code: -2146893822
> Windows Error Text: Bad Hash.
>
> Source File Name: cryptohelper\cryptpa
ssword.cpp
> Compiler Timestamp: Mon Jul 18 01:10:20 2005
> Function Name: sqls::CryptPassword:
:UnprotectString
> Source Line Number: 311
>
> Delay load of action " UploadDrWatsonLogAct
ion" returned nothing. No action
> will occur as a result.
> Message pump returning: 2148073474
>
>
> -------- END OF OUTPUT ---------------------
>
>
> I've trying to work around it I have tried installing from the command line.
> This gets much further with setup starting correctly on both nodes. I get as
> far as installing the actual SQL Server Service instance then I'm thrown an
> error. Summary.log shows:
>
>
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> --------------------------------------------------------------------------------
> Machine : SERVERA
> Product : SQL Server Database Services
> Error : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> --------------------------------------------------------------------------------
> Machine : SERVERA
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\
SQLSetup0014_LON-IMS01A_SQL.log
> Last Action : Validate_ServiceAcco
unts
> Error String : A domain group is missing for one or more services. To
> install SQL Server 2005 as a failover cluster, domain groups must be
> specified for all the clustered services being installed .To proceed, enter
> the missing domain group information.
> The domain group cannot be validated for the service SQL Server.
> Error Number : 28130
>
>
> --- END OF OUTPUT
>
>
> In the GUI you get asked for Domain Groups for each service, the
> documentation for the command line installer doesn't tell me what the
> parameters are for this. Do I need them, is the documentation missing
> something?? Also I'm not too sure what the ADMINPASSWORD= paramater is for -
> I'm putting in my domain password currently - again teh documentation isn't
> too hot for this.
>
> I'm running out of ideas. If anyone has any suggestions please let me know!
>
> Thanks
>
| |
| Andy Ball 2005-11-12, 3:23 am |
| Simon,
yep I noticed that too. Just an omission in BOL. I sent feedback via the BOL
entry for installing a Cluster from template/unattend, suggest you do the
same.
Andy.
"Simon" <Simon@discussions.microsoft.com> wrote in message
news:ECC70F54-2E3D-43BE-AE8B- 5B91EFC74E60@microso
ft.com...[color=darkred]
>I figured out the problem to the command line - why the GUI crashed I do
>not
> know.
>
> BOL does not document any of these parameters for the command line which
> are
> REQUIRED for a cluster install:
>
> SQLBROWSERACCOUNT="DOMAIN\USER"
> SQLBROWSERPASSWORD="PASSWORD"
>
> SQLCLUSTERGROUP="DOMAIN\GROUP"
> AGTCLUSTERGROUP="DOMAIN\GROUP"
> FTSCLUSTERGROUP="DOMAIN\GROUP"
>
> However if you look in the template.ini file on your install cd you will
> find details of how and when to use them.
>
> A very dissapointed customer.
>
>
>
>
> "Simon" wrote:
>
| |
| Anthony Thomas 2005-11-13, 1:23 pm |
| That information is in the Readme notes as well as the Readme errata posted
online.
ALWAYS READ THE README.
Anthony Thomas
--
"Andy Ball" < ng@spamno77greenfell
.com> wrote in message
news:u%23k3gf05FHA.3976@TK2MSFTNGP15.phx.gbl...
> Simon,
>
> yep I noticed that too. Just an omission in BOL. I sent feedback via the
BOL
> entry for installing a Cluster from template/unattend, suggest you do the
> same.
>
> Andy.
> "Simon" <Simon@discussions.microsoft.com> wrote in message
> news:ECC70F54-2E3D-43BE-AE8B- 5B91EFC74E60@microso
ft.com...
setup[color=darkred]
get[color=darkred]
thrown[color=darkred
]
To[color=darkred]
>
-------[color=darkred]
To[color=darkred]
>
-------[color=darkred]
To[color=darkred]
>
>
| |
| Andy Ball 2005-11-14, 8:24 pm |
| must be going blind - i'm looking @ ReadmeSQL2005.htm from the Dev \ MSDN
edition and Q907284 I can't see it
Andy.
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:OaT56MI6FHA.1184@TK2MSFTNGP12.phx.gbl...
> That information is in the Readme notes as well as the Readme errata
> posted
> online.
>
> ALWAYS READ THE README.
>
>
> Anthony Thomas
>
>
> --
>
> "Andy Ball" < ng@spamno77greenfell
.com> wrote in message
> news:u%23k3gf05FHA.3976@TK2MSFTNGP15.phx.gbl...
[color=darkred]
> BOL
> setup
> get
> thrown
> To
> -------
> To
> -------
> To
>
>
| |
| Anthony Thomas 2005-11-15, 1:23 pm |
| At the time, this seemed clearer, but it appears you are speaking of
something else. There is also the Setupsql9.chm file that is seperate from
the BOL. You are right; it is unclear.
Microsoft SQL Server September 2005 Community Technology Preview
http://download.microsoft.com/downl...ion_
cuy1
3.5.15 Corrections to the Names of Security Groups Created During Setup
During setup, SQL Server 2005 adds the following security groups to Windows:
SQLServer2005DTSUser
$ComputerName
SQLServer2005MSFTEUs
er$ComputerName$Inst
anceName
SQLServer2005MSOLAPU
ser$ComputerName$Ins
tanceName
SQLServer2005MSSQLSe
rverADHelperUser$Com
puterName
SQLServer2005MSSQLUs
er$ComputerName$Inst
anceName
SQLServer2005Notific
ationServicesUser$Co
mputerName
SQLServer2005Reporti
ngServicesWebService
User$ComputerName$In
stanceName
SQLServer2005ReportS
erverUser$ComputerNa
me$InstanceName
SQLServer2005SQLAgen
tUser$ComputerName$I
nstanceName
SQLServer2005SQLBrow
serUser$ComputerName
These groups simplify granting permissions required to run SQL Server
Windows services and other executables. They also help secure SQL Server
files.
In SQL Server Books Online, $ComputerName was omitted from the names. The
computer name has since been added to the group names to uniquely identify
each group. Unique group names are necessary if SQL Server 2005 is installed
on domain controllers. For all references to security groups that start with
"SQLServer2005," substitute the appropriate group name listed above.
3.5.17 Restrictions for Service Accounts on a Failover Cluster
SQL Server service, SQL Server Agent service, Analysis Services service, and
Full-Text Search service must run as domain accounts that are members of the
built-in Administrators group on each node of the cluster.
Sincerely,
Anthony Thomas
--
"Andy Ball" < ng@spamno77greenfell
.com> wrote in message
news:uEuMBdV6FHA.1000@tk2msftngp13.phx.gbl...
> must be going blind - i'm looking @ ReadmeSQL2005.htm from the Dev \ MSDN
> edition and Q907284 I can't see it
>
> Andy.
>
> "Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
> news:OaT56MI6FHA.1184@TK2MSFTNGP12.phx.gbl...
>
>
>
the[color=darkred]
the[color=darkred]
do[color=darkred]
server/ instance[color=darkr
ed]
task[color=darkred]
shows[color=darkred]
returned[color=darkr
ed]
parsing[color=darkre
d]
command[color=darkre
d]
I[color=darkred]
services.[color=darkred]
proceed,[color=darkr
ed]
>
-[color=darkred]
services.[color=darkred]
proceed,[color=darkr
ed]
>
-[color=darkred]
services.[color=darkred]
proceed,[color=darkr
ed]
the[color=darkred]
missing[color=darkre
d]
documentation[color=
darkred]
me[color=darkred]
>
>
| |
| Anthony Thomas 2005-11-16, 1:23 pm |
| From the Setupsql9.chm, regarding your original issue:
How to: Install SQL Server 2005 from the Command Prompt
For failover cluster installations, you must be a local administrator with
permissions to logon as a service, and to act as part of the operating
system on all nodes of the virtual server.
start /wait setup.exe /qn VS=<VSName> INSTALLVS=Analysis_S
erver
INSTANCENAME=<InstanceName> ADDLOCAL=Analysis_Se
rver ADDNODE=n
GROUP=<NotSQLDiskGroup> IP=<IP,Networkname> ADMINPASSWORD=<StrongPassword>
SAPWD=<StrongPassword> INSTALLSQLDIR=<InstallationPath>
INSTALLSQLDATADIR=<ShareDrivePath> ASACCOUNT=<domain\user>
ASPASSWORD=<DomainUserPassword> SQLBROWSERACCOUNT=<domain\user>
SQLBROWSERPASSWORD=<DomainUserPassword> SQLREPORTING=1
Start /wait <DVD Drive>\setup.exe /qn VS=<VSName> INSTALLVS=SQL_Engine
INSTANCENAME=<InstanceName> ADDLOCAL=SQL_Engine,
Client_Components
ADDNODE=<NodeName1,NodeName2> GROUP=<Diskgroup> IP=<IP,Networkname>
ADMINPASSWORD=<StrongPassword> SAPWD=<StrongPassord>
INSTALLSQLDIR=<InstallationPath> INSTALLSQLDATADIR=<ShareDrivePath>
SQLACCOUNT=<domain\user> SQLPASSWORD=<DomainUserPassword>
AGTACCOUNT=<domain\user> AGTPASSWORD=<DomainUserPassword>
The same holds true for the other components.
Sincerely,
Anthony Thomas
--
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
from
> the BOL. You are right; it is unclear.
>
> Microsoft SQL Server September 2005 Community Technology Preview
>
http://download.microsoft.com/downl...ion_
cuy1
>
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
Windows:
> SQLServer2005DTSUser
$ComputerName
>
> SQLServer2005MSFTEUs
er$ComputerName$Inst
anceName
>
> SQLServer2005MSOLAPU
ser$ComputerName$Ins
tanceName
>
> SQLServer2005MSSQLSe
rverADHelperUser$Com
puterName
>
> SQLServer2005MSSQLUs
er$ComputerName$Inst
anceName
>
> SQLServer2005Notific
ationServicesUser$Co
mputerName
>
> SQLServer2005Reporti
ngServicesWebService
User$ComputerName$In
stanceName
>
> SQLServer2005ReportS
erverUser$ComputerNa
me$InstanceName
>
> SQLServer2005SQLAgen
tUser$ComputerName$I
nstanceName
>
> SQLServer2005SQLBrow
serUser$ComputerName
>
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
installed
> on domain controllers. For all references to security groups that start
with
> "SQLServer2005," substitute the appropriate group name listed above.
>
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
and
> Full-Text Search service must run as domain accounts that are members of
the
> built-in Administrators group on each node of the cluster.
>
>
> Sincerely,
>
>
> Anthony Thomas
>
> --
>
> "Andy Ball" < ng@spamno77greenfell
.com> wrote in message
> news:uEuMBdV6FHA.1000@tk2msftngp13.phx.gbl...
MSDN[color=darkred]
> the
> the
I[color=darkred]
> do
> server/instance
> task
the[color=darkred]
> shows
> returned
execution.[color=darkred]
> parsing
No[color=darkred]
> command
nodes.[color=darkred]
> I
> services.
be[color=darkred]
> proceed,
>
> -
> services.
be[color=darkred]
> proceed,
>
> -
> services.
be[color=darkred]
> proceed,
> the
> missing
paramater[color=dark
red]
> documentation
> me
>
>
| |
| Andy Ball 2005-11-16, 8:24 pm |
| and the portion I presume is talking about the Local Groups that created on
the Server where SQL is installed. Simon's original post is about the DOMAIN
local groups that are required for Clustering.
cheers,
Andy.
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:eETZ86g6FHA.1000@tk2msftngp13.phx.gbl...
> At the time, this seemed clearer, but it appears you are speaking of
> something else. There is also the Setupsql9.chm file that is seperate
> from
> the BOL. You are right; it is unclear.
>
> Microsoft SQL Server September 2005 Community Technology Preview
> http://download.microsoft.com/downl...ion_
cuy1
>
> 3.5.15 Corrections to the Names of Security Groups Created During Setup
> During setup, SQL Server 2005 adds the following security groups to
> Windows:
> SQLServer2005DTSUser
$ComputerName
>
> SQLServer2005MSFTEUs
er$ComputerName$Inst
anceName
>
> SQLServer2005MSOLAPU
ser$ComputerName$Ins
tanceName
>
> SQLServer2005MSSQLSe
rverADHelperUser$Com
puterName
>
> SQLServer2005MSSQLUs
er$ComputerName$Inst
anceName
>
> SQLServer2005Notific
ationServicesUser$Co
mputerName
>
> SQLServer2005Reporti
ngServicesWebService
User$ComputerName$In
stanceName
>
> SQLServer2005ReportS
erverUser$ComputerNa
me$InstanceName
>
> SQLServer2005SQLAgen
tUser$ComputerName$I
nstanceName
>
> SQLServer2005SQLBrow
serUser$ComputerName
>
> These groups simplify granting permissions required to run SQL Server
> Windows services and other executables. They also help secure SQL Server
> files.
> In SQL Server Books Online, $ComputerName was omitted from the names. The
> computer name has since been added to the group names to uniquely identify
> each group. Unique group names are necessary if SQL Server 2005 is
> installed
> on domain controllers. For all references to security groups that start
> with
> "SQLServer2005," substitute the appropriate group name listed above.
>
> 3.5.17 Restrictions for Service Accounts on a Failover Cluster
> SQL Server service, SQL Server Agent service, Analysis Services service,
> and
> Full-Text Search service must run as domain accounts that are members of
> the
> built-in Administrators group on each node of the cluster.
>
>
> Sincerely,
>
>
> Anthony Thomas
>
> --
>
> "Andy Ball" < ng@spamno77greenfell
.com> wrote in message
> news:uEuMBdV6FHA.1000@tk2msftngp13.phx.gbl...
> the
> the
> do
> server/instance
> task
> shows
> returned
> parsing
> command
> I
> services.
> proceed,
> -
> services.
> proceed,
> -
> services.
> proceed,
> the
> missing
> documentation
> me
>
>
| |
| Anthony Thomas 2005-11-16, 8:24 pm |
| Yea, I saw that and it didn't make sense. There is no such thing as "DOMAIN
local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
Resource groups, and, apparently, SQL Server 2005 security groups.
However, there is a new requirement that not only does the Installation
Administrator need Local Administrators group membership but also the ACT AS
PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
installations that probably caused the initial issue to begin with.
Sincerely,
Anthony Thomas
--
"Andy Ball" < ng@spamno77greenfell
.com> wrote in message
news:O$aRRzw6FHA.808@TK2MSFTNGP09.phx.gbl...
> and the portion I presume is talking about the Local Groups that created
on
> the Server where SQL is installed. Simon's original post is about the
DOMAIN
> local groups that are required for Clustering.
>
> cheers,
> Andy.
> "Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
> news:eETZ86g6FHA.1000@tk2msftngp13.phx.gbl...
http://download.microsoft.com/downl...ion_
cuy1[color=darkred]
The[color=darkred]
identify[color=darkr
ed]
MSDN[color=darkred]
do[color=darkred]
I[color=darkred]
you[color=darkred]
the[color=darkred]
true[color=darkred]
true[color=darkred]
No[color=darkred]
nodes.[color=darkred]
>
-[color=darkred]
>
-[color=darkred]
let[color=darkred]
>
>
| |
| Andy Ball 2005-11-17, 3:24 am |
| Domain Local Groups were introduced in Windows 2000 Active Directory
cheers
Andy.
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:exXVCFx6FHA.3276@TK2MSFTNGP10.phx.gbl...
> Yea, I saw that and it didn't make sense. There is no such thing as
> "DOMAIN
> local groups." There are DOMAIN Global groups, LOCAL groups, Cluster
> Resource groups, and, apparently, SQL Server 2005 security groups.
>
> However, there is a new requirement that not only does the Installation
> Administrator need Local Administrators group membership but also the ACT
> AS
> PART OF THE OPERATING SYSTEM User Security rights assignment for clustered
> installations that probably caused the initial issue to begin with.
>
> Sincerely,
>
>
> Anthony Thomas
>
>
> --
>
> "Andy Ball" < ng@spamno77greenfell
.com> wrote in message
> news:O$aRRzw6FHA.808@TK2MSFTNGP09.phx.gbl...
> on
> DOMAIN
> http://download.microsoft.com/downl...ion_
cuy1
> The
> identify
> MSDN
> do
> I
> you
> the
> true
> true
> No
> nodes.
> -
> -
> let
>
>
| |
| Anthony Thomas 2005-11-17, 9:23 am |
| Ok, there is a difference between Universal, Global, and Local Domain
Groups. However, if you have a Single Forest, Single Domain model, they are
equivalent.
But, then, the installer would also need AD permission to create these
Domain Local Groups in addition to the membership in the Machine Local
Administrators Group and Act as part of the Operating System User Access
Right.
I am still suspect on whether or not this is a Security Group or Cluster
Resource Group requirement.
I can see the need to promote Machine Local Groups to Domain Local Groups
when we are talking about clusters because the level of scope. But then
again that would require a higher level of privilege.
If true, then I would most certainly agree that the documentation is Grossly
lacking.
Sincerely,
Anthony Thomas
--
"Andy Ball" < ng@spamno77greenfell
.com> wrote in message
news:eN8B5k06FHA.1724@TK2MSFTNGP10.phx.gbl...
> Domain Local Groups were introduced in Windows 2000 Active Directory
>
> cheers
> Andy.
>
> "Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
> news:exXVCFx6FHA.3276@TK2MSFTNGP10.phx.gbl...
ACT[color=darkred]
clustered[color=dark
red]
created[color=darkre
d]
seperate[color=darkr
ed]
http://download.microsoft.com/downl...ion_
cuy1[color=darkred]
Setup[color=darkred]
SQLServer2005Reporti
ngServicesWebService
User$ComputerName$In
stanceName[color=dar
kred]
start[color=darkred]
errata[color=darkred
]
you[color=darkred]
schedule[color=darkr
ed]
files[color=darkred]
core.log[color=darkred]
true[color=darkred]
during[color=darkred
]
nothing.[color=darkred]
Server.[color=darkred]
>
-[color=darkred]
Server.[color=darkred]
>
-[color=darkred]
Server\90\Setup[colo
r=darkred]
Server.[color=darkred]
the[color=darkred]
>
>
| |
| Anthony Thomas 2005-11-18, 3:23 am |
| Fine. Time to bite the bullet on that one.
I dug around on my own and the both of you are absolutely right. God, I
hate that, but how else do you learn.
Thanks for bringing it to everyone's attention, and for helping me see
through my own pig-headedness.
For what it is worth, I've been trying to follow the "Best Practices"
solution of creating machine local groups to which I add Domain Global
Groups for years to provide as much resource isolation as possible, but for
clusters, that's a bit tricky and redundant. With the use of Domain Local
Groups, this makes it easier.
So, in short, I'm glad for the change; however, you are both absolutely
right in that the documentation totally sucks in this case. It makes sense,
given they do document the machine local groups as SQL Server security
groups and promoting them for clustered installations, but it sure would
have been nice to have noted that somewhere else other than the very last
paragraph in the template.ini.
Thanks again.
Sincerely,
Anthony Thomas
--
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:euSltp36FHA.1020@TK2MSFTNGP15.phx.gbl...
> Ok, there is a difference between Universal, Global, and Local Domain
> Groups. However, if you have a Single Forest, Single Domain model, they
are
> equivalent.
>
> But, then, the installer would also need AD permission to create these
> Domain Local Groups in addition to the membership in the Machine Local
> Administrators Group and Act as part of the Operating System User Access
> Right.
>
> I am still suspect on whether or not this is a Security Group or Cluster
> Resource Group requirement.
>
> I can see the need to promote Machine Local Groups to Domain Local Groups
> when we are talking about clusters because the level of scope. But then
> again that would require a higher level of privilege.
>
> If true, then I would most certainly agree that the documentation is
Grossly
> lacking.
>
> Sincerely,
>
>
> Anthony Thomas
>
> --
>
> "Andy Ball" < ng@spamno77greenfell
.com> wrote in message
> news:eN8B5k06FHA.1724@TK2MSFTNGP10.phx.gbl...
Installation[color=d
arkred]
> ACT
> clustered
> created
of[color=darkred]
> seperate
>
http://download.microsoft.com/downl...ion_
cuy1
> Setup
> SQLServer2005Reporti
ngServicesWebService
User$ComputerName$In
stanceName
Server[color=darkred
]
names.[color=darkred]
> start
above.[color=darkred]
members[color=darkre
d]
\[color=darkred]
> errata
feedback[color=darkr
ed]
> you
cd[color=darkred]
> schedule
> files
> core.log
returned[color=darkr
ed]
returned[color=darkr
ed]
> true
> during
line[color=darkred]
> nothing.
the[color=darkred]
then[color=darkred]
> Server.
>
> -
> Server.
>
> -
> Server\90\Setup
> Server.
> the
documentation[color=
darkred]
please[color=darkred
]
>
>
| |
| Geoff N. Hiten 2005-11-18, 7:23 am |
| You aren't the only one to notice the documentation is less than stellar.
And you are also correct in that domain-level security groups is the correct
way to manage security for SQL service accounts, clustered or not. And
finally, you aren't the first "expert" to make a mistake in public. That is
what makes a community forum so great. If you screw up, you will get called
on it. :)
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:umeUHd$6FHA.1188@TK2MSFTNGP12.phx.gbl...
> Fine. Time to bite the bullet on that one.
>
> I dug around on my own and the both of you are absolutely right. God, I
> hate that, but how else do you learn.
>
> Thanks for bringing it to everyone's attention, and for helping me see
> through my own pig-headedness.
>
> For what it is worth, I've been trying to follow the "Best Practices"
> solution of creating machine local groups to which I add Domain Global
> Groups for years to provide as much resource isolation as possible, but
> for
> clusters, that's a bit tricky and redundant. With the use of Domain Local
> Groups, this makes it easier.
>
> So, in short, I'm glad for the change; however, you are both absolutely
> right in that the documentation totally sucks in this case. It makes
> sense,
> given they do document the machine local groups as SQL Server security
> groups and promoting them for clustered installations, but it sure would
> have been nice to have noted that somewhere else other than the very last
> paragraph in the template.ini.
>
> Thanks again.
>
> Sincerely,
>
>
> Anthony Thomas
>
>
> --
>
> "Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
> news:euSltp36FHA.1020@TK2MSFTNGP15.phx.gbl...
> are
> Grossly
> Installation
> of
> http://download.microsoft.com/downl...ion_
cuy1
> Server
> names.
> above.
> members
> \
> feedback
> cd
> returned
> returned
> line
> the
> then
> documentation
> please
>
>
| |
| Andy Ball 2005-11-18, 7:23 am |
| Respect :-)
I did see somewhere about a December 2005 refresh BOL that will have the
process detailed.
cheers,
Andy.
"Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
news:umeUHd$6FHA.1188@TK2MSFTNGP12.phx.gbl...
> Fine. Time to bite the bullet on that one.
>
> I dug around on my own and the both of you are absolutely right. God, I
> hate that, but how else do you learn.
>
> Thanks for bringing it to everyone's attention, and for helping me see
> through my own pig-headedness.
>
> For what it is worth, I've been trying to follow the "Best Practices"
> solution of creating machine local groups to which I add Domain Global
> Groups for years to provide as much resource isolation as possible, but
> for
> clusters, that's a bit tricky and redundant. With the use of Domain Local
> Groups, this makes it easier.
>
> So, in short, I'm glad for the change; however, you are both absolutely
> right in that the documentation totally sucks in this case. It makes
> sense,
> given they do document the machine local groups as SQL Server security
> groups and promoting them for clustered installations, but it sure would
> have been nice to have noted that somewhere else other than the very last
> paragraph in the template.ini.
>
> Thanks again.
>
> Sincerely,
>
>
> Anthony Thomas
>
>
> --
>
> "Anthony Thomas" <ALThomas@kc.rr.com> wrote in message
> news:euSltp36FHA.1020@TK2MSFTNGP15.phx.gbl...
> are
> Grossly
> Installation
> of
> http://download.microsoft.com/downl...ion_
cuy1
> Server
> names.
> above.
> members
> \
> feedback
> cd
> returned
> returned
> line
> the
> then
> documentation
> please
>
>
| |
|
| I am getting the same error (can't start the scheduled job on the
remote node due to a permission error) while trying to install SQL 2005
Analysis Services on a 2 node cluster. I actually have SQL 05 already
installed on the cluster... It had the same problem but after trying
the install 3 or 4 times it eventually worked. The Analysis services
install just wont start on the remote nide.
Any ideas all?
Thanks,
Jiles
|
|
|
|
|