cancel
Showing results for 
Search instead for 
Did you mean: 
JoeDen
Pilgrim

Help with SQL 2014 Express slient install

Hello - I apologize if this ends up being a duplicate...I submitted a new thread earlier, but it never showed up.

I'm fairly new to InstallShield 2015 and am trying to leverage existing logic that installed SQL 2008 Express R2 SP1 to use with SQL 2014 Express RTM (x86 & x64 Wow). This is a feature perquisite.

The plan is to do a new install of SQL 2014 and not upgrade 2008. I've been testing using a Win10 64-bit machine and the install appears to work silently, but fails shortly after the SQL install starts.

I've been doing research, but can't find a solution to what appears to be a common problem.

Can someone please review the following and let me know if you can see where I'm going wrong? Thanks in advance!!

One note: c:\SQL is only a test to see if it works with a shorter path name...this isn't permanent.

command line used as a custom action:
/SQLEXPR32_x86_ENU.exe /SkipInstallerRunCheck=1 /Q /x:c:\SQL /INSTANCENAME=SunGardiWORKS /ACTION=Install /FEATURES=SQL /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCSTARTUPTYPE=Automatic /HIDECONSOLE /IACCEPTSQLSERVERLICENSETERMS /SkipRules=RebootRequiredCheck

I've attached the full SqlSetup.log details...here are some details...
//////////////////////////////////////
05/02/2017 16:33:32.691 Attempting to launch landing page workflow
05/02/2017 16:33:32.832 Media source: C:\SQL\
05/02/2017 16:33:32.832 Install media path: C:\SQL\x86\setup\
05/02/2017 16:33:32.847 Media layout: Core
05/02/2017 16:33:32.847 Attempting to get execution timestamp
05/02/2017 16:33:32.847 Timestamp: 20170502_163327
05/02/2017 16:33:32.847 Attempting to run workflow LANDINGPAGE
05/02/2017 16:33:32.863 Attempting to launch process C:\SQL\x86\ScenarioEngine.exe
05/02/2017 16:36:34.328 Process returned exit code: 0x84B40001
05/02/2017 16:36:34.344 Workflow LANDINGPAGE returned exit code: 0x84B40001
//////////////////////////////////////
05/02/2017 16:36:35.141 Setup closed with exit code: 0x84C40013
Labels (1)
0 Kudos
9 Replies
rguggisberg
Active participant

Re: Help with SQL 2014 Express slient install

For SQL 2014/2016 Microsoft changed the default location where payload was extracted to.
Try replacing
/x:c:\SQL
with this
/x:"%Temp%\SQLEXPR32_x86_ENU.exe"

I should have added that this assumes your executable is named SQLEXPR32_x86_ENU.exe. I see you are reusing code so you may need to change that accordingly.
0 Kudos
JoeDen
Pilgrim

Re: Help with SQL 2014 Express slient install

rguggisberg wrote:
For SQL 2014/2016 Microsoft changed the default location where payload was extracted to.
Try replacing
/x:c:\SQL
with this
/x:"%Temp%\SQLEXPR32_x86_ENU.exe"

I should have added that this assumes your executable is named SQLEXPR32_x86_ENU.exe. I see you are reusing code so you may need to change that accordingly.

///////////////////////////////////////

Hi rguggisberg - thanks for your reply. I made the following change, but the install is still failing.

/SQLEXPR_x86_ENU.exe /SkipInstallerRunCheck=1 /Q /x:%Temp%\SQLEXPR_x86_ENU.exe /INSTANCENAME=SunGardiWORKS /ACTION=Install /FEATURES=SQL /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCSTARTUPTYPE=Automatic /HIDECONSOLE /INDICATEPROGRESS /IACCEPTSQLSERVERLICENSETERMS /SkipRules=RebootRequiredCheck

I also noticed that the Sqlsetup.log is no longer being created. I found the following in the msi log...not sure where to go next...any suggestions?

