SQL Server 2008 R2 Express installation config.ini
-
Thursday, August 05, 2010 4:10 PM
After I am done installing the SQL Server 2008 R2 Express, the summary.txt file points to an InstallConfig.ini. However, this ini file does not exist. Is this a bug in the installer that it does not generate an ini file. Has anyone else noticed this?
I know for a fact that with the previous version of express (2008 SP1), I could generate the installconfig.ini.
All Replies
-
Monday, August 09, 2010 8:57 AMModerator
Hi srs007,
Did you mean the file storing the configuration information during installation?
Based on my research, the configuration file generated in SQL Server 2008 R2 is ConfigurationFile.ini.
For further investigation, could you please paste the Summary.txt file here?
If anything is unclear, please let me know.
-
Monday, August 09, 2010 2:18 PM
The summary.txt is generated and lists the configuration parametres. It also points to a ConfigurationFile.ini location. However, the actual configurationFile.ini is no where to be found in the directory location specified in the summary.txt.
Here is the summary.txt:
____________________________________________________________--
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2010-08-05 13:50:51
End time: 2010-08-05 14:09:46
Requested action: InstallMachine Properties:
Machine name: USSCHDT223
Machine processor count: 1
OS version: Windows XP
OS service pack: Service Pack 3
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: NoProduct features discovered:
Product Instance Instance ID Feature Language Edition Version ClusteredPackage properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: c:\91a92ffc0066568528a4\x86\setup\
Installation edition: EXPRESS_ADVANCEDUser Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: NT AUTHORITY\NETWORK SERVICE
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Disabled
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE:
CUSOURCE:
ENABLERANU: True
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,SSMS,SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: GNO
INSTANCENAME: GNO
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: GNR_MN\ssukthankar
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: AutoAdvance
X86: FalseConfiguration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100805_134831\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: PassedFeature: Management Tools - Basic
Status: Passed
MSI status: Passed
Configuration status: PassedRules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100805_134831\SystemConfigurationCheck_Report.htm
________________________________________________________________
right below the user input settings, notice the path:
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100805_134831\ConfigurationFile.ini
The config file is not there!!!
-
Tuesday, August 10, 2010 4:48 AMModerator
Hi srs007,
It seems that this file is deleted by someone accidently.
This file just records the configuration of some installation. If the installation succeed, we doesn't need to care about this file.
Could you please provide us more information why you need this file?
-
Tuesday, August 10, 2010 3:18 PM
I need this file so that I can use it for an unattended installation along with our application s/w installer. In the past verion of SQL Server Express, this file was conveniently generated according to my input. Now I have to go through the user input parameters in the summary.txt and create my own config file. I also have to go through all the parameters and remove those that I need defaulted...doh!!
-
Tuesday, August 10, 2010 9:20 PMJust came across the problem as well. Please post a solution if you find it.
Nick's Programming Tips -
Wednesday, August 11, 2010 3:53 AMModerator
Hi srs007,
In this situation, we could run the installation process to generate a ConfigureFile.ini.
Please follow the steps below:
1. Run the installation of SQL Server 2008 R2
2. Configure the installation
3. In the “Ready to Install” page, please click “Cancel” to cancel the installation
4. Then we will see a ConfigurationFile.ini in the location provided in the textbox under “Configuration file path:” in “Ready to Install” page.
If anything is unclear, please let me know.
-
Wednesday, August 11, 2010 3:28 PM
What you say was true for the previous version of SQL Server Express. That is exactly how I would generate the configuration files on demand. However, for the current SQL Server 2008 R2 Express version, this screen was eliminated. So I cannot follow your steps as described because the 'Ready to Install' screen is not available for 'Cancel'. Infact I remember reading on the Sql Server Express website about how the new version has "fewer clicks". This was when 2008R2 was newly released. I cannot find the Microsoft page that advertised the "fewer clicks during installation" any more. The exe that I am running is SQLEXPRWT_x86_ENU.exe
But the point is that the ability to generate the configuration file automatically was really a nice feature, it was taken away either accidently or intentionally. The summary.txt points to a configration file in a certain folder and this is very misleading because the file doesnt exist there!!!
I dont think we have come up with a true solution yet.
-
Wednesday, August 11, 2010 3:35 PM
With the release of SQL Server 2008 R2, by default the ConfigurationFile.ini is not created when installing the Express version. Check out this blog entry for a solution on how to get the installer to generate the ConfigurationFile.ini:
http://nickstips.wordpress.com/2010/08/16/sql-sql-server-2008-express-missing-configurationfile-ini/
The documentation for installing SQL Server 2008 from the command line includes the switch /UIMODE that will all you to see all the dialogs in the installation wizard. Setting /UIMODE=Normal will provide you with all the dialogs. Documenation found here: http://msdn.microsoft.com/en-us/library/ms144259.aspx#Install
Excerpt from Documentation:
Specifies whether to present only the minimum number of dialog boxes during setup.
/UIMode can only be used with the /ACTION=INSTALL and UPGRADE parameters.
Supported values:
-
/UIMODE=Normal is the default for non-Express editions and presents all setup dialog boxes for the selected features.
-
/UIMODE=AutoAdvance is the default for Express editions and skips nonessential dialog boxes.
Nick's Programming Tips- Proposed As Answer by Nick Olsen Monday, August 16, 2010 3:09 PM
- Edited by Nick Olsen Monday, August 16, 2010 11:44 PM
-
-
Wednesday, August 11, 2010 5:47 PMOK I just tried running 'setup.exe /UIMODE=Normal'. It still did not produce the screen 'Ready to Install' out of which I could cancel to generate the configuration file, so status quo.
-
Thursday, August 12, 2010 1:14 AMModerator
Hi srs007,
I recommend that you try the method I provided in my previous reply in a machine without SQL Server installed.
-
Thursday, August 12, 2010 6:27 AM
I have had the same problem with SQL Server 2008 R2 Express not generating the ini file.
If you download the trial version of SQL Server 2008 R2 you will be able to generate the ini file.
- Proposed As Answer by Tom Li - MSFTModerator Thursday, August 12, 2010 7:00 AM
-
Thursday, August 12, 2010 3:05 PM
OK. I will take this as an answer although less than ideal. But I think this was an oversight...some one didnt test properly before releasing the 2008 R2 ;-)
-
Monday, August 16, 2010 12:42 PM
Nick's suggestion will work, but you must specify both flags otherwise it ignores the UIMODE flag.
So I have just run the command line: SQLEXPRWT_x86_ENU.exe /UIMODE=Normal /ACTION=INSTALL
This gives the extended UI and generates a config file at the Ready To Install screen.
-
Monday, August 16, 2010 2:55 PMThanks SamJ___ . Your suggestion totally worked. It is certainly the answer I was looking for.
-
Monday, August 16, 2010 3:06 PMSorry, I didn't catch that you didn't include /ACTION=INSTALL. The fact that you have to use that flag is posted in my original posted. It must have just been looked over.
Nick's Programming Tips -
Tuesday, December 21, 2010 11:49 PM
Note: You have to make the following manual changes to the resulting ConfigurationFile.ini in order to perform silent installs. By default when running a normal UI mode install, these aren't set.
Add:
IACCEPTSQLSERVERLICENSETERMS="True"
QUIET (or QUIETSIMPLE)="True"
SAPWD=”password”
Delete (or comment out):
UIMODE="Normal "

