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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Noor51
Creator
Creator

Binary Load General Script Error

I trying to do a binary load, but I get error message "General Script Error". How do I solve this issue. 

Noor51_0-1713273990093.png

Does it make a difference if the QVF file is on the server file vs personal drive when loading?

Also, Is there a way to remove section access after a binary load? 

 

 

Labels (3)
12 Replies
Kaushik2020
Creator III
Creator III

Is this thread resolved ?

I am using November 2024, Patch 9 on premise edition. Still the Binary load is failing.

@Sonja_Bauernfeind 

B_Duncan
Partner - Contributor II
Partner - Contributor II

I heard back from support and they are saying:

"The ability to use binary load from an app within the same Qlik Sense Enterprise deployment by referring to the app ID is no longer supported. You can only perform a binary load from a .qvf file. The Qlik Security team expressed concerns about this functionality, which decision to restrict binary loading to only .qvf extension files from whitelisted paths."

This doesn't make sense because the restriction on the file ending with .qvf has always been there in the documentation from what I can tell and the Folder Data Connection was recommended by "experts" to be the solution. 

It is troubling that change like this would be included in a patch with practically no documentation on something that breaks a huge part a many deployment architecture. There is a mention of a "White list" for folders to be included but no info on where said list is.

A better solution then what is being provided thus far is needed.

merav21
Contributor
Contributor

Following a recent QlikSense server upgrade to Nov 24 Patch14,
we identified a loading issue in the production environment.
While binary loads of QVF files worked correctly in the development environment,
they were failing in production.
The key difference we found was the connection path for the QVF files.
In the production environment, the path was configured as a local directory (C:\QlikShareRoot\Apps),
whereas the development environment used a network share path (SERVERNAME\QlikShareRoot\Apps\).
After updating the connection path in the production environment to the network share,
the binary load was successful.
It appears that QlikSense's whitelisted folders must be configured as network shares for binary loads to function correctly.