Search

QS command line parameter does not override configuration file QUIETSIMPLE by retracement

Closed
as Fixed Help for as Fixed

1
0
Sign in
 to vote
Type: Bug
ID: 713497
Opened: 12/12/2011 11:06:40 AM
Access Restriction: Public
1
Workaround(s)
0
User(s) can reproduce this bug
When using SQL command line installation setup, specifying command line parameter /QS does not override a configuration file QUIETSIMPLE="False"

Command line settings are supposed to override configuration file settings and QS is the functional shortcut for QUIETSIMPLE.
Incidently a cmd line Q *does* override a configuration file QUIET="False"
Details (expand)

Product Language

English

Version

SQL Server 2012 RC0

Category

Setup

Operating System

Windows Server 2008 R2 Enterprise

Operating System Language

English

Steps to Reproduce

Have a SQL Installation configuration file with the following set:-

QUIETSIMPLE="False"

perform a command line installation ensuring you use the /QS parameter i.e.

setup /IACCEPTSQLSERVERTERMS /ACTION=Install /QS /CONFIGURATIONFILE="<configuration file location>"

Actual Results

Interactive installation begins

Expected Results

Installation should start as QUIETSIMPLE i.e. visual non-interactive.

Platform

X64

Virtualization

 
File Attachments
File Name Submitted By Submitted On File Size  
cmdline.PNG (restricted) retracement 12/14/2011 -
Detail_ComponentUpdate.txt (restricted) retracement 12/14/2011 -
Detail_GlobalRules.txt (restricted) retracement 12/14/2011 -
Settings_GlobalRules.xml (restricted) retracement 12/14/2011 -
Summary_wonko_20111214_213115_GlobalRules.txt (restricted) retracement 12/14/2011 -
Sign in to post a comment.
Posted by Microsoft on 5/25/2012 at 6:27 AM
Hello, this bug has been fixed and will be available in the next service pack.

thanks,
[SQL Server Team]
Posted by Microsoft on 12/14/2011 at 2:12 PM
Thanks for providing the attachments. We have confirmed the issue on our end.

Thanks,
[SQL Server Team]
Posted by retracement on 12/14/2011 at 1:44 PM
5 attachments should now be available to you.

Regards,

Retracement.
Posted by retracement on 12/14/2011 at 8:19 AM
I have already told you in the workarounds that /QUIETSIMPLE from the command line correctly overrides the configuration file!
Posted by Microsoft on 12/14/2011 at 7:55 AM
Thanks for your feedback. Logs help speed the process for the developer investigating.

For a workaround could you try /QUIETSIMPLE (instead of /QS) on the command line instead and see if that resolves the issue.

thanks,
[SQL Server Team]
Posted by retracement on 12/14/2011 at 7:52 AM
I think you haven't understood the problem if you believe you need to look at any logs. This item can be replicated with ease if you follow my explanation. At the point the installer ignores the /QS switch there is little log/s generated but I shall attach what there is anyway.
Posted by Microsoft on 12/13/2011 at 12:30 PM
Could you attach the setup logs in order to facilitate further investigation?

thanks,
[SQL Server Team]
Posted by Microsoft on 12/13/2011 at 10:09 AM
Hi thanks for reporting this issues. We will investigate and get back to you shortly.

Thanks,
[SQL Server Team]
Sign in to post a workaround.
Posted by retracement on 12/12/2011 at 11:11 AM
Two ways to workaround this are:-
1. comment out or remove QUIETSIMPLE from the configuration file (which is not ideal if you want to use the configuration files as templates that you do not edit)
2. specify /QUIETSIMPLE instead of /QS (although this works fine, it totally negates the whole point of having a shortcut switch)
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement