This article describes how to resolve the NPrinting connection verification error:

x Qlik NPrinting webrenderer can reach Qlik Sense hub error

Environment

• NPrinting: all versions
• Qlik Sense: all versions
  • multi-node QS proxy environment
  • NLB (Network Load Balancer or Alias URL) server address used in front of cluster of Qlik Sense proxy nodes (which are linked to a Virtual Proxy. Proxy nodes will not work with NPrinting unless they are linked to a QS virtual proxy)

Resolution

• Although it is possible to use an NLB address in front of your QS proxy nodes that are used by NPrinting, the error generated in the NP connection verification process will appear as described in the article title
• This error can safely be ignored as this does not affect generation of NPrinting connections
• To eliminate the 'error' message, you would need to update your NPrinting connection to use a virtual proxy node address/computer name behind the NLB address . It must be the computer name and not an alias url).
• The proxy node used must be linked to a virtual proxy with the following required attribute
  
  • Microsoft Windows NTML authentication on the Qlik Sense proxy. (SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections).
  • A link between the proxy node and virtual proxy.
  • For all NPrinting to Qlik Sense requirements visit https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#anchor-1

Related Content

• https://help.qlik.com/en-US/nprinting/Content/NPrinting/Troubleshooting/Verify-connection-to-Sense-errors.htm
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#Requirem

Internal Investigation ID

• QB-2871

The reload history found in the Catalog (1) > App menu (2) > Schedule (3) > History (4) > does not display results of manually initiated reloads.

Resolution

To review manual triggers:

1. Go to the Catalog
2. Click the App menu (...)
3. Open Details
   
   
   
   
4. Open Reload History
   
   

Improvements to this section of the tenant UI are planned for the future. No details or estimates can be provided as of now.

Cause

This is a current limitation. Only reloads triggered on a schedule will be displayed in this section of the tenant UI.

Environment

• Qlik Cloud Analytics

A scheduled reload using Qlik Data Gateway fails with the following error:

Internal error. (Connector error: Unknown reason:. Connector process started but gRPC server failed to initialize after 3 attempts (DirectAccess-1500)) The engine error code: EDC_ERROR:22013

Manual reloads may work as expected, but scheduled reloads continue to error out. 

Resolution

The error indicates a resource shortage.

Increase the Qlik Data Gateway VM server CPU and RAM to meet the system requirements. See System prerequisites for details. 

Environment

• Qlik Cloud Analytics
• Qlik Data Gateway

This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.

Authentication and Authorization

To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:

• Mail.Send
• User.Read
• Offline_access

Sending Email with the Microsoft Outlook 365 connector

The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.

The following parameters are available on the Send Email block:

• To: A comma separated list of recipients;
• CC: A comma separated list of recipients to which the email should be copied;
• BCC: A comma separated list of recipients to which the email should be blind copied;
• Subject: A title for your email;
• Type: Choose between plain text email or HTML;
• Body: The content of your email. You can use HTML for your email if chosen as the type.

Generating a report and sending an email with the report

As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.

Environment:

Qlik Automate 

The claims can be accessed via an API Endpoint:

For User claims: 

Please log out of the tenant and re-authenticate using the new identity provider connection. Once logged in, change the URL in the address bar to point to https://<tenanthostname>/api/v1/diagnose-claims  This will return the JSON of the claims information of your IDP sent to the tenant. Here is a slightly redacted example:

Explanations of the different sections in the diagnose-claims endpoint:

• internalClaims: Summary of the user in Qlik Cloud. Usually derived from the IDP claims, but also contains information specific to Qlik Cloud access control (like the user’s roles).
• claimsFromIdp: The raw claims received from the IDP. For Azure AD, most likely this comes directly from Azure AD’s ID token, however groups from the ID token are not imported to Qlik Cloud, the Microsoft Graph API is used to retrieve them instead.
• extraClaims: This section only applies to Azure AD at the time of writing this article, since groups are fetched from Microsoft Graph API. If groups were retrieved correctly from Microsoft Graph API , they will be shown here.
• mappedClaims: Applies the extra claims mapping on top of the raw IDP claims to get the final set of claims used for the Qlik Cloud user.

