February 23, 2012 at 3:06 am
Hi,
I tried to install single node SQL server 2008R2 failover cluster using the below commands.
setup.exe /q /ACTION=InstallFailoverCluster /IACCEPTSQLSERVERLICENSETERMS /FEATURES=SQL /INSTANCENAME="SQL***_DB0004" /INSTANCEDIR="C:\Program Files\Microsoft SQL Server" /INSTALLSHAREDDIR="C:\Program Files\Microsoft SQL Server" /SQLSVCACCOUNT="****\******" /SQLSVCPASSWORD="******" /AGTSVCACCOUNT="****\******" /AGTSVCPASSWORD="*****" /INSTALLSQLDATADIR= "H:\MSSQLSERVER" /SQLCOLLATION="SQL_Latin1_General_CP1_CS_AS" /FAILOVERCLUSTERGROUP="SQL***_DB0004" /FAILOVERCLUSTERDISKS="Disk H:" /FAILOVERCLUSTERIPADDRESSES="IPv4;**.***.**.**;Public;***.**.***.**" /FAILOVERCLUSTERNETWORKNAME="ISQL***-DB0004" /SQLSYSADMINACCOUNTS="****\******" /SECURITYMODE=SQL /SAPWD="****" /INDICATEPROGRESS
I am getting the below error
2012-02-21 17:40:02 Slp: The following exception occurred during Watson failure processing: The process cannot access the file 'C:\Users\****\AppData\Local\Temp\tmp8CDE.tmp' because it is being used by another process.
2012-02-21 17:40:02 Slp:
2012-02-21 17:40:02 Slp: ----------------------------------------------------------------------
2012-02-21 17:40:02 Slp:
2012-02-21 17:40:02 Slp: Error result: 204557340
2012-02-21 17:40:02 Slp: Result facility code: 1073
2012-02-21 17:40:02 Slp: Result error code: 19484
Anybody faced the similar issue?
When I tried without /q then I am able to do the installation successfully. Here is one problem, the instance name is selected as default though INSTANCENAME is mentioned there.
Ryan
//All our dreams can come true, if we have the courage to pursue them//
June 25, 2012 at 9:22 pm
Ryan,
I got the same issue. You need to add the parameter:
PCUSOURCE="The path for your software"
Use the path for the SP that you're installing.
Example:
PCUSOURCE="C:\install\SQL_Server2008R2\SP
or
Generate the file by running the setup and canceling it at the Ready to Install point.
June 26, 2012 at 12:56 am
rherrera 67295 (6/25/2012)
Ryan,I got the same issue. You need to add the parameter:
PCUSOURCE="The path for your software"
Use the path for the SP that you're installing.
Example:
PCUSOURCE="C:\install\SQL_Server2008R2\SP
or
Generate the file by running the setup and canceling it at the Ready to Install point.
The is a slipstream option, you'll need to obtain and extract the SP to a directory first. Then you'll need to manually install the support tools MSI from the extracted directory before using the /PCUSource or /CUSource options.
Slipstreaming the latest SP does get round a whole host of gremlins in the RTM installer.
By the way this thread is 4 months old 😉
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
June 29, 2012 at 6:23 am
I have had so much trouble trying to install a SQL Cluster with the RTM installer that I always set up slipstream media with the latest SP, and also tend to include the CU that I want.
FineBuild will do all this for you, including setting up the DTC cluster, and may be an easier way to get done what you need.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply