StarQuest Technical Documents

Silent Installation of StarSQL

Last Update: 26 September 2013
Product: StarSQL
Version: 6.x
Article ID: SQV00SQ057


This document describes how to execute a silent installation of StarSQL v6.1 and later. See Creating a Custom StarSQL v5.x Installable Image for instructions on creating a silent installation of StarSQL v5.x and v6.0.

The installer for StarSQL v6.1 and later is a Basic MSI project. A normal (non-silent) installation receives the necessary input from the user in the form of responses to dialog boxes. However, a silent installation does not prompt the end user for input. Instead, it obtains its input from arguments passed on the command line.


Silent Install

The following command will install a Typical Setup to the default installation directory (e.g. C:\Program Files\StarQuest\StarSQL):

C> Setup.exe /s /v"/qn"

The /s parameter tells setup.exe to run silently, and /v passes the arguments /qn (quiet, no UI) to msiexec.exe.

To specify a target directory, pass the INSTALLDIR property to msiexec.exe; if the directory name includes spaces, use the backslash character to escape quotes:

C> setup /s /v"/qn INSTALLDIR=\"C:\My Directory With Spaces\""

To specify which StarSQL features you want to install, use the ADDLOCAL msiexec.exe property. The following example installs the Core driver software with standard licensing (SQ_SPECIFIC) and the Trace Viewer utility (TrcView):

C> setup /s /v"/qn ADDLOCAL=Core,SQ_SPECIFIC,TrcView"

If you do not use the ADDLOCAL property, the typical install contains the features Core, SQ_SPECIFIC, TrcStart, PDF, and Licensing (for the standard installer), or Core, UNLICENSED_SPECIFIC, TrcStart, and PDF (for the special enterprise installer).

The following table shows the feature names that you can specify with the ADDLOCAL command. The feature names are case sensitive, and only properly-specified features will be installed during the silent installations. For a successful installation you must specify that the Core be installed in addition to specifying a license type. Additional feature names are optional, although it is recommended that you include the PDF feature to install the documentation for the core StarSQL driver.

Feature Name Required? Description
Core required the core StarSQL driver
SQ_SPECIFIC UNLICENSED_SPECIFIC one or the other is required indicates whether you have a standard or enterprise license for using StarSQL
these tools are all optional-- you can specify one or more of these feature names the tool choices allow you to install the:

TraceStart utility, which initiates a DRDA trace.
TraceViewer utility, which is used to display a DRDA trace.
ResourceManager, which provides support for two-phase commit transactions in a TCP/IP network.
Admin2PC, which provides a utility for managing two-phase commit transactions.


PDF is recommended


The PDF feature provide documentation for the core StarSQL driver.
Licensing optional The Licensing feature installs the StarLicense utility and help system.

Importing a Data Source and License Configuration

The installer can import both a StarSQL data source and a license configuration during the installation.

  • To import a data source:

Create a DSIMPORT.TXT file as instructed in the StarSQL User's Guide or in the technical document How to Distribute StarSQL Data Source(s) to Your Users. Copy this file to the root of the installation directory (i.e. F:\starsql_install), it must be in the same location as the setup.exe.

  • To import a license configuration:

Follow the StarSQL User's Guide to find the starlic.lic file which contains the license information. Copy this file to the root of the installation directory (i.e. F:\starsql_install), it must be in the same location as the setup.exe.

An alternative to importing a license configuration is to use the default license server name of “starlic".  Refer to the StarSQL for Windows Users Guide for details on SQIMPORT and the default license server name.

Silent Uninstall of StarSQL 6.1 and later

  • Identify the product code of the version of StarSQL that you are uninstalling.

For 32-bit StarSQL v6.1: {F4B7BE16-3252-47B8-88D5-84597846D3ED}
For 64-bit StarSQL v6.1: {44DC33D6-2932-461E-A269-173486FAE4FC}

  • To verify the product code, use regedit to locate the registry key for StarSQL in

For 32-bit StarSQL v6.1 on a 32-bit system, confirm that this registry key exists:

For 32-bit StarSQL v6.1 on a 64-bit system, look for:

For 64-bit StarSQL v6.1, look for:

If the expected registry key does not exist, contact StarQuest Support; the product code may change in future versions of StarSQL.

  • Make sure that are no active ODBC applications (SQDR, SQL Server Linked Server, etc) are using StarSQL and that StarSQL utilities such as trcstart are not running.
  • Issue the following command

C> MsiExec.exe /qn /xPRODUCT_CODE


For 32-bit StarSQL v6.1 on either 32-bit or 64-bit systems:
C> MsiExec.exe /qn /x{F4B7BE16-3252-47B8-88D5-84597846D3ED}