For Group Claims:

Once logged in, change the URL in the address bar to point to https://<tenanthostname>/api/v1/groups  This will return the JSON of the claims information of your Groups sent to the tenant.

Environment

Qlik Cloud 

The information in this article is provided as-is and to be used at your 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.

Feature requests are submitted to Qlik through our Ideation program, which is accessible via the Qlik Ideation Portal and is available for registered Qlik customers.

What would be applicable as a feature request for Qlik Stitch? 

• Certain fields you need are available through specific integrations, but are not currently supported by Stitch.

• You're looking for additional flexibility or functionality in Stitch that isn’t yet available.

If either of these applies to you, we’d love to hear from you! 

For instructions on submitting an idea or proposing an improvement, see How To Submit an Idea or Propose and Improvement For Qlik Products.

Environment

• Stitch 

If you notice certain fields not receiving data from a specific date onward, or if data replication unexpectedly stops for some fields, it may indicate a potential data discrepancy issue. However, before diving into investigation or troubleshooting, it's crucial to first confirm whether a discrepancy actually exists.

First To Go

To confirm whether a discrepancy exists, you will need to check the following things.

1. Please confirm that these fields contain non-Null values in your source data. The reason we ask is that Stitch will only create a column on your table downstream once at least one value is returned for that field. Empty column can not be replicated to the destination because stitch cannot identify what is the data type of this column.
2. When data is deemed incompatible by the destination, the record will be “rejected” and logged in a table called _sdc_rejected. What looks like missing data may actually be a compatibility issue. If you’re missing data, the first place you should look is in the _sdc_rejected table in the integration’s schema. Please refer to stitch documentation rejected-records-system-table for more info on this table and how to use it to troubleshoot.
   

   Stitch will create the _sdc_primary_keys even if none of the tables in the integration have a Primary Key. Primary Key data will be added to the table when and if a table is replicated that has a defined Primary Key. This means it’s possible to have an empty _sdc_primary_keys table.

3. If the missing records were created very recently, or if Stitch is replicating a large historical data set, you may need to wait for an update of your data to be completed before they appear in your destination.

If you are not in all of above situations, please feel free to contact Support for further investigation or troubleshooting.

Related Content 

To follow the standard procedures for data discrepancy issues, please kindly provide the relevant information according to our document here:

data-discrepancy-troubleshooting-guide

Environment

Stitch 

The status of the Qlik NPrinting Engine consistently appears as Offline on the Engine Manager page.

The Qlik NPrinting Engine Logs read:

RabbitMq server is not connected - trying diagnoser queue creation again in 5 seconds
Qlik.NPrinting.Engine 24.4.14.0 Qlik.NPrinting.Engine.EngineService 20250521T190411.917+05:30 
ERROR NBHI-DC-APP-69 RabbitMq service is not connected - trying again in 60 seconds. 
ERROR: RabbitMQ.Client.Exceptions.BrokerUnreachableException: None of the specified endpoints were reachable 
---> RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: 
AMQP close-reason, initiated by Peer, code=541, text='INTERNAL_ERROR - access to vhost '/' refused for user 'client_engine': 
vhost '/' is down', classId=10, methodId=40

Additionally, the RabbitMQ logs may read:

EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60918 -> [::1]:5672)
[info] accepting AMQP connection ([::1]:60921 -> [::1]:5672)
[error] Error on AMQP connection ([::1]:60921 -> [::1]:5672, state: starting):
[error] EXTERNAL login refused: user 'client_engine' - invalid credentials
[info] closing AMQP connection ([::1]:60921 -> [::1]:5672)

For information about how to obtain log files, see How to collect the Qlik NPrinting Platform Log Files.

Resolution

Initial checks:

1. Follow the instructions in Qlik NPrinting Engine Offline status 
2. Continue with How to Resolve Qlik NPrinting Engine Offline Status.

If the issue persists, the RabbitMQ installation needs to be repaired. To do so effectively may require multiple rounds of reinstalling the Qlik NPrinting engine, as well as the RabbitMQ certificates to be recreated. 

Our expected result is:

• The Qlik NPrinting Engine comes online
• RabbitMQ logs do not include errors
• We do not receive errors when checking the RabbitMQ status

RabbitMQ repair:

All Qlik NPrinting services must be running for this procedure to work.

1. Recreate the RabbitMQ certificates (see Recreate the messaging service certificates).
2. Reinstall the Qlik NPrinting engine (see Installing Qlik NPrinting Engine).
3. Does the issue persist? Review the Qlik NPrinting and RabbitMQ logs to verify if the two errors (RabbitMq service is not connected and EXTERNAL login refused: user 'client_engine' - invalid credentials) continue to be logged.
4. Check the RabbitMQ service status (see Check the node status on the RabbitMQ console).
5. Repeat: Recreate the RabbitMQ certificates (see Recreate the messaging service certificates).
6. Repeat: Reinstall the Qlik NPrinting engine (see Installing Qlik NPrinting Engine).
7. Verify RabbitMQ permissions for the client_engine user (see Check the messaging service users and permissions).
8. Repeat: Check the RabbitMQ service status (see Check the node status on the RabbitMQ console).
9. If you continue to see errors when checking the RabbitMQ status (rabbitmqctl.bat status), repeat from Step 1. 

This cycle should be completed only twice at the most, but it is necessary to reestablish a connection between the Qlik NPrinting Engine and RabbitMQ.

If this fails to resolve the issue, log a support case with Qlik Support, including detailed information about all troubleshooting steps that have already been performed.

Cause

This indicates the RabbitMQ installation is corrupted or otherwise damaged. Multiple root causes exist:

• A Qlik NPrinting Upgrade corrupted the files
• C:\ Drive was full, or the Qlik NPrinting installation drive was full
• RabbitMQ crashed due to Antivirus scanning
• Unsupported items; for Qlik Sense see Qlik NPrinting and Qlik Sense Object Support and Limitations, for QlikView see Qlik NPrinting: Unsupported QlikView Document items, System Configurations and other limitations.
   

Environment

• Qlik NPrinting

Users previously assigned a Basic User entitlement have unexpectedly been promoted to Full User entitlement. 

This is working as expected and will happen when a Basic User is granted any additional permissions. Source: Types of user entitlements.

An exception is the Collaboration Platform role, see Qlik Cloud Analytics: Assigning the Collaboration Platform User role to a Basic User does not promote it to full.

How to determine what elevates a user

To determine what promotes a user to a Full User: 

1. Log in and go to the Cloud Administration center
2. Go to User Management
3. Hover (a) over the user's Information icon
   
   
   
   

It is also possible to use the Access Evaluator App to have a more holistic overview over assignments.

What to remove

To avoid users being promoted to Full Users, remove any assignment, both in single spaces and at a global level.

Spaces

Verify the users are not assigned any roles other than than Has restricted view. 

Be careful when using the Anyone group, since assigning any other role to this group will promote all users to Full.

This includes the default data space: Default_Data_Space created on tenant setup. Remove the Anyone member:

1. Go to Spaces
2. Click the ellipses menu (...) and choose Manage members
3. Remove Anyone by through the ellipses menu (...) and clicking Remove
   
   
   

Global

Turn off Auto assign for all Security roles in the Administration Center.

1. Open the Administration Center
2. Open Users
3. Switch to the Permissions tab
4. Switch Auto assign to Off on all Security roles:
   
   

Specific users

If a user was manually assigned a role, the role has to be removed again manually.

1. Open the Administration Center
2. Open Users
3. Switch All Users tab if not already selected
4. Locate the user and click the ... menu (a), then choose Edit roles (b) and remove all previously assigned roles
   
   

Environment

• Qlik Cloud Analytics

Is it faster to use a CSV file versus a Parquet file? Will one load to Qlik Cloud faster than the other?

The answer to this depends on the data.

The Analytics Engine makes calls to read data from the file as needed (streaming). While parquet files have built-in compression, which can affect how quickly certain data can be accessed, an equivalent CSV might be larger in raw data volume.

Environment

• Qlik Cloud
• Qlik Data Gateway

The following error occurred in Qlik Cloud Analytics:

Unexpected token: 'NONCLUSTERED', expected: 'Relationship' The engine error code: EDC_ERROR:11005 The error occurred here: CREATE >>>>>>NONCLUSTERED<<<<<< INDEX IX_WebProducts_ProductID ON #WebProducts(ProductID) !EXECUTE_NON_SELECT_QUERY

Resolution

Add the following SQL statement to resolve the issue:

SQL CREATE NONCLUSTERED INDEX IX_YourIndexName1234 ON "test_db".SalesLT.Customer (LastName DESC) !EXECUTE_NON_SELECT_QUERY; 

Environment

• Qlik Cloud Analytics

Some Qlik Cloud visualisations allow images to be shown from external URLs.

Is it possible to embed images that were uploaded to the media library?

Resolution

We currently don't have a global repository for images in Qlik Cloud, but each app has its own media library, where images can be uploaded.

To link them:

1. Make sure you are authenticated on the tenant
2. Get the list of all media contained in an app by going to https://TENANT.REGION.qlikcloud.com/api/v1/apps/APPID/media/list, replacing TENANT, REGION, and APPID with the correct values
3. Get the link for each image
   
   Example:
   
   "type": "image","id": "UserAnalyzer.png","link": "/api/v1/apps/1aa5c924-72cb-405a-bb60-8b5118e4b299/media/files/UserAnalyzer.png","name": "UserAnalyzer.png" 
   
   
4. Use the resulting /api/v1... URL for your visualization
   
   

Using a full URL to display the images (example: https://TENANT.REGION.qlikcloud.com/api/v1/apps/APPID/media/files/FILENAME.png) will work inside the app when authenticated on the tenant, but it will not work in other scenarios, such as mashups or the reporting service.

Make sure to use a relative URL (example: /api/v1/apps/APPID/media/files/FILENAME.png) instead.

For suggestions on how to improve the media library, please log an idea at Qlik Ideation.  

Environment

• Qlik Cloud Analytics

The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 2.0.0.

Content

• What's New
• 2.0.0 May 2025 Release Notes
• Known Limitations (2.0.0)
• 1.4.0 December 2023 Release Notes
• Known Limitations (1.4.0)
• 1.3.0 May 2023Release Notes
• Known Limitations (1.3.0)
• 1.2.0 Release Notes

What's New

• The PostgreSQL version used by QPI has been updated to 14.17
• An upgrade of an already upgraded external instance is now possible
• Support for an upgrade of the embedded 14.8 database was added
• Silent installs and upgrades are supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)

2.0.0 May 2025 Release Notes

Known Limitations (2.0.0)

• Rollback is not supported.
• The database size is not checked against free disk space before a backup is taken.
• Windows Server 2012 R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012 R2.
• QPI will only upgrade a PostgreSQL instance that only contains Qlik Sense Databases (QSR, SenseServices, QSMQ, Licenses, QLogs, etc.)

1.4.0 December 2023 Release Notes

Known Limitations (1.4.0)

• QB-24990: Cannot upgrade PostgreSQL if Qlik Sense was installed in a custom directory such as D:\Sense. See Qlik PostgreSQL Installer (QPI): No supported existing Qlik Sense PostgreSQL database found.
• Rollback is not supported.
• Database size is not checked against free disk space before a backup is taken.
• QPI can only upgrade bundled PostgreSQL database listening on the default port 4432. Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
• Cannot migrate a 14.8 embedded DB to standalone
• Windows Server 2012R2 does not support PostgreSQL 14.8. QPI cannot be used on Windows Server 2012R2.

1.3.0 May 2023 Release Notes

Create the Bookmark

1. Create a bookmark. The bookmark menu can be located in the top right corner of the Qlik Sense app overview. 
   
   
   
   
2. Create and save the bookmark
3. Navigate back to the bookmark menu.
4. Right-click the bookmark that you wish to share.
5. Select Publish
   
   
   

You can also click Copy link - this will show a warning that the bookmark needs to be published. When confirming the warning, the bookmark will be automatically published. 

Share the Bookmark

1.  Right-click the bookmark again.
2. Select Copy link   
   
   
   
   
3. Share the link with anyone who has access to the application. 

If the share option is not available or if users who should see the bookmarks cannot find it, verify that Sense has not been set up with Security Rules that disallow sharing or access to specific objects. See the attached document for details.

Loading MS Access data (.accdb file) using generic ODBC (via Data Gateway) in Data Manager fails with the following error:

Failed to add data
Data could not be added to Data manager. Please verify that all data sources connected to the app are working and try adding the data again.

The Direct Access ODBC Connector log reads:

Message=Error in HandleJsonRequest for method=getRawScript,
exception=Exception, error=ODBC Wrapper: Unable to execute SQLForeignKeys:
[Microsoft][ODBC Driver Manager] Driver does not support this function.
internalError=True

Resolution

Use the Data Load Editor to load MS Access data.

Loading file-based Access DBs through ODBC to a modern BI tool is not recommended, specifically with larger files. These are likely to underperform during the loading process.

Cause

This error indicates the MS Access ODBC driver doesn’t support the SQLForeignKeys ODBC function. However, retrieving the table foreign keys is essential for Data Manager (as opposed to Data Load Editor).

Internal Investigation ID(s)

SUPPORT-4446

Environment

• Qlik Cloud Analytics
• Qlik Data Gateway

A Talend Spark Stream Job configured with Yarn cluster mode and Kerberos enabled is encountering issues and failing to execute, presenting the following errors: 

YarnClusterScheduler- Lost executor 3 on me-worker1.xxx.co.id: Unable to create executor due to Unable to register with external shuffle server due to : java.lang.IllegalStateException: Expected SaslMessage, received something else (maybe your client does not have SASL enabled?)

jaas.conf content =
Client {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};

KafkaClient {
com.sun.security.auth.module.Krb5LoginModule required
useKeyTab=true
keyTab="/tmp/adm.keytab"
principal="cld_adm@XXX.CO.ID"
doNotPrompt=true;
};

Cause

The external shuffle service within YARN is configured to mandate SASL authentication; however, the Spark executor is either improperly configured to use SASL or is transmitting an incompatible message.

Common causes includes:

1. The absence or inaccuracy of SASL configuration in either spark-defaults.conf or YARN's configuration file (yarn-site.xml).
2. A version discrepancy between Spark and YARN, where the shuffle service necessitates a particular SASL protocol unsupported by the Spark client.
3. Improper security configurations, including the omission of Kerberos credentials or incorrect settings for spark.authenticate and associated properties.

This error results in the executor's failure to register with the shuffle service, prompting the YarnClusterScheduler to mark it as lost.

Resolution

Ensure that the external shuffle service is enabled, and that the SASL settings are in accordance with YARN's configurations:

spark.authenticate true
( #not necessary 
spark.network.crypto.enabled true
spark.network.crypto.saslFallback true
)

Environment

• Talend Data Integration 

The new Straight Table was moved into the new native section of charts from the visualization bundle. The new Straight Table offers many improvements from the old table, and we encourage everyone to start using the new table instead of the old one.

This article aims to answer any frequently asked questions around this switch, beginning with:

• The old table will not be removed anytime soon. It will continue to work until further notice. We encourage you to subscribe to the Qlik Support Blog and What's New in Qlik Cloud to stay ahead of updates.
• The old table will not be updated further. Use the new table to benefit from future improvements.
• We monitor your feedback and will improve the functionality of the new table.

FAQ

What improvements does the Straight table come with?

Here are some examples:

• Grid styling
• Totals styling
• Pagination or virtual scroll
• Scrollbars outside of the table
• Add, delete many fields at the same time
• Cell font family, size and color styling
• Font styling by expression
• Column width options pixels, percentages
• Chart exploration, end user can pick dimensions and measures
• Header on/off
• Zebra striping
• Null value styling
• Selection info in export
• Totals in export
• Titles in export
• Cyclic dimension controls in dropdown

Will the old table be removed?

No, the old table will continue to work in the foreseeable future. Any changes will be notified in advance. Regardless, we highly recommend upgrading your tables as soon as possible to enjoy the new Straight Table's new functions. 

How do I convert to the new table?

The easiest way to convert your tables is to drop the new table chart onto the old one.

1. First, copy the old table
2. Edit the sheet that includes the Table (retired)
3. Open the Charts pane
4. Drag the Straight table over your table
5. Choose Convert to: Straight table

The new table looks different and offers more functionality that must be enabled to be used.

When will the old table be deprecated?

Not anytime soon, it will be a soft fade out. The new Straight Table will be the preferred choice for all new applications, and we anticipate many will upgrade to benefit from new functionality. Over time, the usage of the old table will diminish until most applications are using the new table anyway.

Will this affect Qlik Sense Enterprise on Windows?

Qlik Sense Enterprise on Windows will have the table feature aligned with Qlik Cloud Analytics in a future release.

I’m not happy with X and Y of the new table, will that be changed?

We’re closely monitoring feedback on the new table and are dedicated to creating the best possible experience, including improvements to accessibility. We are committed to accessible standards so people with disabilities can use our products. Printing, the tables should, of course, print in as consistent a manner as possible. As for usability. we aim to enable experienced users to reach functionality quickly, while also not overwhelming new users.

Environment

• Qlik Analytics

This article aims to help you facilitate the most effective way to collaborate with Qlik Support. It defines your responsibilities as a partner, including reproducing issues, performing basic troubleshooting, and consulting the knowledge base or official documentation.

For the Qlik Talend guide, see Partner Guide: How to Prepare and Collaborate with Qlik Talend Technical Support.

Before contacting Qlik Data Analytics Technical Support, partners must complete the steps outlined in Qlik Responsible Partner Duties and should review the OEM/MSP Support Policy to understand the scope of support and the expectations on Partners.

• Partners are required to complete the steps outlined in this article before submitting a support case.
• It is the partner’s responsibility to answer the customer's questions to the best of their ability by referring to documentation, the Qlik Community, previous cases, and online resources before submitting a case or commenting on an existing one.
• For high-priority or urgent issues, it is acceptable to raise a ticket early. However, the responsibilities outlined in the article still apply at every stage of the case. 

Content

• General Expectations Before Submitting a Case
• Isolate What Is Affected
• Provide Product and Version Information
• Reproduce the Issue in Your Environment
• Always Provide Complete (Not Partial) Logs
• Describe What You Have Already Investigated
• Submit All Related Files You Investigated Or Used For Replication
• Submit the Case Using Your Partner Account
• Partner Case Submission
• Template
• Summary of the Problem
• Customer Information
• Files Attached
• Summary of your Investigation

General Expectations Before Submitting a Case

Isolate What Is Affected

Identify which Qlik product, environment, product configuration, or system layer is experiencing the issue. 

For example, if a task fails in Qlik Sense Enterprise on Windows, try running it directly in Qlik Sense Management Console to determine whether the problem is transient. Also, try running a different task to determine whether the problem is task-specific.

Similarly, if a reload fails in one environment (e.g., Production), inform the customer to try running it in another (e.g., Test) to confirm whether the issue is environment-specific.

Provide Product and Version Information

Always include the exact product name, version, and patch (or SR) the customer is using. 

Many issues are version-specific, and Support cannot accurately investigate the issue without this information.

If the product the customer is using has reached End of life (EOL), please plan the upgrade. If the issue can be reproducible on the latest version, please reach out to us so that we can investigate and determine whether it's a defect or working as designed. 

For End of Life or End of Support information, see Product Lifecycle.

Reproduce the Issue in Your Environment

Partners are expected to recreate the customer’s environment (matching versions, configurations, and other relevant details) and attempt to reproduce the issue.

If you do not already have a test environment, please ensure one is set up. Having your own environment is essential for reproducing issues and confirming whether the same behavior occurs outside of the customer’s setup.

In addition, please test whether the issue occurs in the latest supported product version. In some cases, it may also be helpful to test in a clean environment to rule out local configuration issues. If the issue does not occur in the newer version or a clean setup, it may have already been resolved, and you can propose an upgrade as a solution.

See the Release Note for the resolved issues.

Regardless of whether the issue could be reproduced, please include: 

• The exact Qlik Product version and environment information (OS, Browser, etc)
• The exact steps you followed
• Screenshots showing your process
• Any sample apps, data files, or configuration files used during testing
• A summary of your results (such as “Reproduced same error,” or “Could not reproduce – no error occurred”)

Always Provide Complete (Not Partial) Logs

While pasting a portion of the log into the case comment can help highlight the main error, it is still required to attach the entire original log file (using, for example, FileCloud).

Support needs the full logs to understand the broader context and to confirm that the partial information is accurate and complete. 

It is difficult to verify the root or provide reliable guidance without full logs.

Additionally:

• Specify which logs you reviewed
• Confirm that the customer provided full, uncut logs, not only short fragments
• Include logs from both the customer's environment and your own reproduction tests
• If possible, change the log level to DEBUG temporarily and share it with us
  
  Providing both sets of logs allows Support to see what testing has been done and whether the same error occurred during reproduction. 

Describe What You Have Already Investigated

Please do not simply forward or copy and paste the customer’s inquiry.

As a responsible partner, you are expected to perform an initial investigation. In your case submission, clearly describe:

• What you reviewed (such as logs and configurations)
• What actions you took to isolate or reproduce the issue
• What you analyzed, tested, or attempted
• What you concluded or suspected based on your investigation (such as why you think it is a bug, why you think the problem is occurring)

Sharing this thought process:

• Helps Support understand your assumptions
• Avoids duplicated effort
• Demonstrates that the case is ready for advanced-level investigation

Even if the issue remains unresolved, outlining what you already tried helps Support move forward faster and more effectively.

Submit All Related Files You Investigated Or Used For Replication

Attach all relevant files you received from the customer and personally reviewed during your investigation, as well as all relevant files you have used when reproducing the steps.

Providing both the customer’s files and your reproduction files allows Support to verify whether the same issue occurred under the same conditions, and to determine if the problem is reproducible, environment-specific, or isolated to the customer's configuration.

This includes (but is not limited to):

• Log files (e.g. Qlik logs, Connector logs, Windows Event logs, Server Stats, Har file, etc, if necessary)
• Screenshots: If an error is visible on the UI, please include the error message and accessed page URL.
• Sample input files or test data

Submit the Case Using Your Partner Account

All support cases must be submitted using your official partner account, not the customer's account.

If you do not yet have a partner's account, contact Qlik Customer Support to request access and to receive the appropriate onboarding.

Partner Case Submission

Review the support policy and set the case severity properly. See 
Qlik Support Policy and SLAs

Template

This template helps guide you on what to include and how to structure your case.

Summary of the Problem

What happened? When did it happen? Where did it happen?

Clearly describe the event, including:

• A brief summary of the impact (e.g., "Unable to login to Qlik Sense Enterprise on Windows hub")
• Date and time the issue occurred (e.g., "Since July 10, between 13:50–13:55 JST")
• Product (e.g., "Qlik Sense on Windows Nov 2024 Patch 7")
• Environment: OS version, Browser, etc

Customer Information

Only include what is needed based on the case type.

Examples:

• Customer's Company Name
• License number
• Tenant information (only Qlik Cloud):
  Find your Qlik Cloud Subscription ID and Tenant Hostname and ID

Files Attached

List the files you have included in the case and what each one is.

Summary of your Investigation

Explain what investigation was done before contacting support.

Examples:

• Logs/files you reviewed
• Patterns/errors observed
• Assumptions you made (e.g., suspected cause)
• Whether the issue is reproducible (If it's reproducible, describe the reproduction steps too)
• Troubleshooting steps attempted

Thank you! We appreciate your cooperation in following these guidelines.

This ensures that your cases can be handled efficiently and escalated quickly when necessary.

Question

After moved migrated GitHub from on-premises to cloud and so switched from credential login to SSO, is there a way to authenticate Talend Studio to GitHub using SSO login? If using personal access tokens (PATs), is it on the security risk?

So far Talend Studio cannot SSO directly to GitHub, it can use a workaround with PATs or SSH keys, and thereby also be more secure than without SSO. 

• How a personal access token can be authorized for SSO

  https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-a-personal-access-token-for-use-with-saml-single-sign-on

  This link above explains how a personal access token can be authorized for SSO. So using a username and PAT from Studio to login to GitHub. GitHub allows granular permission controls for PATs and SSO authorization further mitigates security risks. Developers will need considerable rights.

• How an ssh key can be authorized for SSO

  https://docs.github.com/en/enterprise-cloud@latest/authentication/authenticating-with-saml-single-sign-on/authorizing-an-ssh-key-for-use-with-saml-single-sign-on

  You can do much the same with SSH keys

Environment

Talend Studio 

When attempting to connect to a GitHub repository from Talend Studio, encountered an error with the following message:

"git-upload-pack not permitted on 'https://github.com//.git'"

Common Symptoms:

Error:org.eclipse.jgit.api.errors.TransportException

Message:username or password are not correct

GitHub Desktop and Git Bash access may still work

Can successfully access other GitHub repositories

Cause

This issue is caused by a missing Single Sign-On (SSO) authorization on the GitHub Personal Access Token (PAT) being used.

When a GitHub organization enforces SAML SSO, all PATs must be explicitly authorized for use by the organization. If this step is skipped or the organization has changed its SSO enforcement, Git operations like git-upload-pack will be denied — even if the PAT has the correct scopes.

Resolution

To address the issue, please verify and reauthorize Single Sign-On (SSO) for your GitHub Personal Access Token (PAT) by following these step-by-step instructions:

1.  Sign in to GitHub
   1. Go to https://github.com/settings/tokens
2. Locate Your Personal Access Token 
   1. Find the token being used for Talend Studio under "Tokens (classic)"
3. Authorize SSO Access
   1. Click "Configure SSO" next to the PAT 
   2. A pop-up will appear listing available organizations
   3. Click Authorize next to your organization
4. Retry the Git Connection in Talend Studio
   1. Restart Talend Studio
   2. Re-enter your GitHub username and the PAT as the password when prompted

Optional: Test via Git Bash

Run: 

git clone https://user:PAT@github.com/<org>/<repo>.git

If SSO is not configured, you will receive a message:

Your organization has enabled or enforced SAML SSO...

Related Content

Qlik Talend Cloud: 'git-receive-pack not permitted' error while creating a project

Environment

• Talend Studio 8.0.1