There has always been a noticeable gap in Qlik Replicate, where users had no means of importing just an endpoint into Qlik Replicate. This article provides a workaround to that limitation.

1. To start creating an endpoint, it is advisable to prototype something the product generates.
   
   Create a dummy task with a dummy endpoint (source or target) which resembles the endpoint you wish to import. This task or endpoint does not have to be perfectly filled out. See example below: 
   
   
   
   
2. Once the dummy task has been set up, export the task. See Exporting tasks.
   
   
3. Open the resulting JSON file. See Editing an exported (json) file. 
   
   
4. You will only need the following definitions from the task JSON payload:
   
   The "cmd.replication_definition"."databases" group and a "_version" member:
   
   

   {
   	"cmd.replication_definition":	{
   		"databases":	[{
   		...
   			}]
   	},
   	"_version":	{
   		...
   	}
   }

5.  Create the JSON definitions of the endpoint following the example below. This will be the endpoint you import. 
   
   

   Verify that your endpoint name is correct.  
   
   

   You may want to skip entering the password and add it later through the user interface. Inputting the password in the JSON is in plain text.

   {
   	"cmd.replication_definition":	{
   		"databases":	[{
   				"name":	"DB2z_Source",
   				"description":	"",
   				"role":	"SOURCE",
   				"is_licensed":	true,
   				"type_id":	"DB2ZOS_NATIVE_COMPONENT_TYPE",
   				"db_settings":	{
   					"$type":	"Db2zosSettings",
   					"additionalConnectionProperties":	"MaryHad=aLittleLamb",
   					"username":	"dimae",
   					"databaseAlias":	"DBALIAS",
   					"server":	"lpardns.mydomain.com",
   					"port":	5035,
   					"databaseName":	"LOCATION",
   					"CCSIDMapping":	"234,ibm-p100-2345",
   					"ifi306SpName":	"R4Z_UDF_ALL_NEW"
   				},
   				"override_properties":	{
   				}
   			}]
   	},
   	"_version":	{
   		"version":	"2023.5.0.213",
   		"version_major":	2023,
   		"version_minor":	5,
   		"version_revision":	213
   	}
   }

6. Save this content as a .JSON file. We recommend the /data/imports folder to make the import command simpler, but any folder and drive your user has access to can be used.
   
   
7. Import the definitions into the Qlik Replicate server.
   
   You can do so using either:
   • Qlik Enterprise Manager API
   • Qlik Enterprise Manager
   • Qlik Replicate UI, 
   • repctl CLI  command (on Windows):
     

     repctl importrepository json_file=NAMEOFFILE.JSON folder_name=DRIVE:\FOLDER

        

Related Content

Editing an exported (json) file
ImportAll | Enterprise Manager API
Exporting and importing tasks
Importing tasks

Environment

• Qlik Replicate
• Qlik Enterprise Manager

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Qlik Replicate can be licensed using RepCtl. For instructions on how to license Qlik Replicate using the standard user interface, see Registering a license.

To register a license on Windows:

1. Convert the current text format license to JSON file format
   
   Example license.json file:
   

   {
        "cmd.license":
   
                 {
   
                      "license_type": "EVALUATION_LICENSE",
                      "licensed_to": "QLIK CUSTOMER",
                      "licensed_by": "Attunity US",
                      "serial_no": "60035964",
                      "expiration_date": "2023-12-01",
                      "hosts": "xxx.xxxx",
                      "source_types": "oracle",
                      "target_types": "target",
                      "features": "yyyy",
                      "version": "2023.11",
                      "issue_date": "2023-10-31",
                      "checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
                  }
   }

   
   
2. Place the JSON format license file (license.json created in step 1) in the Qlik Replicate data/imports folder
   
   Example: C:\Program Files\Attunity\Replicate\data\imports\license.json
   
   
3. Open a Windows Command Prompt as administrator
   
   
4. In the command line, change to the <Installation_folder>\bin directory
   
   Example:
   
   cd "C:\Program Files\Attunity\Replicate\bin"
   
   