Action 10:44:10: Installing Microsoft SQL Server 2014 Express RTM (x86 & x64Wow). Installing Microsoft SQL Server 2014 Express RTM (x86 & x64Wow)
MSI (c) (CC!58) [10:44:10:937]: Closing MSIHANDLE (646) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Creating MSIHANDLE (647) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Creating MSIHANDLE (648) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Closing MSIHANDLE (647) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Closing MSIHANDLE (648) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Creating MSIHANDLE (649) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Closing MSIHANDLE (649) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Creating MSIHANDLE (650) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:937]: Closing MSIHANDLE (650) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:953]: PROPERTY CHANGE: Adding ISPREREQDIR property. Its value is 'C:\Users\JOE~1.BOC\AppData\Local\Temp\{0AA46B8B-55D7-45F9-8AAA-A017CA9A626A}\{BA6CCDBA-B43D-417D-9F28-89988A3DB2AB}\'.
MSI (c) (CC!58) [10:44:10:953]: Creating MSIHANDLE (651) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:953]: Creating MSIHANDLE (652) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:953]: Closing MSIHANDLE (652) of type 790531 for thread 5208
MSI (c) (CC!58) [10:44:10:953]: Closing MSIHANDLE (651) of type 790531 for thread 5208
MSI (c) (CC!58) [10:45:08:568]: Creating MSIHANDLE (653) of type 790531 for thread 5208
MSI (c) (CC!58) [10:45:08:568]: Closing MSIHANDLE (653) of type 790531 for thread 5208
MSI (c) (CC!58) [10:45:08:568]: Creating MSIHANDLE (654) of type 790531 for thread 5208
Info 2835.The control ErrorIcon was not found on dialog SetupError.
The installation of Microsoft SQL Server 2014 Express RTM (x86 & x64Wow) has failed. Setup will now exit.
MSI (c) (CC!58) [12:40:46:989]: Closing MSIHANDLE (654) of type 790531 for thread 5208
MSI (c) (CC!58) [12:40:50:020]: Creating MSIHANDLE (655) of type 790531 for thread 5208
InstallShield 12:40:50: *** Prerequisites complete; return code 2
MSI (c) (CC!58) [12:40:50:020]: Closing MSIHANDLE (655) of type 790531 for thread 5208
MSI (c) (CC!58) [12:40:50:020]: Creating MSIHANDLE (656) of type 790531 for thread 5208
InstallShield 12:40:50: Destroyed Window {44C92F81-F492-48F7-906B-EDA9D7D5583C}
MSI (c) (CC!58) [12:40:50:020]: Closing MSIHANDLE (656) of type 790531 for thread 5208
CustomAction ISInstallPrerequisites returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (CC:64) [12:40:50:020]: Closing MSIHANDLE (223) of type 790542 for thread 1700
Action ended 12:40:50: ISInstallPrerequisites. Return value 3.
MSI (c) (CC:A4) [12:40:50:020]: Doing action: SetupCompleteError
Action 12:40:50: SetupCompleteError.
Action start 12:40:50: SetupCompleteError.

The last line in the log file is:
MSI (c) (CC:A4) [12:40:56:551]: MainEngineThread is returning 1603
0 Kudos
rguggisberg
Active participant

Re: Help with SQL 2014 Express slient install

I would try these things... one at a time:
1. Search your computer for Sqlsetup.log. I think you will find it somewhere else (I forget where right now).
2. Remove the /HIDECONSOLE to see if anything is shown
3. Remove the /INDICATEPROGRESS. For some unknown reason I can't show progress for SQL 2014 or SQL 2016 on silent install the way I could for SQL 2008 and SQL 2012.
4. Execute your command line from a CMD prompt. Get it working that way first. You may choose to try this before choices 2 & 3.
0 Kudos
JoeDen
Pilgrim

Re: Help with SQL 2014 Express slient install

rguggisberg wrote:
I would try these things... one at a time:
1. Search your computer for Sqlsetup.log. I think you will find it somewhere else (I forget where right now).
2. Remove the /HIDECONSOLE to see if anything is shown
3. Remove the /INDICATEPROGRESS. For some unknown reason I can't show progress for SQL 2014 or SQL 2016 on silent install the way I could for SQL 2008 and SQL 2012.
4. Execute your command line from a CMD prompt. Get it working that way first. You may choose to try this before choices 2 & 3.


