KACE
AppDeploy

SQL Server 2005 Express Edition (MSDE) 9.x
Company: Microsoft
Setup Type: Native Windows Installer setup (MSI)
Package Difficulty Rating: Somewhat Difficult (4) [ Rate It or View Ratings ]
Most Commonly Reported Method: Windows Installer Command Line (No MST)
Record Created On: 11/26/2007
Number of Views: 7,680
 
  
 
Software Knowledge Base: The software knowledge base contains details on over 60,000. The closest record matching this software package is displayed here. Browse the Software KB directly to find similar records.

No record in the Software KB was found to match this package.

Download the AppDeploy Scanner   Browse the Software KB
 
 
Command Lines: Command line details for installation and removal of this software. Details may include available command line arguments and/or public properties.

For a complete default unattended installation ...

Run SQLEXPR.EXE /x to extract the source files. Find the file template.ini (usually in the folder where the setup.exe file is). Open it and fill/add what needed and save the file under the name of your choice.

Here's the default parameters I used:
USERNAME=User
COMPANYNAME=Company
INSTALLSQLDIR=
INSTALLSQLSHAREDDIR=
INSTALLSQLDATADIR=
ADDLOCAL=SQL_Engine,SQL_Data_Files,Client_Components,Connectivity
INSTANCENAME=MSSQLSERVER
SQLACCOUNT="NT AUTHORITY\LOCAL SERVICE"
SQLBROWSERAUTOSTART=1
SQLAUTOSTART=1
AGTAUTOSTART=0
DISABLENETWORKPROTOCOLS=0
ENABLERANU=0
ADDUSERASADMIN=0

Here's the command to execute the setup with the .ini file:

start /wait setup.exe /qn /setting [path of the .ini]

Above Entry Provided on 10/21/2009 by Mencaliss 		Rate It
 Rating
0

Having followed Shuffles post from the "Notes" section, SQL installed perfect using only the MSI's.

To create a new Instance using only MSI's, find the "sqlrun.msi" and use the standard setup.exe string.
ie:

msiexec /i "..\sqlrun_sql.msi" instancename=SQLEXPRESS SQLAUTOSTART=1

Above Entry Provided on 6/27/2010 by scumoftheearth 		Rate It
 Rating
0
Add an Entry
 
 
Notes: Shared "notes from the field" covering how to handle the automated installation of this software.

2005 is problematic in that you can't just use the MSIs, as the main one, SQLRUN, relies on some registry settings which Setup.EXE puts down. We captured those and created a pre-requisite MSI for that purpose. Additionally, you need to run SQLWriter.MSI before SQLRUN. Our deployment goes like this:

- Pre-requisite MSI we created
- SQLWriter
- SQLNCLi (optional)
- SQLRun

Above Entry Provided on 11/26/2007 by VBScab 		Rate It
 Rating
6

You can use the .MSI's just fine. Install in this order for a basic setup:

SqlSupport.msi (can be installed silently)
sqlncli.msi (SQL Client - can be installed silently)
SqlWriter.msi (can be installed silently)
SqlRun.msi

Works peachy!

Above Entry Provided on 3/12/2008 by shuffle 		Rate It
 Rating
132

For Unattended install from the EXE:

sqlexpr32.exe -q /norebootchk /qn reboot=ReallySuppress addlocal=all instancename=SQLEXPRESS SQLAUTOSTART=1

NOTES:

You cannot force log files like a normal MSI (it's an "InstallShield MSI"). This particular install will create log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG

The /QN will not make the install Silent. /QB will also work. Either way it's an automated install with a lot of Flash for the user to watch. (it's an "InstallShield MSI")

Known issue: installing SQL Server 2005 fails on MSXML6

MSI log file shows:
MainEngineThread is returning 1605 (This action is only valid for products that are currently installed.)

Used the Windows Installer Cleanup Utility (available here: http://support.microsoft.com/kb/290301) to remove the MSI Database entry for MSXML6.0.

Probable Cause: There seems to be at least 2 "Flavors" of MSXML6.0. The SQL Express flavor cannot install over top of the other and does not see it as equivalent and fails with MSI error 1605.

Above Entry Provided on 11/19/2008 by misterd 		Rate It
 Rating
5

If you use the individual MSI method to install you will need to specify the features you want installed. The default install level is set to 90 and the features are set to 100.

Above Entry Provided on 6/24/2009 by joedown 		Rate It
 Rating
1
Add an Entry
 
 
Virtualization: Information regarding how to work with this software in creating a virtual deployment package for products like Altiris SVS and Microsoft SoftGrid.

Thinapp suggestion:
http://blogs.vmware.com/thinapp/2009/03/how-to-thinapp-msdesql-2005-express.html

Above Entry Provided on 1/5/2010 by nucko 		Rate It
 Rating
0
Add an Entry
 
 
Terminal Services: Notes on how to address problems working with this software in a Terminal Services session as with Citrix shared environments.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Related Links: Additional resources to reference in regards to the deployment and configuration of this software.
 
Security Information: Details covering which files, directories and/or registry entries must be opened to standard users for operation in a locked down environment.

No information at this time. Discuss this package in the forum or click here if you have something to contribute!

 
 
Discussion threads: Discussion topics in the AppDeploy message boards that have been linked as relevant information to this entry.
 

 


Report a problem
  Printer Friendly Version