5. Run the following command:
   
   repctl importlicense license_file=license
   
   
   
   
6. To confirm the registered license or simply view any currently registered license, run the following command:
   
   repctl getlicense   --help
                

To register a license on Linux:

3. Convert the current text format license to JSON file format
   
   Example license.json file:
   

   {
        "cmd.license":
   
                 {
   
                      "license_type": "EVALUATION_LICENSE",
                      "licensed_to": "QLIK CUSTOMER",
                      "licensed_by": "Attunity US",
                      "serial_no": "60035964",
                      "expiration_date": "2023-12-01",
                      "hosts": "xxx.xxxx",
                      "source_types": "oracle",
                      "target_types": "target",
                      "features": "yyyy",
                      "version": "2023.11",
                      "issue_date": "2023-10-31",
                      "checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
                  }
   }

4. Place the JSON format license file (license.json created in step 1) in the Qlik Replicate data/imports folder.
   
   Example:
   
   /opt/attunity/replicate/data/imports/
5. Change ownership of the license.json file:
   
   chown attunity:attunity /opt/attunity/replicate/data/imports/license.json
   
   
6. Run the below commands from the installation bin folder:
   
   cd /opt/attunity/replicate/bin/
   
   source /opt/attunity/replicate/bin/arep_login.sh
   
   ./repctl importlicense license_file=license
   
   
7. o confirm the registered license or simply view any currently registered license, run the following command:
   
   ./repctl getlicense --help

The Qlik Compose monitoring window takes a long time to load.

This is likely caused by old task entries not being purged from the project's ProjectRepoRuntime.sqlite file. 

ProjectRepoRuntime.sqlite is located in <Instation_folder>\data\projects\PROJECT_NAME
Example (default): C:\Program Files\Qlik\Compose\data\projects\YOUR_PROJECT_NAME              

Resolution 

Upgrade to Qlik Compose 2022.5.0-sp16 (2022.5.1177) or any later version.

After the upgrade, note:

1. The UI performance improvements may not be noticeable immediately, as Qlik Compose deletes a set amount of 500 ghost reference records from ProjectRepoRuntime.sqlite at the end of each successful task completion. Depending on the number of entries that need to be cleaned from ProjectRepoRuntime.sqlite, it can take multiple days before real improvement is seen.
2. Once the UI performance stabilizes, Qlik recommends compressing the ProjectRepoRuntime.sqlite file using a third-party tool such as DB Browser for SQLite.

   It is essential to stop the Qlik Compose service and back up the project folder before compacting the file. Please contact support if any assistance is needed. 

Fixed version

2022.5.0-sp16 (2022.5.1177) and higher

Cause

Recob-7766

Information provided on this defect is given as is at the time of documentation. For up-to-date information, please review the most recent Release Notes with RECOB- 7766 for reference.

While using Databricks Lakehouse (Delta) as a target endpoint, it would be highly beneficial for users to have the option to write data to multiple databases within a single target endpoint connection.

Some specific business use cases involve managing more than 30 databases under a single catalogue. Creating over 30 separate target endpoint connections in Qlik Replicate to handle these databases is a big challenge.

In this article, we will explain the solutions to how we can manage multiple databases within a single connection. The same approach can be used in other common databases, including Databricks (Cloud Storage), Microsoft SQL Server, PostgreSQL, and other similar databases.

Resolution

Changing the Target table schema is the equivalent of changing the specified database name in the endpoint settings.

How to manipulate multiple databases within single connection

In the endpoint definition, specify the "Database" name, this is the default database. In our screenshot example, the default database is named "APACDB".

We may use "schema" to identify the non-default database name, which will write different tables of data to different databases within a single connection.

There are two options, Table level, and Global level:

1. In Table Settings (see Table Settings for details):
   1. Open General
   2. Select Table Schema
2. In Global Rules (see Defining global rules for details):
   1. Click New rule
   2. Go to Transformation
   3. Rename schema 
      
      Define a rule which database should be used for the given table(s). For example, apply a global transformation rule to rename schemas from %.% to $AR_M_SOURCE_SCHEMA:
      
      
      