Thanks for the recommendations...I appreciate your help! I'll give these a try...
0 Kudos
JoeDen
Pilgrim

Re: Help with SQL 2014 Express slient install

I was able to get SQL installed from a CMD prompt, but I needed to edit the command to use c:\SQL instead of %Temp%\SQLEXPR_x86_ENU.exe

c:\SQL>Setup.exe /SkipInstallerRunCheck=1 /Q /INSTANCENAME=SunGardiWORKS /ACTION=Install /FEATURES=SQL /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCSTARTUPTYPE=Automatic /IACCEPTSQLSERVERLICENSETERMS /SkipRules=RebootRequiredCheck

/////////////////////////
When I ran the following it failed...
C:\Users\joe.bock\AppData\Local\Temp\SQLEXPR_x86_ENU.exe>Setup.exe /SkipInstallerRunCheck=1 /Q /x:%Temp%\SQLEXPR_x86_ENU.exe /INSTANCENAME=SunGardiWORKS /ACTION=Install /FEATURES=SQL /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCSTARTUPTYPE=Automatic /IACCEPTSQLSERVERLICENSETERMS /SkipRules=RebootRequiredCheck


Microsoft (R) SQL Server 2014 12.00.2000.08
Copyright (c) Microsoft Corporation. All rights reserved.

The following error occurred:
The argument '/X:C:\USERS\JOE~1.BOC\APPDATA\LOCAL\TEMP\SQLEXPR_X86_ENU.EXE' is formatted incorrectly. The delimiter '=' is missing.

Error result: -2068578298
Result facility code: 1204
Result error code: 6

Please review the summary.txt log for further details
///////////////////

It doesn't seem to like installing from C:\USERS\JOE~1.BOC\APPDATA\LOCAL\TEMP...any idea which delimiter is miss the '='?
0 Kudos
rguggisberg
Active participant

Re: Help with SQL 2014 Express slient install

For the temp dirrectory In one case it is using
C:\Users\joe.bock
and in the other case it is using
C:\USERS\JOE~1

Try changing
%Temp%
to
C:\USERS\JOE.BOCK\APPDATA\LOCAL\TEMP\
0 Kudos
JoeDen
Pilgrim

Re: Help with SQL 2014 Express slient install

rguggisberg, thanks again for your replies...

I tried changing %Temp% to C:\USERS\JOE.BOCK\APPDATA\LOCAL\TEMP\, but the install failed.

I also tried running a CMD prompt from C:\USERS\JOE.BOCK\APPDATA\LOCAL\TEMP\SQLEXPR_x86_ENU.exe and was able to successfully install SQL 2014 Express. I used the following command:
Setup.exe /SkipInstallerRunCheck=1 /Q /INSTANCENAME=SunGardiWORKS /ACTION=Install /FEATURES=SQL /SQLSVCACCOUNT="NT AUTHORITY\SYSTEM" /SQLSYSADMINACCOUNTS="BUILTIN\ADMINISTRATORS" /SQLSVCSTARTUPTYPE=Automatic /IACCEPTSQLSERVERLICENSETERMS /SkipRules=RebootRequiredCheck

