Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Qlik Sense June 2017 silent setup on Windows Server 2016

I am trying to setup Qlik Sense on a Windows Server 2016 vm, .\QlikSense...exe -s, it exits after couple of seconds with no error and no logs when I add the -l flag and path to logs folder. On the same machine I have achieved the silent installation of Qlik Sense 3.2.4 with just a -s flag.

So, is it possible to install Qlik Sense -s on WS2016?

1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

So, in the end it s possible, the right way would be using a command:

.\Qlik_Sense_x64setup_2017.06.exe -s -l ".\log.txt" spc='.\spc.cfg' dbpassword='postgres'

log.txt was pre-created and spc.cfg existing with such content:

<?xml version="1.0"?>

<SharedPersistenceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

  <DbUserName>qliksenserepository</DbUserName>

  <DbUserPassword>postgres</DbUserPassword>

  <DbHost>QLIKHOST</DbHost>

  <DbPort>4432</DbPort>

  <RootDir>\\sharenode\sharefolder</RootDir>

  <StaticContentRootDir>\\sharenode\sharefolder\StaticContent</StaticContentRootDir>

  <CustomDataRootDir>\\sharenode\sharefolder\CustomData</CustomDataRootDir>

  <ArchivedLogsDir>\\sharenode\sharefolder\ArchivedLogs</ArchivedLogsDir>

  <AppsDir>\\sharenode\sharefolder\Apps</AppsDir>

  <CreateCluster>true</CreateCluster>

  <InstallLocalDb>true</InstallLocalDb>

  <ConfigureDbListener>true</ConfigureDbListener>

  <ListenAddresses>*</ListenAddresses>

  <IpRange>0.0.0.0/0</IpRange>

  <!--<JoinCluster>true</JoinCluster>-->

</SharedPersistenceConfiguration>

View solution in original post

3 Replies
Anonymous
Not applicable
Author

So, in the end it s possible, the right way would be using a command:

.\Qlik_Sense_x64setup_2017.06.exe -s -l ".\log.txt" spc='.\spc.cfg' dbpassword='postgres'

log.txt was pre-created and spc.cfg existing with such content:

<?xml version="1.0"?>

<SharedPersistenceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

  <DbUserName>qliksenserepository</DbUserName>

  <DbUserPassword>postgres</DbUserPassword>

  <DbHost>QLIKHOST</DbHost>

  <DbPort>4432</DbPort>

  <RootDir>\\sharenode\sharefolder</RootDir>

  <StaticContentRootDir>\\sharenode\sharefolder\StaticContent</StaticContentRootDir>

  <CustomDataRootDir>\\sharenode\sharefolder\CustomData</CustomDataRootDir>

  <ArchivedLogsDir>\\sharenode\sharefolder\ArchivedLogs</ArchivedLogsDir>

  <AppsDir>\\sharenode\sharefolder\Apps</AppsDir>

  <CreateCluster>true</CreateCluster>

  <InstallLocalDb>true</InstallLocalDb>

  <ConfigureDbListener>true</ConfigureDbListener>

  <ListenAddresses>*</ListenAddresses>

  <IpRange>0.0.0.0/0</IpRange>

  <!--<JoinCluster>true</JoinCluster>-->

</SharedPersistenceConfiguration>

Anonymous
Not applicable
Author

Have you tried the joining the cluster (rim node)

My central node is a success but not the consumer.

<?xml version="1.0"?>

<SharedPersistenceConfiguration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

  <DbUserName>qliksenserepository</DbUserName>

  <DbUserPassword>postgres</DbUserPassword>

  <DbHost>QLIKHOST</DbHost>

  <DbPort>4432</DbPort>

  <RootDir>\\sharenode\sharefolder</RootDir>

  <StaticContentRootDir>\\sharenode\sharefolder\StaticContent</StaticContentRootDir>

  <CustomDataRootDir>\\sharenode\sharefolder\CustomData</CustomDataRootDir>

  <ArchivedLogsDir>\\sharenode\sharefolder\ArchivedLogs</ArchivedLogsDir>

  <AppsDir>\\sharenode\sharefolder\Apps</AppsDir>

  <CreateCluster>true</CreateCluster>       ----> set to false

  <InstallLocalDb>true</InstallLocalDb>      -----> set to false

  <ConfigureDbListener>true</ConfigureDbListener>

  <ListenAddresses>*</ListenAddresses>

  <IpRange>0.0.0.0/0</IpRange>

  <!--<JoinCluster>true</JoinCluster>-->       ----->un commented

</SharedPersistenceConfiguration>

Anonymous
Not applicable
Author

Nope, no further work on this, but will try in some months.