I am using installshield to distribute SQL Server 2005 Express. I have the SQLEXPR.EXE file and I want to run it in /qb mode so the user can see the pretty dialogs pop up but not have to click anything.
The SQL Express books say that SQL Express uses the same command line switches that SQL does, so I looked up the switches here:
SQL Server 2005 Books Online
How to: Install SQL Server 2005 from the Command Prompt
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/instsql9/html/df40c888-691c-4962-
a420-78a57852364d.htm#installationscripts
"The /qb switch allows the display of basic Setup dialog boxes. Error messages are also displayed."
The problem is thus:
On a Windows Server 2003 box that does not have Service Pack 1, the installation runs and then exits silently. No errors are displayed to the user and the installation is not completed.
In the C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt file it says the setup failed because the system did not meet the min requirements (no service pack 1).
I am not sure where to go from here, maybe make the user install SQL Express manually
Any Ideas
Apparent BUG with SQL Server 2005 Express silent install /qb command line ( SQLEXPR.EXE/qb ) and displaying errors.
Hot Topic
- I need a CONNECTION GURU to explain what is going on.
- SQL Looping for Complex Query
- Command Line connect to SQL Server Database
- Oddball SQL calculation query - any Gurus up to this??
- Use Replication to Identify Updated Data?
- NOT build index while loading data into a DW
- System Tray Icon Missing?
- Time Intelligence
- Matrix not displaying null fields
- Updating database workflow question
SQL Server
- Trouble inserting multiple nodes during UPDATE
- Authentication, windows or custom
- Oddball SQL calculation query - any Gurus up to this??
- how to align data
- Accessing Multiple databases from Stored procedure in SQL 2000
- Parameters
- AS2005 - Displaying time calculations in a Perspective
- How to run DTS package/upgrade in SQL 2005.
- COnfiguring Number of records per page?
- Confused about MSSQL Express installations
Apparent BUG with SQL Server 2005 Express silent install /qb command line ( SQLEXPR.EXE/qb ) and displaying errors.
djartsinc
hi,
the point is... sqlexpr.exe doesn't accept the mentioned switches.
/qb, /qn, ... are for setup.exe which is the main installer file for sql server express.
you will have to extract files inside sqlexpr.exe using /x switch, and then you will find all the files required to install sql server express, including template.ini which is also useful for passing parameters to setup.exe.
sqlexpr.exe /x (then select the path to extract files)
setup.exe /qb addlocal=all (or any other arguments...)
this has worked for me; hope it helps.
bigmanu
Acutally this isn't correct. passing the command line switches to SQLEXPR.EXE works. The compression utility used to create SQLEXPR.exe will pass the command line switches to setup.exe post extraction. For example, I can run the following SQLEXPR.exe /q /qb ADDLOCAL=ALL. The /q goes to the compression utility to supress the extraction. /qb goes to setup.exe to show progress dialogs only. And ADDLOCAL=ALL goes to setup.exe to specify what'll be installed.
Win2K3 RTM is not a supported platform and as such Express will not install.
Cheers,
Dan
antonieb
Sorry friend.
Windows 2003 Server is a supported platform for SQL Server 2005 Express. It installs and works great (32bit and 64bit).
The issue with the SQLEXPR.EXE file occurs on Windows XP with no service packs. The problem is the error is not reported.
I fixed the problem by simply having InstallShield check to make sure that we were installing on a Supported Enviroment before calling SQLEXPR.EXE
Thanks though, hope this helps other people.
Steve Adams
I am using SQLEXPR.exe as a setup prerequisite in Installshield 2008 Pro, trying to use the command line switches to perform a silent install and a define instance name.
I have tried a number of command line combinations with no luck, has anyone deployed SQL Express this way and if so which switch has worked in an Installshield prerequisite.
Thanks
James Mayer
It also happens when hardware requirements are not met. I think sqlexpr with "/qb" option should show these messages, since it's cumbersome to check for every condition that could cause installation to fail.