Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Silently uninstalling Qlik Replicate

Silently uninstalling Qlik Replicate consists of creating a response file and then running the uninstall.

Creating a response file

Before starting the uninstall, you need to create a response file.

To create the response file

  1. Copy the response file text below into a text editor.

    Response file text:

    [{9C614355-28A0-4C2A-98DF-DB9FD674826F}-DlgOrder]

    Dlg0={9C614355-28A0-4C2A-98DF-DB9FD674826F}-SdWelcomeMaint-0

    Count=3

    Dlg1={9C614355-28A0-4C2A-98DF-DB9FD674826F}-MessageBox-0

    Dlg2={9C614355-28A0-4C2A-98DF-DB9FD674826F}-SdFinish-0

    [{9C614355-28A0-4C2A-98DF-DB9FD674826F}-SdWelcomeMaint-0]

    Result=1

    [{9C614355-28A0-4C2A-98DF-DB9FD674826F}-MessageBox-0]

    Result=6

    [{9C614355-28A0-4C2A-98DF-DB9FD674826F}-SdFinish-0]

    Result=1

    bOpt1=0

    bOpt2=0

  2. Save the file as <name>.iss, e.g. silent_uninst_64.iss.

Running a silent uninstall

To silently uninstall Qlik Replicate, open a command prompt and issue the following command (where RESPONSE_FILE is the path to the response file you created earlier and LOG_FILE is the path to the uninstall log file):

Syntax:  

"C:\Program Files (x86)\InstallShield Installation Information\directory_containing_setup_file\setup.exe" /s /f1RESPONSE_FILE [/f2LOG_FILE]

Information note

The directory containing the Replicate setup file always ends with the following string: DB9FD674826F

Example:  

C:\>"C:\Program Files (x86)\InstallShield Installation Information\{9C614355-28A0-4C2A-98DF-DB9FD674826F}\setup.exe" /s /f1C:\temp\response.iss /f2C:\temp\1\silent_uninstall.log

 

If the uninstall was successful, the log file should contain the following rows:

[ResponseResult]

ResultCode=0

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!