Environment

Qlik Replicate  all versions
Databricks Lakehouse (Delta) all versions
Databricks (Cloud Storage) all versions

Internal Investigation ID(s)

Support case #00122351

The QlikView server creates a last document state or session recovery bookmark ($LASTKNOWNSTATE) when a QlikView document is closed from the Full Browser Client. This allows work to be resumed, even after the session has been terminated. Sometimes, this session or state needs to be cleared.

Symptoms:

A QlikView document does not open and is stuck in:

Resolution:

The last known document state may be attempting to call an invalid state or object created by the user the last time the document was closed.

To clear this, the end-user needs to click the Remove Last Document State button visible in the View Details menu accessible from a link below the document listed on the AccessPoint.
 

Note that clearing the last document state does not mean the session is reset. If the user is still within an active session and they close and re-open the document, the previous session is resumed. This is not the last document state.

The last document state is a bookmark applied at the end of a session.

For a more detailed description, see Session Recovery in QlikView: How to enable it and how it works.

Qlik Sense works normally, but a huge quantity Repository logs is generated. These following  messages are continuously repeated (not necessarily both of them are present).

In System logs:

INFO SERVERNODE System.Repository.Repository.Core.Repository.Common.ModelRepository`1[[Repository.Domain.Model.UserDirectorySettings, Repository.Domain, Version=xx.xx.x.0, Culture=neutral, PublicKeyToken=...]] 
..... Database object has newer timestamp than object being modified; ....
.... ERROR SERVERNODE System.Repository.Repository.Core.Repository.Common.TransactionUtility 
..... Error when committing 

In User Management logs:

WARN SERVERNODE UserManagement.Repository.Repository.Users.SyncUsersWorker ........  
Conflict when trying to do database operation; retrying... at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵

The quantity of messages generated is very high and several GB of memory can be occupied in disk in few hours.

Environment

• Qlik Sense until February 2021 Patch 6.

Resolution

In order to avoid a complete filling of the disk, it is necessary to restart the node where the problem occurs. Generally, this  resolves the issue.

To avoid this problem, we have introduced an improvement in the latest Qlik Sense releases that avoids potential conflicts. This improvement is present in Qlik Sense February 2021 Patch 6 and in Qlik Sense May 2021 SR1 or higher releases. An upgrade is recommended to ultimately fix the problem.

Cause

The problem  is due to an incorrect synchronization between the Database and one of the nodes.

Internal Investigation ID(s)

SHEND-509

The Qlik Download page or Qlik Ideation app do not show their expected content. The web page and browser console display error messages referring to HTTP 401 Unauthorized access, which may look similar to the below examples. 

• {"errors":[{"title":"State verification failed","detail":"State not valid, missing request forgery protection","code":"STATE-1","status":"401"}],"traceId":"{ID}"}
• VM624:1 GET https://download.us.qlikcloud.com/api/v1/users/me 401
• VM624:1 GET https://download.us.qlikcloud.com/api/v1/csrf-token?qlik-web-integration-id={ID} 401

Resolution

The Qlik Download page and Ideation App on Qlik Community require 3rd party cookies as part of the current web integration. The accessing browser must allow 3rd-party cookies while accessing the Qlik Downloads page in order for the page to render successfully. 

The browser does not have to completely allow 3rd party cookies, but can also just allow 3rd cookies for the *.qlik.com or community.qlik.com domain. 

The cookie settings are browser-specific, please consult browser help for more details. 

Cause

The Qlik Download page and Ideation App in Qlik Community are composed by an embedded object hosted in Qlik Cloud. This means cookies for the user session are associated with two different domains, community.qlik.com and qlikcloud.com. The browser refer to the parent page (community.qlik.com) as a 1st party cookie, while the embedded content from a different domain (qlikcloud.com) is referred to as a 3rd party cookie. 

3rd party cookies may be blocked in a browser as a mechanisms to block user tracking and advertisement. Browser incognito mode may also block 3rd party cookies by default as part of keeping the user more anonymous. 

Related Content

Clear, allow & manage cookies in Chrome 
Third-party cookies and Firefox tracking protection 
Microsoft Edge, browsing data, and privacy 
Clear cookies in Safari on Mac 

QMSEDX is a community-provided customization. Qlik does not provide support or direct assistance for this solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.

EDX is a trigger mechanism for starting a QlikView reload or task from an external source, such as a scheduler or application. To start a task using EDX the QlikView Management API must be used and this is delivered in the form of a Web Service.

QMSEDX is a third-party app designed to perform said mechanism. For more information, see Using EDX in QlikView 11. 

QMSEDX is an open source tool that is developed by CwolfX on sourceforge where you can find more information and maybe support: https://sourceforge.net/p/qmsedx/wiki/Home/ Also keep in minde that as it is an opensource it could have other developers making there version available online, juste make sure to contact the one that made the version you are using

For custom developments. Documentation about QMS API is available at Qlik Help.

Related Content:

QMS API is available at Qlik Help
Using EDX in QlikView 11

Upgrading QlikView fails with the Warning: 

You need a valid maintenance contract to be allowed to install and use this Software

Proceeding with upgrades without an updated maintenance contract will lead to the QlikView Server license being invalidated. The server will enter Off Duty state. 

Attempting to license a QlikView server with an outdated license will lead to 

Server failed to set license: QVS@qlikviewserver: This license key has expired!

Cause

The maintenance data for the license key has expired prior to the release date of the product version you are updating too.

See the Maintenance contract on upgrade for more details. 

Example:

000000000000000
NUMBER_OF_USERCALS;5;;
NAMED_CAL_BY_MACHINE_ID;NO;;
PRODUCTLEVEL;10;;2016-12-30
000000000000000
 

Resolution

1. Verify your license first by reviewing if the LEF includes the correct maintenance date. See How to request a control number and LEF.
2. Update the license on the server prior to the upgrade. See Lef expires or Lef expired displayed in QlikView Management console alert banner on steps to follow.

If the maintenance date is correct and you have attempted to update the license, verify if no old LEF.txt files are stored in your system. See Where do all the QlikView LEF files go? for information on where they are stored. Carry the check out on all nodes if you have a multi node environment. 

If you do not have an up-to-date maintenance date, contact your Qlik Account Manager to renew the license and repeat steps 1 and 2 above.

Issue:

When attempting to connect to a new Direct Access Data Gateway data source within the load script editor of a Qlik Application, the new data connection test fails.

When reviewing the Data Gateway logs at "C:\Program Files\Qlik\ConnectorAgent\data\logs" , the following error is discovered:

ERROR partner 'myremotedataserver.com:3350' not reached"

Environment

• Direct Access Data Gateway

Diagnosis:

• Open windows powershell
• Type: (without quotes and replace xxxx with the port in question)
  • "tnc qlikserver3.domain.local -port xxxx"

Expected Result:

Resolution:

• If the above port test fails following the message 'waiting for connection'  the identified 'blocked' communications port found in the Data Gateway logs must be opened on your network firewall.
• Once the port is opened, retest your Direct Access Data Gateway connection.
• You should now see 'test succeeded '

Cause

• All network ports closed by default in a highly secure network. This including explicitly blocked ports to external data sources (such as SAP SQL connector port 3350), when required for data gateway source data connectivity, must be re-opened on the network firewall
• Ports recently closed due to updated network firewall policy blocking undocumented ports

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

If you want to submit a new idea or improvement request for Qlik's products, our Ideas section in the Qlik Community is open to all registered customers. 

Content:

• Where to find Qlik Ideation
• How to submit an Idea on the Ideation

Ideas are qualified and prioritized based on their value to improving and enhancing the Qlik product. For a successful request, please consider including a strong business case on why you think the change would be beneficial, including:

• Functionality: How does the product work now? How would you like it to work in the future? 
• Motivation: Why is the change important for your business?
• Importance: What is the impact if the feature request is not approved?
• Benefits: What is the impact if the feature request is implemented?

Where to find Qlik Ideation

1. Go to the Qlik Community
2. Log in!
3. After logging in, navigate to Ideation
   1. You can navigate there manually from (a) Ideation
   2. And (b) Browse and Suggest
      
      
      
      
4. Scroll down to locate the Ideation Landing Page / App
   
   
   
   For more information on the Ideation Dashboard and its functionalities, see About Ideation.
   
   
   

How to submit an Idea on the Ideation

Before you get started, review Ideation Guidelines: How to Submit an Idea for submission guidelines and eligibility information.

1. Go to the Ideas Site
2. Click the Suggest Features card
    
   
   
   
3. Provide us with as much detail as possible, including a descriptive subject and description.
4. Choose the appropriate Product Area.
5. And click Submit request.
   
   

Ideas and Improvement requests are reviewed by our product teams. While we strive to provide answers, we cannot guarantee a specific response time.  

Related Content:

Ideation on Community  
Ideation Platform Updates
Ideation Guidelines: How to Submit an Idea

After upgrading from Windows 10 to Windows 11, or applying certain patches to Windows Server 2016, Qlik Replicate may not load in the browser.

The following error is displayed:

ERR_SSL_KEY_USAGE_INCOMPATIBLE

Environment

Qlik Replicate 2022.11 (may happen with other versions)
Qlik Compose 2022.5 (may happen with other versions)
Qlik Enterprise Manager 2022.11 (may happen with other versions)
Use of the self-signed SSL certificate
Windows 11
Windows server 2016

Resolution

This issue has to do with the self-signed SSL certificate. Deleting the existing one and allowing Qlik Replicate/Compose/Enterprise Manager to regenerate them resolves the issue.

1. Stop the services for all affected software. Example: AttunityReplicateConsole and QlikReplicateServer as well as Qlik Compose or Qlik Enterprise Manager
2. (This step only applies to Qlik Replicate) Rename the data folder under the SSL folder (\Program Files\Attunity\Replicate\data\ssl\data)
3. Delete self-signed certificates in the management console
   1. Open a command prompt and enter MMC to open the console
   2. Click the File drop-down menu and select Add/Remove snap-in
      

      
      

   3. Select Certificates and click Add
      

      
      

   4. Select Computer account. Click Next, then click Finish.
      
      

      

   5. Click OK to close the Add or Remove Snap-ins window
   6. Open Certificates and navigate to Local Computer, then Personal, then Certificates
      
      

      

   7. In the list of certificates shown, select the certificates where the "Issued To" value and the "Issued By" value equal your computer name and delete them.
   8. Close the Management Console.
      
      
4. Next we will remove the reference to the self-signed certificate in Qlik Replicate:
   
   
   1. Open a command prompt As Administrator
      
      For Qlik Replicate:
      
      Navigate to the ..\Attunity\Replicate\bin directory and then run the following command:
      
      RepUiCtl.exe certificate clean
      

      
      
      
      For Qlik Compose:

      Navigate to the ..\Qlik\Compose\bin directory and then run the following command:
      
      ComposeCtl.exe certificate clean
      
      

      For Qlik Enterprise Manager:

      Navigate to the ..\Attunity\Enterprise Manager\bin directory and then run the following command:
      
      aemctl.exe certificate clean
      
      
   2. Run the command: netsh http delete sslcert ipport=0.0.0.0:443
      
      Note, you may get a message that the command failed in the event there are no certificates bound to the port. This message can be ignored.
      
      
5. Restart the services.
   
   This will create a new data folder underneath the ssl folder for Replicate and generate a new self-signed certificate for all affected applications. You can delete the folder you renamed in step 2 above.

Qlik Replicate will now allow you to open the user interface once again.

If users still cannot log in and are returned to the log in prompt at each attempt, see How to change the Qlik Replicate URL on a Windows host.

Related Content:

How to change the Qlik Replicate URL on a Windows host 

This article explains how to save network logs in web development tools and the console logs from the browser and how to capture and read client-side response trace with HAR file analyzer.

For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.

Environment:

• Internet Explorer / Edge browser
• Google Chrome browser
• Mozila FireFox browser
• iPad/iPhone and Safari

Google Chrome and Microsoft Edge (new Chromium version):

1. Open developer tools (Menu > More tools > Developer tools or Ctrl + Shift + I or F12)
2. Select the Network tab.
3. Make sure that "Preserve log" is checked so that all traffic is captured.
4. Access or refresh the page traffic needs to be captured for or a problem should be reproduced in
5. Perform the steps to cause the behavior/issue
6. Click on the down arrow "Export HAR..." button or Right-click within the Network capture pane then choose 'Save as HAR with content' and save the .har capture locally.
7. Click on the Console tab > right-click > Save As > Save on the .log file. (Important)

To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/

Firefox (41+) :

1. Go to Menu > Web Developer > Network
2. Reload the page you want to get the log for
3. Perform the steps to cause the behavior/issue. 
   Note: For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.
4. Right-click > Save All as HAR
5. Click on Console tab, Right-click > Select All.
6. Right-Click > Export Visible Message To > File, and save on a .txt file. (Important)

Internet Explorer and Microsoft Edge (older versions):

1. Open Developer Tools (F12)
2. Go to the network tab and click on the green arrow to start the tool
3. Refresh the page to capture the logs
4. Perform the steps to cause the behavior/issue
5. Note: For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.
6. Click 'Export captured traffic' icon and choose XML or HAR format.
7. Click on Console tab > right-click > Copy All, and paste it / save on a .txt file. (Important)

To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/

iPad or iPhone Safari:

1. On the iPad or iPhone, open the Settings app and go to Safari, Advanced. Enable the Web Inspector.
   
   
   
   
2. On the Macintosh, launch Safari --> Preferences --> Advanced --> Show Develop menu in tab bar
   
   
   
   

Further Troubleshooting

1. On the iPad/iPhone, access the QlikView / Qlik Sense site you are having issues with
2. On the Mac, launch Safari --> Develop menu --> pick the name of the iOS device and select the site to inspect.
   
   
   
   
3. The Web inspector will launch. Select Networking and then, on the iOS device, start reproducing the issue.
   
   
   
   The Web Inspector can be used not only with iOS devices, but also with the iOS Simulator for Mac.  Please, check the "How to simulate iOS Safari on a Mac" article.

Upgrading Qlik Sense Enterprise on Windows with a standalone PostgreSQL database to August 2023 or later fails. The installer does not return an error on-screen.

A Qlik Sense Enterprise on Windows environment can have a bundled PostgreSQL database or a standalone database.

If your Qlik Sense environment has relied on a standalone PostgreSQL database since its initial setup, and still has its PostgreSQL 9.6 database and binaries, additional steps are required to prepare for an upgrade to any versions beyond Sense August 2023. 

These binaries will be in the following folder: 

C:\Program Files\Qlik\Sense\Repository\PostgreSQL\version number

Where version number is 9.3 or 9.6. 

The old binaries need to be uninstalled and new binaries installed (on all nodes).

Applies to:

Qlik Sense August 2023 and higher as the target version
Qlik Sense May 2023 and lower as the source version

Resolution

Before proceeding with an upgrade:

1. Remove the 9.6 binaries for Postgres
   
   
   1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
      
      
   2. From there, search for PostgreSQL.msi
      
      

      
      The msi will be revealed.

   3. Right-click the msi file and select uninstall from the menu.
      
      

       

2. Install the 12.5 Postgres binaries
   
   
   1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache
      
      
   2. From there, search for either PostgreSQL14.msi or PostgreSQL14.msi
      
      Qlik Sense August 2023 and later: PostgreSQL14.msi
      Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
      
      

      
      The msi will be revealed.

   3. Right-click the .msi file and Open File location 
      
      
   4. Open a Windows Command Prompt as administrator
      
      
   5. Copy the path to the .msi file and navigate to it in the Command Prompt
      
      Example: 
      
      cd C:\ProgramData\Package Cache\{GUID}
      
      
   6. Run the following command, replacing PostgreSQL.msi with the correct .msi depending on your previous version used.
      
      Qlik Sense August 2023 and later: PostgreSQL14.msi
      Qlik Sense February 2022 to May 2023: PostgreSQL125.msi
      
      msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"
      
      This will re-install the binaries without installing a database.
      
      
3. Verify if old PostgreSQL binaries still remain in one of the two folders:
   
   C:\Program Files\Qlik\Sense\Repository\PostgresSQL\version number
   
   If 9.x directories remain in this folder, reboot the machine, then repeat the uninstall steps.
   
   C:\Programdata\Qlik\Sense\Repository\PostgresSQL\version number
   
   If 9.x directories remain in this folder, Qlik Sense was previously run with a bundled database. The directories can be safely renamed.
   
   
   

Cause 

The upgrade will be blocked when a 9.6 or 9.3 database binary folder is found. These folders can be in either:

C:\Programdata\Qlik\Sense\Repository\PostgresSQL\version number  
C:\Program Files\Qlik\Sense\Repository\PostgresSQL\version number

The CPU affinity is not working as expected. The number of CPU affinity for the QVS does not match the cores in the Server.

Environment:

QlikView 
Generation 9 HP servers

 

This issue comes from a new BIOS setting introduced in Generation 9 of HP servers.  A new setting has been added in BIOS that needs to be modified to allow the QlikView services to properly detect all the CPU Cores in the machine.

This can be resolved by changing the BIOS setting "NUMA Group Size" to "Flat". The default setting for "NUMA Group Size" disables QlikView from properly detecting all CPU cores in the hardware.

In this Webinar, we covered how to approach a Qlik Sense Enterprise on Windows migration.

The session covers:

• How to Back-Up and Restore
• Managing Certificates
• Potential Pitfalls
• Automation Options
• If assistance is needed, Qlik Consulting would need to be engaged. Qlik Support cannot provide walk-through assistance with server migrations outside of a post-installation and migration completion break/fix scenario.

Resources and Related Content:

Qlik Sense Migration: Migrating your Entire Qlik Sense Environment (Blog post)
Help.Qlik.Com Documentation: Backup and Restore Qlik Sense Enterprise on Windows
Qlik Sense Upgrade Guide
Qlik Admin Playbook

Q&A:

Q: Is it possible to migrate from a standalone installation to a clustered one? 
A: Yes. Once the Central Node has been moved to a new host, additional Rim nodes can be added as usual through the QMC. 

Q: What about the personnal objects created by users (sheets, bookmarks, ...) ?  Are they included in the QSR backup ? 
A: All user objects as well as base sheets are included both in the Apps themselves as well as in the QSR. 

Q: Is this possible to migrate one repository to another server and merge the repository with another one? 
A: Not through the procedure outlined in this webinar. If your goal is to merge content from multiple sites, or seamlessly migrate content, I recommend reaching out to your Account Manager and discuss Qlik Mission Control platform. 

Q: Would the steps given here change if postgres is installed on a stand-alone server?
A: The only steps that would change would be the backup/restore for the DB itself, as this would have to be performed locally on the DB host. Additionally, if the DB location has changed, the QRS connection strings will have to be updated via QlikSenseUtil. 

Q: Is it necessary to have the same release on both servers before migrating ? Or is there compatibility between versions of QlikSense ? 
A: You can restore a database from a previous version on a newer Qlik Sense release and the system will update the internal objects automatically, however the reverse is not possible. It is recommended to perform the upgrade in place, before migrating the server. 

Q: Is it possible to restore without certificate ? 
A: Yes, Trust Root and Qlik Client certificates can be recreated from scratch, however as mentioned during the call, all internal metadata values that were previously encrypted, such as data source connection strings, would have be updated via the QMC by re-entering the connection password and saving.