for 64-bit StarSQL v6.1:
C> MsiExec.exe /qn /x{44DC33D6-2932-461E-A269-173486FAE4FC}

Additional Information for Upgrade Scenarios:

You may want to perform a silent uninstall of earlier versions of StarSQL before executing a silent install of StarSQL 6.1.

StarSQL v5.x and v6.0:

  • To update from StarSQL v5.x and v6.0, which use MSI InstallScript installers, construct an uninstall command in the following manner:

Using regedit, locate the registry key for StarSQL in

Or (on a 64-bit system)

For example, the 32-bit version of StarSQL 5.51 through 6.0 will be this entry:


for 32-bit StarSQL on a 64-bit system:

For 64-bit StarSQL on a 64-bit system: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\InstallShield_{B3962DA7-634A-4D15-BE7D-8A2D7EB522BB}

Note that the entry is located in the Wow6432Node (32-bit) area on a 64-bit system, even for 64-bit StarSQL.

* Once you have identified the registry key, copy the contents of the Uninstall value - this will be something like:

"C:\Program Files (x86)\InstallShield Installation Information\{A60CD161-348E-4D88-8598-6456DE951539}\setup.exe" -runfromtemp -l0x0409 -removeonly

* You will also need the uninstall_starsql55x.iss file from the appropriate (32-bit or 64-bit) StarSQL 6.1 installer directory. Note that the contents of this file is different for 32-bit vs 64-bit StarSQL.

Append the following string to the Uninstall string you copied from the registry:

/s /uninst /F1"<path_to_iss_file>uninstall_starsql55x.iss"

For example, assuming you extracted the contents of the StarSQL installer to C:\temp\starsql_installer, this is the command to silently uninstall the 32-bit version of StarSQL from a 32-bit system:

"C:\Program Files\InstallShield Installation Information\{A60CD161-348E-4D88-8598-6456DE951539}\setup.exe" -runfromtemp -l0x0409 -removeonly /s /uninst /F1"C:\temp\starsql_installer\x86\uninstall_starsql55x.iss"

Here is an example of silently uninstalling the 64-bit version of StarSQL:

"C:\Program Files (x86)\InstallShield Installation Information\{B3962DA7-634A-4D15-BE7D-8A2D7EB522BB}\setup.exe" -runfromtemp -l0x0409 -removeonly /s /uninst /F1"C:\temp\starsql_installer\x64\uninstall_starsql55x.iss"

If you are uninstalling an earlier version of StarSQL 5.x (prior to 5.51), the Product Code GUID's above will differ, and you will need to construct the .iss file; contact StarQuest support for assistance.

Below are the Product Code GUID's for all versions of StarSQL 5.x:

StarSQL 32-bit:
{A60CD161-348E-4D88-8598-6456DE951539} StarSQL 5.51 through 6.0
{784E3D03-CC95-4E17-A980-563814F2BEFE} StarSQL 5.50
{951C06B8-A3E9-41CA-8BCF-AF17C3B61D4A} StarSQL 5.3, 5.4
{8A76671C-B52E-475E-9005-807C1AA0A67A} StarSQL 5.2
{0E192DF7-EFBF-4C5C-A1AC-4D46A2F28E43} StarSQL 5.0, 5.1

StaSQL 64-bit:
{B3962DA7-634A-4D15-BE7D-8A2D7EB522BB} StarSQL 64-bit 5.51 through 6.0
{C9321638-7FD3-469F-8DA0-C1EBD790130B} StarSQL 64-bit 5.50

StarSQL v4 and earlier:

The following script will silently StarSQL v4 and earlier. These versions used an installer created with InstallShield v5.5.

You may need to adjust values in the script if you have installed StarSQL to a different location, and the name of the ISU file may vary with older (v2 & v3) versions of StarSQL. You can copy the Properties of the shortcut for “Uninstall StarSQL” located in the Start Menu and add “-a” to indicate silent mode.

*  Copy the following into a text editor and save as UNINSTALL_V4X.BAT:


REM -a = Run the uninstaller in silent mode. In this mode unInstallShield will not display any messages to the end user indicating that the REM uninstallation has taken place. When running in silent mode, if unInstallShield encounters a shared file for which it would normally display the REM dialog box asking the user whether to remove the shared file, it will automatically reduce the reference count to zero and not remove the file. REM Therefore, running unInstallShield in silent mode is functionally equivalent to an uninstallation in which the user selects the “No to all” REM option when this dialog box first appears.

C:\WINNT\IsUninst.exe -a -fC:\StarSQL\STRSQL32.ISU -c"C:\StarSQL\Programs\LATC.DLL"

Run the UNINSTALL_V4X.BAT file to uninstall a previous version of StarSQL in silent mode.


The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.