Next, I used the same command in my InstallShield project, but the installed failed. It tried to use the default location, but I'm guessing it didn't like the long path name.
//////////////////
Action 11:49:07: Installing Microsoft SQL Server 2014 Express RTM (x86 & x64Wow). Installing Microsoft SQL Server 2014 Express RTM (x86 & x64Wow)
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (646) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (647) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (648) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (647) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (648) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (649) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (649) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (650) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (650) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: PROPERTY CHANGE: Adding ISPREREQDIR property. Its value is 'C:\Users\JOE~1.BOC\AppData\Local\Temp\{1586D722-5FE1-4539-BB52-01C8B9312EEC}\{BA6CCDBA-B43D-417D-9F28-89988A3DB2AB}\'.
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (651) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Creating MSIHANDLE (652) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (652) of type 790531 for thread 5900
MSI (c) (50!0C) [11:49:07:498]: Closing MSIHANDLE (651) of type 790531 for thread 5900
MSI (c) (50!0C) [11:50:36:577]: Creating MSIHANDLE (653) of type 790531 for thread 5900
MSI (c) (50!0C) [11:50:36:577]: Closing MSIHANDLE (653) of type 790531 for thread 5900
MSI (c) (50!0C) [11:50:36:577]: Creating MSIHANDLE (654) of type 790531 for thread 5900
Info 2835.The control ErrorIcon was not found on dialog SetupError.
The installation of Microsoft SQL Server 2014 Express RTM (x86 & x64Wow) has failed. Setup will now exit.
MSI (c) (50!0C) [11:50:42:436]: Closing MSIHANDLE (654) of type 790531 for thread 5900
MSI (c) (50!0C) [11:50:45:780]: Creating MSIHANDLE (655) of type 790531 for thread 5900
InstallShield 11:50:45: *** Prerequisites complete; return code 2
MSI (c) (50!0C) [11:50:45:780]: Closing MSIHANDLE (655) of type 790531 for thread 5900
MSI (c) (50!0C) [11:50:45:780]: Creating MSIHANDLE (656) of type 790531 for thread 5900
InstallShield 11:50:45: Destroyed Window {B598447D-3AF3-43D4-8B7B-D43B7ABC9275}
MSI (c) (50!0C) [11:50:45:780]: Closing MSIHANDLE (656) of type 790531 for thread 5900
CustomAction ISInstallPrerequisites returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (50:D0) [11:50:45:780]: Closing MSIHANDLE (223) of type 790542 for thread 5980
Action ended 11:50:45: ISInstallPrerequisites. Return value 3.
MSI (c) (50:5C) [11:50:45:780]: Doing action: SetupCompleteError
Action 11:50:45: SetupCompleteError.
Action start 11:50:45: SetupCompleteError.
//////////////////

Is it possible to do a silent install of SQL 2014 Express?? I've seen a lot of comments online, but haven't seen a solution.
0 Kudos
rguggisberg
Active participant

Re: Help with SQL 2014 Express slient install

Yes, I do a silent install of SQL 2014 Express... but I do it as part of Server set up using an ini file and not in InstallShield.
Error 1603 could be a number of things.... are you sure SQL was not already installed?
I would continue trying to install from CMD prompt and get it working that way first.
We have already discussed 2 differences wit SQL 2014:
1. Location of extracted files
2. I don't think you can display the progress bar with SQL 2014 as you can with previous versions of SQL.
0 Kudos
JoeDen
Pilgrim

Re: Help with SQL 2014 Express slient install

rguggisberg wrote:
Yes, I do a silent install of SQL 2014 Express... but I do it as part of Server set up using an ini file and not in InstallShield.
Error 1603 could be a number of things.... are you sure SQL was not already installed?
I would continue trying to install from CMD prompt and get it working that way first.
We have already discussed 2 differences wit SQL 2014:
1. Location of extracted files
2. I don't think you can display the progress bar with SQL 2014 as you can with previous versions of SQL.


rguggisberg - thanks again for your help with this issue...

I've been testing a couple ways:
1) on a clean QA machine that doesn't have SQL installed
2) after I was able to successfully install using a CMD prompt, I uninstalled SQL and made sure nothing was left behind.

The install is failing both ways when trying through Installshield. I've had success using a CMD prompt, but using the same commands in Installshield fails. I've also tried using a .bat file to install SQL which was successful, but trying to use the same .bat in Installshield failed. I'm pretty sure it tried to run the .bat before the setup was extracted.

I'm going to try and take the .bat approach next and get the setup extracted before running the .bat file.

I'm pretty new to Installshield so this may take some time/testing. If this fails, I'm going to try removing SQL as a feature pre-req and install it before our application install kicks off.

I appreciate your time helping me through this...

Joe
0 Kudos