Replicate Error for oracle source endpoint:

ORA-01801: date format is too long for internal buffer.

Cause 

The date format string was too long to process. This should occur only if several long literals are specified as part of the date at the source.

Resolution

Remove long literals from the date format string.

Identify the exact record which is causing the issue on the database side by, fo example using cqlplus utility to scan a particular column.

Related Content 

ORA-12899: value too large for column 

Environment

• Oracle as source endpoint for Qlik Replicate 

This article lists the resolution and troubleshooting steps that must be followed if images are not rendered correctly in Qlik NPrinting reports.

NOTE: Before proceeding below, please check this article

• NPrinting Qlik Sense Images Fail to Render Export Generate or Preview

Troubleshooting Steps:

Image export failures may be due to some configuration errors. The following must be checked:

• Insufficient system resources: Low Qlik Sense, QlikView and NPrinting System resources can cause this issue. Please do performance monitoring to check for Peak CPU and RAM usage that on all NP QS and QV servers. NPrinting has the ability to exhaust a production Qlik Sense or Qlikview server if those servers are not sufficiently provisioned with enough RAM in particular. https://community.qlik.com/t5/Official-Support-Articles/Finetuning-and-preparing-your-NPrinting-202x-Deployment-for-use/ta-p/1716222
  • It may be useful to Enable performance logging on the NP, QS and or QV servers to verify if it is being heavily taxed while NPrinting reports and or report publish tasks etc are being executed. Qlik Sense - How to monitor resources using Microsoft Performance Monitor 

• Assistance/suggestions mode for the Qlik Sense charts is not supported. Ensure it is disabled for all the objects imported in the report.

• The imported object ideally will be a native Qlik Sense chart object. 3rd party extensions may result in unexpected results. Contact your extensions vendor for 3rd party extension support

• Certain Qlik Sense visualizations from the visualization bundle are not supported: See compatibility matrix here:
   Creating a visualization using a custom object

• For a listing of compatible, built-in Qlik Sense objects, check the compatibility matrix found in the following link to better understand specific Qlik Sense object limitations with NPrinting reporting. 
  Working with Qlik objects

• Please check and validate minimum cipher requirements on the Qlik NPrinting and Qlik Sense server. See NPRINTING ERROR CEF RENDERING EXCEPTION Cipher Issue

• Check that the internet options/proxy settings are cleared as per article:
  NPrinting Issues to generate report and previews, connect to Qlik Sense apps, image and objects issues and on demand issues

• Check that Qlik NPrinting Engine and Server Internet Options are configured. See:
  How to Configure NPrinting Server and NPrinting Engine computer Internet Options

• Check that 'In' and 'Out' bound ports between the Qlik NPrinting server Qlik NPrinting engine and the Qlik Sense server are configured. Keep in mind that Ports 4997 and 443 must now also be configured since November 2018 release of Qlik NPrinting.

• Check that ports 2727 and 15672 are not being used by any other process/program on the NPrinting server and engine computers. These ports are required for normal NPrinting operation. See Ports - Qlik NPrinting

• Check that the Qlik Sense objects and or Qlik Sense visualization used in your NPrinting report are supported as per the "Keep in Mind" section above

• Check if HTTP is used in the Proxy field of the Qlik NPrinting Connection to the Qlik Sense app in the 'Proxy Address' field. If yes, see article
  NPrinting Unexpected CEF rendering exception with HTTP connection

• Check that the Qlik Sense Proxy default 'https://' listening port settings has not been changed.  Open the following link for more information:
  NPrinting Designer CEF Rendering error and or Error Object reference not set to an instance

• Check for the use of a Qlik Sense proxy 'prefix' in the Qlik Sense Management Console. If one exists, via the NP web console, the prefix must be added to the NP connection string ie: https://qlikserver1.qlik.com/qlik

• Check to see if anything has been entered into Additional Response Headers under the Qlik Sense Virtual Proxy being used (select Advanced to view), if so remove and test.

• Check the Qlik NPrinting logs for 'Websocket' errors. If found check this article to resolve that issue.
  NPrinting Engine connection stays offline on February 2019 release and newer - RabbitMQ log shows "Insufficient Security no_suitable_ciphers"

