SQL Server 2014 express /QS parameter requires user input - by ldakotaq

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 878374 Comments
Status Closed Workarounds
Type Bug Repros 14
Opened 5/20/2014 3:07:42 PM
Access Restriction Public


The following link:  Install SQL Server 2014 from the Command Prompt
states:  The /QS switch only shows progress, does not accept any input, and displays no error messages if encountered.  This is incorrect.  The /QS switch shows the Choose Directory for Extract Files dialog with Ok, Cancel, and Browse buttons.  The user must click on one of these buttons to continue.  This is a problem for me because I am installing SQL Server 2014 Express using the InstallShield Install Pre-requisites functionality.  I am using the /QS switch instead of the /Q switch because it takes several minutes to install SQL Server 2014 Express and I want the user to be able to see activity during the installation.   Note:  The /Q switch does suppress this dialog, but it suppresses all dialogs.   The change I would like is to be able to use the /QS switch, but suppress the Choose Directory for Extracted Files dialog requirement for user input.  Thank you.
Sign in to post a comment.
Posted by Azat.Khadiev on 12/1/2015 at 12:48 AM
Microsoft being Microsoft...
Posted by tknnguyen on 10/23/2015 at 5:59 PM
So I found that SP1 suppresses the user prompt for extraction, however, it defaults to the main location of where the installer package resides. My problem is that I am deploying my package along with the SQL 2014 Express package on a USB flash drive, and it is limited on space. I do not want to extract directly to the USB drive, so is there a switch to allow me to change the default extracted folder? I tried using /x:Foldername option, it worked for the extraction, but the installation no longer starts automatically after the package was fully extracted. Please help.

Thank you. Much appreciated.
Posted by Karthim20 on 7/28/2015 at 12:33 AM
SQLEXPR_x64_ENU.exe /u /x:LocationToExtract does not showing progress bar when I execute from my VB6 application, whereas if I run the same command from command prompt, am getting the progress bar. May I know how to show progress bar while extracting from VB6 code?

sample syntax: "E:\SQL 2014 Express x64\SQLEXPRWT_x64_ENU.exe /u /x:"C:\SQLEXPRWT""
Posted by simdoc on 5/15/2015 at 4:07 PM
Now that SP1 is available, how are we supposed to emulate the single step installation behavior we had with SQL 2012 Express?
Posted by Milos [MSFT] on 1/23/2015 at 8:50 AM
There was a change in the self-extract Express packages in SQL Server 2014. The default location where payload is extracted was changed. That location can be specified on the UI or on the command line.
To preset the location on the UI run:
SQLEXPR_x64_ENU.exe /x:LocationToExtract
To extract payload to a specific location without prompt use and with the progress bar use:
SQLEXPR_x64_ENU.exe /u /x:LocationToExtract
To extract payload to a specific location without prompt and silent use:
SQLEXPR_x64_ENU.exe /q /x:LocationToExtract

There is an issue that /qs parameter is not recognized and cannot be used the same way as in SQL 2012. That issue will be addressed in SQL Server 2014 Service Pack 1.
Posted by Tero Salonen on 12/21/2014 at 10:45 PM
We have also embedded SQL Server 2014 Express installation to our software package. I was aware of this issue that if though using /QS switch installation requires user input to select folder to extract files. Recently we discovered a problem that extraction was not successful since provided default path was long enough causing path to exceed MAX_PATH. This caused whole installation to fail and error message returned to user was not exact. Default extraction folder is determined in our case by InstallShield based on where it extracts pre-requisites for installation from install package. Then SQL Server installation uses that as base path for extraction and if base path is too long then extraction will fail at some point. SQL Server installation package uses quite long path names internally so base path needs to be rather short. Couldn't figure any workaround for this unfortunately thus looking for rather quick fix for this.
Posted by kwypto77 on 11/4/2014 at 2:17 PM
This is a real problem for us. We actually take advantage of the QS setting for the very reason that the user gets to see progress, but it doesn't require any user input. We are currently using 2012 and were wanting to move up to 2014. Unfortunately we will not be able to do it because of this issue.
Posted by simdoc on 10/8/2014 at 10:42 AM
It also needs to remove the extraction folder when complete as it did with 2012. It doesn't do this with /Q either. With /Q or /QS it should extract to a temporary folder then delete this folder when complete. All this was working fine in 2012. Seems like someone broke something that was working perfectly well.
Posted by Bandit2001 on 7/14/2014 at 1:45 AM
Is there any chance to get a quick fix?
We need a silent installation of SQL Server 2014 Express as a Setup-Prerequisite.

Posted by ldakotaq on 7/8/2014 at 8:15 AM
This issue is specific to the express installers: sqlexprwt_x86_ENU.exe and most likely the 64 bit one as well. The other versions of SQL Server 2014 are not packaged in a single executable like SQL Express. Note: The use of the /QS switch to skip the extraction dialog worked in earlier versions of SQL Server express using the same executable name of sqlexprwt_x86_ENU.exe.
Posted by Sethu Srinivasan on 7/8/2014 at 12:02 AM
Let us know if you see the same issue with other SQL Server editions in SQL 2014

Sethu Srinivasan [MSFT]
SQL Server