Domain Admin

This is a quick one: does the domain account that is installing SQL Server on
a cluster need to also be a domain administrator? If it weren't, would that
cause the SQL insatall to fail?
Thanks again!
NO!!!!! Make it a Domain User only, then add it to the local Administrators
group on each node.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:EDBD5BC8-5C0F-4DEF-AE89-F1FDB069C4F3@.microsoft.com...
> This is a quick one: does the domain account that is installing SQL Server
> on
> a cluster need to also be a domain administrator? If it weren't, would
> that
> cause the SQL insatall to fail?
> Thanks again!
>
|||Didn't think so...I now have no idea what's going on with this install.
I'm getting a PATH SPECIFIED IN COMMAND IS NOT VALID:
\\HMS10NK03\ADMIN$\HMS10NK03_MSSQLSERVER.ISS That file doesn't exist in the
directory anywhere...
That path is just the Windows directory. The user I'm installing under is a
local admin and also has explicit rights to the directory/share.
The install goes for about 20-30 minutews and then get the infamous CAN'T
PERFORM OPERATIONS ON CLUSTER (whatever). When I go out to the Windows
directory, there's no SQLSTP.LOG file at all!!
We're not utilizing MSDTC anywhere so I didn't bother setting up a
group/resource for it. All communications between nodes/shared disks are good.
If anyone can shed any light, I would really appreciate it. If logs would
help, let me know which ones should be looked at (there aren't a whole lot to
choose from). I've included the SETUP.ISS
[InstallShield Silent]
Version=v5.00.000
File=Response File
[File Transfer]
OverwriteReadOnly=NoToAll
[DlgOrder]
Dlg0=SdWelcome-0
Count=19
Dlg1=DlgMachine-0
Dlg2=DlgInstallMode-0
Dlg3=SdRegisterUser-0
Dlg4=SdLicense-0
Dlg5=DlgVirtServer-0
Dlg6=DlgDiskGroups-0
Dlg7=DlgClusterDef-0
Dlg8=DlgAccount-0
Dlg9=DlgClientServer-0
Dlg10=DlgInstanceName-0
Dlg11=SetupTypeSQL-0
Dlg12=SdRemoteInfo-0
Dlg13=DlgServices-0
Dlg14=DlgSQLSecurity-0
Dlg15=DlgCollation-0
Dlg16=DlgServerNetwork-0
Dlg17=SdStartCopy-0
Dlg18=SdFinish-0
[SdWelcome-0]
Result=1
[DlgMachine-0]
Name=HMS10NK04
Type=268435466
Result=1
[DlgInstallMode-0]
Type=1
Result=1
[SdRegisterUser-0]
szName=Hoffman
Result=1
[SdLicense-0]
Result=1
[DlgVirtServer-0]
VirtServerName=HMS10NK04
IpAddresses=10.150.128.114,255.255.255.0,Public - 10.150.128.112
Result=0
[DlgDiskGroups-0]
GroupName=SQLServer
Result=1
[DlgClusterDef-0]
VirtServerName=HMS10NK04
nNumNodes=2
Result=1
ClusterPrefOwners=HMS10NK03,HMS10NK02
[DlgAccount-0]
Domain=HOFFMAN
DomainAcct=MSOCLUSTER
DomainPwd=154526877651e5de852d536c6f8f0889
Result=1
[DlgClientServer-0]
Type=2
Result=1
[DlgInstanceName-0]
InstanceName=MSSQLSERVER
Result=1
[SetupTypeSQL-0]
szDir=C:\Program Files\Microsoft SQL Server
Result=301
szDataDir=S:\Program Files\Microsoft SQL Server
SharedDataDir=S:\Program Files\Microsoft SQL Server
[SdRemoteInfo-0]
svEdit1=MSOCLUSTER
svEdit2=154526877651e5de852d536c6f8f0889
svEdit3=HOFFMAN
svEdit4=HMS10NK04
svEdit5=\\HMS10NK04\C$\Program Files\Microsoft SQL Server
svEdit6=\\HMS10NK03\Z$\x86\setup\
Result=1
[DlgServices-0]
Local-Domain=61680
AutoStart=0
SQLDomain=HOFFMAN
SQLDomainAcct=MSOCLUSTER
SQLDomainPwd=154526877651e5de852d536c6f8f0889
AgtDomain=HOFFMAN
AgtDomainAcct=MSOCLUSTER
AgtDomainPwd=154526877651e5de852d536c6f8f0889
Result=1
[DlgSQLSecurity-0]
LoginMode=2
szPwd=086483159a17f2fb6d
Result=1
[DlgCollation-0]
collation_name=SQL_Latin1_General_CP1_CI_AS
Result=1
[DlgServerNetwork-0]
NetworkLibs=255
TCPPort=1433
TCPPrxy=Default
NMPPipeName=\\.\pipe\sql\query
Result=1
[SdStartCopy-0]
Result=1
[License]
LicenseMode=PERDEVICE
LicenseLimit=4
[SdFinish-0]
Result=1
bOpt1=0
bOpt2=0
"Rodney R. Fournier [MVP]" wrote:

> NO!!!!! Make it a Domain User only, then add it to the local Administrators
> group on each node.
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:EDBD5BC8-5C0F-4DEF-AE89-F1FDB069C4F3@.microsoft.com...
>
>
|||Have your tried copying the SQL install files locally and running from
there?
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:C606061F-CB5E-48AF-A1D8-81E6F2FFF01F@.microsoft.com...[vbcol=seagreen]
> Didn't think so...I now have no idea what's going on with this install.
> I'm getting a PATH SPECIFIED IN COMMAND IS NOT VALID:
> \\HMS10NK03\ADMIN$\HMS10NK03_MSSQLSERVER.ISS That file doesn't exist in
> the
> directory anywhere...
> That path is just the Windows directory. The user I'm installing under is
> a
> local admin and also has explicit rights to the directory/share.
> The install goes for about 20-30 minutews and then get the infamous CAN'T
> PERFORM OPERATIONS ON CLUSTER (whatever). When I go out to the Windows
> directory, there's no SQLSTP.LOG file at all!!
> We're not utilizing MSDTC anywhere so I didn't bother setting up a
> group/resource for it. All communications between nodes/shared disks are
> good.
> If anyone can shed any light, I would really appreciate it. If logs would
> help, let me know which ones should be looked at (there aren't a whole lot
> to
> choose from). I've included the SETUP.ISS
> [InstallShield Silent]
> Version=v5.00.000
> File=Response File
> [File Transfer]
> OverwriteReadOnly=NoToAll
> [DlgOrder]
> Dlg0=SdWelcome-0
> Count=19
> Dlg1=DlgMachine-0
> Dlg2=DlgInstallMode-0
> Dlg3=SdRegisterUser-0
> Dlg4=SdLicense-0
> Dlg5=DlgVirtServer-0
> Dlg6=DlgDiskGroups-0
> Dlg7=DlgClusterDef-0
> Dlg8=DlgAccount-0
> Dlg9=DlgClientServer-0
> Dlg10=DlgInstanceName-0
> Dlg11=SetupTypeSQL-0
> Dlg12=SdRemoteInfo-0
> Dlg13=DlgServices-0
> Dlg14=DlgSQLSecurity-0
> Dlg15=DlgCollation-0
> Dlg16=DlgServerNetwork-0
> Dlg17=SdStartCopy-0
> Dlg18=SdFinish-0
> [SdWelcome-0]
> Result=1
> [DlgMachine-0]
> Name=HMS10NK04
> Type=268435466
> Result=1
> [DlgInstallMode-0]
> Type=1
> Result=1
> [SdRegisterUser-0]
> szName=Hoffman
> Result=1
> [SdLicense-0]
> Result=1
> [DlgVirtServer-0]
> VirtServerName=HMS10NK04
> IpAddresses=10.150.128.114,255.255.255.0,Public - 10.150.128.112
> Result=0
> [DlgDiskGroups-0]
> GroupName=SQLServer
> Result=1
> [DlgClusterDef-0]
> VirtServerName=HMS10NK04
> nNumNodes=2
> Result=1
> ClusterPrefOwners=HMS10NK03,HMS10NK02
> [DlgAccount-0]
> Domain=HOFFMAN
> DomainAcct=MSOCLUSTER
> DomainPwd=154526877651e5de852d536c6f8f0889
> Result=1
> [DlgClientServer-0]
> Type=2
> Result=1
> [DlgInstanceName-0]
> InstanceName=MSSQLSERVER
> Result=1
> [SetupTypeSQL-0]
> szDir=C:\Program Files\Microsoft SQL Server
> Result=301
> szDataDir=S:\Program Files\Microsoft SQL Server
> SharedDataDir=S:\Program Files\Microsoft SQL Server
> [SdRemoteInfo-0]
> svEdit1=MSOCLUSTER
> svEdit2=154526877651e5de852d536c6f8f0889
> svEdit3=HOFFMAN
> svEdit4=HMS10NK04
> svEdit5=\\HMS10NK04\C$\Program Files\Microsoft SQL Server
> svEdit6=\\HMS10NK03\Z$\x86\setup\
> Result=1
> [DlgServices-0]
> Local-Domain=61680
> AutoStart=0
> SQLDomain=HOFFMAN
> SQLDomainAcct=MSOCLUSTER
> SQLDomainPwd=154526877651e5de852d536c6f8f0889
> AgtDomain=HOFFMAN
> AgtDomainAcct=MSOCLUSTER
> AgtDomainPwd=154526877651e5de852d536c6f8f0889
> Result=1
> [DlgSQLSecurity-0]
> LoginMode=2
> szPwd=086483159a17f2fb6d
> Result=1
> [DlgCollation-0]
> collation_name=SQL_Latin1_General_CP1_CI_AS
> Result=1
> [DlgServerNetwork-0]
> NetworkLibs=255
> TCPPort=1433
> TCPPrxy=Default
> NMPPipeName=\\.\pipe\sql\query
> Result=1
> [SdStartCopy-0]
> Result=1
> [License]
> LicenseMode=PERDEVICE
> LicenseLimit=4
> [SdFinish-0]
> Result=1
> bOpt1=0
> bOpt2=0
>
> "Rodney R. Fournier [MVP]" wrote:
|||THanks again, Rod - I'll try that now.
In the meantime, have you ever seen anything like this:
During the SQL Server install, I am receiving the following message: PATH
SPECIFIED IN COMMAND IS NOT VALID:
\\HMS10NK03\ADMIN$\HMS10NK03_MSSQLSERVER.ISS This path is the C:\WINDOWS
directory. The login being used to install SQL Server is a local admin on
both nodes of the cluster and the local admin group has full rights to the
directory. It's working because the user is writing various other logs.
There's plenty of space on the drive as well...
"Rodney R. Fournier [MVP]" wrote:

> Have your tried copying the SQL install files locally and running from
> there?
> Cheers,
> Rod
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering
> http://msmvps.com/clustering - Blog
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:C606061F-CB5E-48AF-A1D8-81E6F2FFF01F@.microsoft.com...
>
>
|||Make sure you have logged in to each node using the install and service
accounts before starting the installation. That will guarantee the account
profile gets set up correctly on each machine Also, check your system TMP
and TEMP variables to make sure they point to valid paths on all nodes.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:9274C646-FBC5-4949-A089-CAB3C3E63786@.microsoft.com...[vbcol=seagreen]
> THanks again, Rod - I'll try that now.
> In the meantime, have you ever seen anything like this:
> During the SQL Server install, I am receiving the following message: PATH
> SPECIFIED IN COMMAND IS NOT VALID:
> \\HMS10NK03\ADMIN$\HMS10NK03_MSSQLSERVER.ISS This path is the C:\WINDOWS
> directory. The login being used to install SQL Server is a local admin on
> both nodes of the cluster and the local admin group has full rights to the
> directory. It's working because the user is writing various other logs.
> There's plenty of space on the drive as well...
>
> "Rodney R. Fournier [MVP]" wrote:
install.[vbcol=seagreen]
in[vbcol=seagreen]
is[vbcol=seagreen]
CAN'T[vbcol=seagreen]
are[vbcol=seagreen]
would[vbcol=seagreen]
lot[vbcol=seagreen]
would[vbcol=seagreen]
|||the ADMIN$ share probably does not have the correct share permissions for
the account you are using to look at it
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:#1nqZ5kJFHA.3492@.TK2MSFTNGP10.phx.gbl...
> Make sure you have logged in to each node using the install and service
> accounts before starting the installation. That will guarantee the
account[vbcol=seagreen]
> profile gets set up correctly on each machine Also, check your system TMP
> and TEMP variables to make sure they point to valid paths on all nodes.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:9274C646-FBC5-4949-A089-CAB3C3E63786@.microsoft.com...
PATH[vbcol=seagreen]
C:\WINDOWS[vbcol=seagreen]
on[vbcol=seagreen]
the[vbcol=seagreen]
> install.
exist[vbcol=seagreen]
> in
under[vbcol=seagreen]
> is
> CAN'T
Windows[vbcol=seagreen]
> are
> would
whole[vbcol=seagreen]
> lot
message[vbcol=seagreen]
SQL
> would
>