• Abort all running Task and On Demand Task executions then reboot the Qlik NPrinting Server, Qlik NPrinting Engine computer and the Qlik Sense server at the first available opportunity and retest if the issue still persists. Ensure all services on each computer are up and running before retesting.

If the issue persists after checking all points above, please check the solutions in the resolutions section of this article.

Resolution steps:

Resolution 1

Fully Qualified Domain Name path or some other parameter of the original Qlik Sense server certificates may have changed. Use the following article to resolve this issue: NPrinting Verification process does not capture certificate FQDN mismatch in turn resulting in GRPC errors

1. Open windows File Explorer
2. Click 'View' tab
3. In 'Show/Hide' area of the 'View' ribbon, Click checkbox "File Name Extensions" in order to show the full file name

Resolution 2 

GRPC error: Check NP CEF Engine log file: May be represented by the error: "The remote server returned an error: (401) Unauthorized" . (Internal JIRA defect reference: OP-8814)

• Check that the path to the QMC proxy is the same as the connection path used in the NP connection proxy address path.
• You must also ensure that port 443 and port 4997 are not blocked in your environment as mentioned in the article description.

Resolution 3

If the NPrinting Error logging or preview errors contain the message "CEF rendering exception - "Buffer cannot be Null" go to the following article for the solution: CEF rendering exception - "Buffer cannot be Null" Error in NP report preview with Qlik Sense Connection"

Resolution 4

If Resolution 1 and 2 above do not resolve the issue and all image export requirements are met, check and perform the steps below:

1. Stop the NPrinting Engine Service.
   
2. Open the renderer.config file in C:\Program Files\NPrintingServer\NPrinting\Scheduler. You may need to open the file in administrator mode.
3. Make a backup copy of the file.
4. Add (or modify if present) the following parameter:
   <add key="webrenderer-timeout-sec" value="120" />
   120 is the time in seconds for the timeout. It can be increased up to 300 if necessary and retest.
5. Restart the NPrinting Engine service

Increasing these timeout values may lead to improved performance as NPrinting may simply need more time to execute tasks and report generation. These changes also need to be made after an NPrinting upgrade. NP Config files are overwritten during the upgrade process.

How to Enable 'Logging'

If resolutions above have not resolved the issue, please perform the following steps and reproduce the issue one again in order to retrieve debug logging necessary for a deeper investigation. Then zip and upload the requested debug logs below up to the support case. 

• Enable debug logging as per Troubleshooting logs - Qlik NPrinting

Causes:

Possible causes of GRPC error

• assistance/suggestions mode is enabled (it is currently on the road map to have this feature fully supported)
• the chart is an unsupported 3rd party extension (map extensions for example). See article below regarding Qlik Sense extensions and how to enable them for image export.
• In some cases, image web rendering default time while connected to Qlik Sense needs to be adjusted perhaps due to network latency or other network performance related issues
• Communication between the NPrinting server and the Qlik Sense server is discovered to be problematic.
• The Qlik Sense server itself could be overloaded and not responding to the NPrinting server in a timely manner.
• When NPrinting is used in conjunction with Qlik Sense Deployments From September 2018 and higher where "HTTP" is used rather than "HTTPS", specific CEF or GRPC errors will be logged. See article Qlik NPrinting Unexpected CEF rendering exception with HTTP connection for more information.
• Certificate mismatch as identified in article NPrinting Verification process does not capture certificate FQDN mismatch in turn resulting in GRPC errors
• Invalid path used in the NP connection 'proxy' address path. Path used with the NP connection should be the same as the path used to open the QMC or QS Hub
• Error logging to look for NPrinting Logs: "Failed to open a resolver for connection" and "The remote server returned an error: (403) Forbidden"

Reference: 

Creating visualizations using chart suggestions
Enabling export of your visualization extension
Using Qlik Sense third-party extensions

The following steps outline a test Multi-Cloud App distribution setup in QlikView Server where applications are distributed to Cloud Hub on Qlik Cloud (Qlik Sense Enterprise SaaS).

Note that starting on the April 2020 release and newer, re-distributions of apps have persistent Cloud Hub Space assignment. Meaning once an App is assigned to a Space by a tenant admin, it will remain assigned to that specific Space after the app is reloaded or edited, then re-distributed to the Cloud Hub(s).

Environment

• QlikView , April 2020
• Qlik Cloud 

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.

Note: Steps covered on the video and some additional information are found below:

1. Connecting QlikView Server to a Qlik Sense Enterprise cloud deployment:

After adding the new Deployment via Qlik Management Console (QMC), under the General tab, copy the generated Local Bearer Token (Copy to clipboard). This will be pasted when setting up the Multi-Cloud Identity Provider in Qlik Sense Enterprise SaaS (QSE SaaS) using Qlik Cloud Services format. 

2. Adding the bearer token to the Qlik Sense Enterprise Cloud Hub:

Login to the Management Console and under Identity Provider, create a new Multi-Cloud type provider for the QlikView Cloud Deployment connection. Then paste the Local Bearer Token previously copied above.

3. Publish a QlikView document or a link to the document in a Qlik Sense cloud hub:

Make sure to have Distribute to Cloud-Native and/or Distribute Link selected, with the correct created Deployment selected. If distributing the document link, a QlikView Server also needs to be added under Distribute to QlikView Server. As an option, the app can have Tag values associated in order to control App access in Cloud Hub.

4. Now the task can be run by right-clicking it on the left pane > Run, and the status and logs can be checked under Status > Tasks. Deployment logs are the same as for Task and and QDS. (see How To Collect QlikView Server Log Files

5. Now the app should show up in the Qlik Cloud Console under Apps, and can be assigned to a Space.

6. Note that with QlikView Cloud Deployments, if the document/app or Link needs to be removed from Cloud hub, it needs to be deleted manually. This is not the case with Qlik Sense Multi-Cloud Deployments where the app is removed by removal of associated Deployments custom property value. More information under Example Multi-Cloud App distribution setup in Qlik Sense

7. Tags assigned to the app can be seen in the App's Details information in Cloud Hub > Explore > ... > Details

Related Content

• Example auth0 authentication setup on Qlik Cloud Services
• Setting Up Qlik Sense Enterprise Multi-Cloud or a SaaS edition
• Qlik Multi-Cloud Frequently Asked Questions (FAQ)
• Publish QlikView documents and links in a Qlik Sense cloud hub
• How to configure Unified Hub and publish QlikView document links in Qlik Sense Hub

A backfill sync is a process that syncs historical data from a source to a target.

When performing a backfill sync, the total amount of records that need to be synced between multiple systems is split over multiple blend runs. This allows the total sync to take longer than the maximum execution time of a single blend run.

In this article, scheduling will be used to execute a single blend multiple times.
It would also be possible to build a solution with a triggered blend that calls itself, but this is more error-prone as a failed blend execution can break the chain.

Backfill patterns 

Scheduled blends 

When building backfills, a scheduled blend offers 2 advantages over a triggered blend:

1. other scheduled and triggered blends won't be blocked by the partial sync
2. a failed run won't impact the schedule and a retry strategy can be implemented

The downside of using a scheduled blend is that it might take longer, the shortest possible interval for the schedule is 30 seconds. If there are many syncs that have to process an empty range of records, some time will be lost on these syncs.

1. Setting the schedule

Set the template to run in "scheduled" run-mode. As long as the schedule is set, the blend will keep executing according to it.

When the sync is finished, the schedule needs to be disabled.
This can be done by executing the "Update Blend" block with the "Schedule every" parameter set to "Disabled". Combine this block with a condition block that checks if the sync has finished.

2. Dividing records and storing a state

The total amount of records needs to be split over multiple blend runs. And each blend run will need to know the current state of the sync. In other words, which part of the records it should process.

How this is done depends on the available list blocks for the connector belonging to the platform where data is fetched from. Our Shopify connector will be used as an example as it has all 3 types of list blocks.

2.1 Incremental block

If an incremental block is available, the pointer can be set using the "Set Pointer" block. This pointer is stored in the Blendr backend so there's no need to worry about storing the state. To prevent the incremental block from fetching all records, set the "Maximum numbers of items to retrieve" parameter in the block's settings tab to the number of records each run should process.

This approach only works if the records are returned sorted from old to new.

After all records for a certain run are processed, use the"Update Pointer" block to change the pointer to the timestamp from the newest record returned by the list incremental block.

2.2 Search block

For an example, see the attached file: Shopify scheduled backfill sync - search block.json

How to import a blend from a JSON file 

A search block is a block that allows you to retrieve a list of records with a certain query. This can be an SQL-like query or some predefined fields. The block can be used with multiple strategies, this article focuses on a time window strategy. This consists of fetching records between two timestamps for example, "timestamp_min" and "timestamp_max". These timestamps define the time window.

Time window

The size of each batch is defined by the time between the timestamps that make up the time window, this should be a fixed value, for example, 5 days or a couple of hours. This depends on the "density" of the data.

To keep track of the current batch that needs to be processed (the state of the backfill), one timestamp should be saved in the CDP or Data Store. The other timestamp can be determined by adding or subtracting the time window size. The formula {blendguid} can be used as a unique identifier to scope variables to their template. During development, this will be parsed into the template's GUID. After a user installs the template, it will be parsed into the GUID of that specific installation.

When processing records from new to old, save the pointer in the CDP (or Data Store) during the setup flow. Use the "Date" formula with "now" as input time to generate a datetime string for the time of the template's installation.

The first steps of the template's main flow will be to fetch the state from the CDP or Data Store and define variables for the timestamps that make up the time window. In the included example, these variables are called "WindowStartDate" and "WindowEndDate".

Casting these values to clearly named variables will lower the template's complexity and will make it easier to use them later on in the backfill sync.

When performing the backfill from new to old, WindowEndDate will be set equal to the saved pointer. WindowStartDate will be set to the pointer minus the time window size.

Once these variables are defined, they can be used in the search block.

Other strategies

There are many other possible strategies to split the records into batches when using a search block. This will differ from connector to connector as not all APIs have a search endpoint. Please contact our support team if a connector is missing a search block (that should be available according to the API documentation).

2.3 Regular list block

If for a certain connector an incremental list block and a search block are both not available. A regular list block is the only possibility. This approach is not efficient and can take a long time.

The strategy is to store the ids of every processed record. After fetching a new batch of records, compare the ids of those records to the ids of already processed records by using the "Compare Lists" block.

This approach will take a long time and the "Compare Lists" block might take too long to run on big lists. 

3. Implementing a retry strategy

3.1 Manual retry

Optionally an inputs field can be included in the settings flow with additional parameters like

• a final date, records older than this date will be ignored
• a custom start date, records younger than this date will be ignored

The custom start date can be used to restart the full sync from a point in time different than the moment of installation. It's even possible to retry a specific time window by specifying both a final date and a custom pointer. 

3.2 Auto retry

Add a new variable "max_retry" to the CDP or Data Store and assign a numeric value to it. This equals the number of times the blend should retry a run if an error is encountered.

Error handling 

Go in the settings tab for each block that could cause an error and change "On Error" to "Warning". After each of these blocks, catch a potential error with a condition block. Retrieve the max_retry variable, if it's greater than 0, subtract 1 and stop the blend without updating the pointer in the CDP or Data Store. This will cause the next run to use the same time window. If the max_retry variable equals 0, update the pointer in the CDP or Data Store and use an alerting connector (for example, email) to notify a user or your services team that a portion of the backfill has failed for a certain time window.

Reset the max_retry variable and stop the blend. Optionally, store the information of failed runs in a new variable and send only one notification of all incomplete runs.

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.

Related Content

Backfill patterns 

Method 1: From the Data Sources

1. Open the Qlik Analytics Service
2. Select  Catalog 
3. Pick your Space 
4. Click Space Details then
5. Select Data Files from the context menu
   
   
   
   
   
6. Locate the data you wish to delete
7. Click the ellipses to open the next menu
8. Click Delete
   
   
   
   
   
9. Alternatively, add /data at the end of the URL.

Method 2: From the Data Load Editor

1. Open the App with a connection to the data files you wish to edit
2. Go to Data Load Editor
3. On the Right Side of the Data Load Editor under add data section select your data space.
4. Click on the table icon under datafiles.
   
   
    
5. select the Delete option on the right side of each file that you want to delete.
   
   

Environment

• Qlik Sense Business 
• Qlik Cloud 

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.

When configuring the mail server in Qlik Alerting, the following symptoms are all experienced:

• "Internal Server Error" in the web interface
• "409" error in the browser's developer tools

• Log files contain a : Global   ERROR   {"stack":"Error: 10716:error:1425F102:SSL *routines:ssl_choose_client_version:unsupported protocol:*[c:\\ws\\deps\\openssl\\openssl\\ssl\\statem\\statem_lib.c|file:///C://ws//deps//openssl//openssl//ssl//statem//statem_lib.c]:1958:\n","message":"10716:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:[c:\\ws\\deps\\openssl\\openssl\\ssl\\statem\\statem_lib.c|file:///C://ws//deps//openssl//openssl//ssl//statem//statem_lib.c]:1958:\n","library":"SSL routines","function":"ssl_choose_client_version","reason":"unsupported protocol","code":"ESOCKET","command":"CONN"}

Using another software on the same machine, it's possible to send emails via the same mail server.

Environment

• Qlik Alerting  February 2021

Resolution

Upgrade to Qlik Alerting May 2021 (upcoming) to solve this.

Cause

This is an issue on Node.js handling of TLS connections, we added an improvement on Qlik Alerting May 2021 to solve this.

Internal Investigation ID(s):

QIAB-366

Unable to Start the Qlik Sense Services in Services.msc due to:

Error 1068: The dependency service or group failed to start 

Environment

• Qlik Sense Enterprise on Windows All Versions

Resolution

1. Check the dependency of the services in Services.msc and start the services accordingly.
2. Right-Click on the Service which is throwing the error -> Properties -> Check Dependencies Tab
   
   
   
   
3. Use a service account (with local admin rights) to run the services in Services.msc
4. Check the Service account if it has 'Log on as a service' rights
   
   Launch local group policy editor by running gpedit.msc from Run command(Windows+R), browse to Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> User Rights Assignment. Find 'Log on as a service' and make sure this account is added. If not, it definitely needs this privilege to run the services that you're trying to start.
   
   
   
5. Try to update/Verify Service Account credentials for that service throwing the error in Services.msc
   
   
   
   
6. Qlik Sense should be installed on Windows Servers not on Windows XP/7/10 etc.
7. Last resort - Repair or Reinstall(Try to Repair first)

As of Replicate 6.5, when working with Oracle endpoint using Attunity log reader to access redo log the following grant is required for capturing RESETLOGS operations: 

Grant SELECT ON V_$DATABASE_INCARNATION 

If Replicate detects that the user sepcified in the endpoint setting does not have the required permission, a warning will be written to the log and the task will continue as normal.

However, when replicating from a RAC environment and/or capturing RESETLOGS operation, not setting this permission may result in data loss and may cause the following error to be written to the log: 

]E: Cannot find any Archived Redo log in the current incarnation (probably, the provided destination id is incorrect), thread ..

Resolution

To solve this error you can either add the missing premission i.e.: 

Grant SELECT ON V_$DATABASE_INCARNATION

or

turn off the supportResetLog option. i.e. :

- Go to Oracle source endpoint --> Advanced tab --> scroll down to the internal parameters

- on the text box please add the following : supportResetLog

- Uncheck the box

When replicating from MS SQL  Always On Availability Group endpoint and facing a problem of Replicate unable to establish connection to replicas with the following error: 
Failed to connect to replica 'XXXXXXXX\YYYYYY'
RetCode: SQL_ERROR SqlState: 08001 NativeError: 2 Message: [Microsoft][ODBC Driver 17 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [2]

[SOURCE_CAPTURE ]T: sqlserver_src_set_odbc_connection_string(): connection string (without credentials): 'DRIVER={ODBC Driver 17 for SQL Server};SERVER=XXXXXXXX.ZZZZ.net;DATABASE=dbname;Trusted_Connection=no;' (sqlserver_endpoint_util.c:222)

Resolution

Problem is caused by wrong alias setting on the AlwaysOn Availability Group

The name of the alias needs to be XXXXXXXX.ZZZZ.net for connecting to replica XXXXXXXX\YYYYYY.