Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

Qlik Sense Extension - Engine Error when Edit sheets

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Benoit_C
Support
Support

Qlik Sense Extension - Engine Error when Edit sheets

Last Update:

Dec 4, 2020 8:59:24 AM

Updated By:

Sonja_Bauernfeind

Created date:

Nov 25, 2020 11:16:43 AM

Environment

  • Qlik Sense All versions

 

Description

In Qlik Sense, when you edit a sheet, Qlik Sense needs to load in all the extensions to have them available in the assets panel.

If you have an extension with an hardcoded appid which is not existing, during the load of this extension it already tries to open up this app with the specific id.

 

Resolution

To solve this issue you can either delete this extension or edit the extension to remove the hardcoded id.

 

Cause

In the below example, the extension tries to open an app with a certain id using the <qlik-visual /> html component:

// <style></style><div>{{appid}}<qlik-visual appid="0a28ea16-45e5-439c-9efb-3766a9c8964d" type="listbox" cols='["LOB_SSD"]' options="{}">asd</qlik-visual></div>

This should be used as a variable instead. Removing the hardcoded appid made the extensions load. 

 

Troubleshooting

If you have the issue described in this article you will have the below Engine error:

No available Qlik Sense engine was found. Refresh your browser or contact your system administrator

 

In the Audit Proxy logs you will find the below error:

11716 20201029T170246.841+0100 INFO QlikServer1 Audit.Proxy.Proxy.SessionEstablishment.LoadBalancingHandlerDependencies 50 7b18d13c-3803-4f4b-b344-7006e823526e DOMAIN\qvservice Retrieved 0 engine(s) from repository, result code AppNotFound, app: TESTTTTTT 1809e96e-49b9-4bf1-aa97-d3802b109b99 f8edc0b7-5117-48b2-9fd6-eb44855bfc34 DOMAIN user1 ::ffff:172.16.16.100 TESTTTTTT {} 9a02c6b414da25b84ad74487e101d53c6c33d9fa

In order to be able to identify which extension is guilty you will have to create a .har file (see Save network web traffic (HAR/XML file) and console logs from the browser's developer tools). 

 

Just before it is trying to open the wrong app you will see what extension it is opening, this is the guilty extension:

GET https://localhost/extensions/GuiltyExtension/TESTTTTTT.html

GET wss://localhost/app/TESTTTTTT

Labels (1)
Version history
Last update:
‎2020-12-04 08:59 AM
Updated by: