debugMinor
Unattended install of SQL Server 2008 R2 cluster fails with error - "Illegal characters in path."
Viewed 0 times
illegalpathinstallfails2008unattendederrorsqlwithcharacters
Problem
I am trying to build an .ini file for unattended installations of SQL Server 2008 R2. I followed this blog post to build an initial .ini file: http://blogesh.wordpress.com/2008/09/23/silent-install-of-sql-server-2008/
After cancelling the install and trying to install from the command line
(\server\store\SQL\setup.exe /ConfigurationFile="\server\store\SQL\Config.ini"), I get this error - "Illegal characters in path."
I get this error after resolving a number of simpler errors (such as paths showing up with no "\") because the created .ini file had some bugs (such as listing the path as "R:" in the .ini)
I'd like to know if anyone has been successful with installing a cluster using an ini file. Any help is appreciated.
Update:
I tried to install the cluster using the ini created from sirsql.net's powershell script. SQL does install now, but fails to bring the network name online (in the Failover Cluster Manager). All the settings look identical to our existing (functional) clusters, but a Wireshark capture shows that the new cluster is using the "realm" of the parent domain instead of the child domain (the server's domain, and the domain of all the service accounts, including the account I am using to install with). Our functional clusters show the "realm" as the child domain.
The packet that comes back from the domain controller shows this Kerberos error:
I'd really like to get a Failover cluster setup without having to go through the gui since we are build a couple new clusters each week. Any ideas on what could be causing this or how to fix it?
After cancelling the install and trying to install from the command line
(\server\store\SQL\setup.exe /ConfigurationFile="\server\store\SQL\Config.ini"), I get this error - "Illegal characters in path."
I get this error after resolving a number of simpler errors (such as paths showing up with no "\") because the created .ini file had some bugs (such as listing the path as "R:" in the .ini)
I'd like to know if anyone has been successful with installing a cluster using an ini file. Any help is appreciated.
Update:
I tried to install the cluster using the ini created from sirsql.net's powershell script. SQL does install now, but fails to bring the network name online (in the Failover Cluster Manager). All the settings look identical to our existing (functional) clusters, but a Wireshark capture shows that the new cluster is using the "realm" of the parent domain instead of the child domain (the server's domain, and the domain of all the service accounts, including the account I am using to install with). Our functional clusters show the "realm" as the child domain.
The packet that comes back from the domain controller shows this Kerberos error:
KRB5KDC_ERR_S_PRINCIPAL_UNKNOWN.I'd really like to get a Failover cluster setup without having to go through the gui since we are build a couple new clusters each week. Any ideas on what could be causing this or how to fix it?
Solution
Nicholas Cain (@SirSQL on Twitter) published three blogs recently regarding the installation of SQL on a WIndows Failover Cluster using PowerShell to script the activity.
The first of the three blog entries may be found at http://sirsql.net/blog/2011/7/11/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
The second of the three blog entries may be found at http://sirsql.net/blog/2011/7/13/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
Finally, the third blog entry may be found at http://sirsql.net/blog/2011/7/18/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
His approach uses PowerShell and it might give you some ideas.
The first of the three blog entries may be found at http://sirsql.net/blog/2011/7/11/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
The second of the three blog entries may be found at http://sirsql.net/blog/2011/7/13/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
Finally, the third blog entry may be found at http://sirsql.net/blog/2011/7/18/creating-a-clustered-sql-install-ini-file-using-powershellpa.html
His approach uses PowerShell and it might give you some ideas.
Context
StackExchange Database Administrators Q#3962, answer score: 3
Revisions (0)
No revisions yet.