Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
Gartner® Magic Quadrant™: 15 YEARS A LEADER - GET THE REPORT

Binary load fails with General Script Error when using app binary instead of .qvf

0% helpful (0/3)
cancel
Showing results for 
Search instead for 
Did you mean: 
Andre_Sostizzo
Digital Support
Digital Support

Binary load fails with General Script Error when using app binary instead of .qvf

Last Update:

Jun 4, 2025 11:06:13 AM

Updated By:

Sonja_Bauernfeind

Created date:

Dec 3, 2015 5:54:36 PM

A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:

General Script Error

or

Binary load fails with error Cannot open file

 

Before Qlik Sense Enterprise on Windows November 2024 Patch 8, the Qlik Engine permitted an unsupported and insecure method of binary loading from applications managed by Qlik Sense Enterprise on Windows.

Due to security hardening, this unsupported and insecure action is now denied.

Binary loads of Qlik Sense applications require a QVF file extension. In practice, this will require exporting the Qlik Sense app from the Qlik Sense Enterprise on Windows site to a folder location from which a binary load can be performed. See  Binary Load and Limitations for details.

Example of a valid binary load:

Binary [lib://My_Extract_Apps/Sales_Model.qvf];

Example of an invalid binary load:

"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"

 

Environment

  • Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases
Labels (1)
Comments
duschking
Contributor II
Contributor II

hallo, ich habe ein ähnliches problem...

unsere apps befinden sich im freigebenen ordner c:\qlikshare\apps.. (es sind alle notwenigen berechtigungen vorhanden)

duschking_0-1743512191255.png

es gibt dort keine extension.

ich will nun dieses file in einer app als binary load verwenden.

binary [lib://Apps/da9378f1-8321-49a2-a20b-ff3591dcd14f];

duschking_1-1743512262509.png

 

das interessante ist aber. wenn ich das file in windows umbenenne und die extension .qvf dranhänge umd im binary das auch so lade funktioniert es..

was ist hier falsch - bitte um hilfe, da ich sonst weiter auf qlikview bleibe und sense so nicht brauchen kann.

 

mariusbirk
Partner - Contributor III
Partner - Contributor III

We have the same issue. After update to Qlik Sense November 2024 (Patch 9) a binary load of a qlik sense app (without file extension) didn't work anymore. Patch 7 & 8 same procedure (i only tested these two version additionally). 

But in IR it works.. So it is a bug in the version November 2024 Patch 7,8,9 

luciano_pw
Partner - Contributor II
Partner - Contributor II

Tive o mesmo problema executando da seguinte forma:

BINARY [lib://Apps/bb1affd0-bbe0-4022-824b-4732c7d9d3ff];

 

Após mudar para o formato abaixo (sem a lib), funcionou perfeitamente:

BINARY [bb1affd0-bbe0-4022-824b-4732c7d9d3ff];

LeeSmithBtn
Partner - Creator
Partner - Creator

Well this is a pretty big mess!! 
so i have apps binary loading across servers, which now i cannot seem to get anything to work.

I have upgraded to May 2025 and i need to test out binary loads between 2 apps. 
app1 is on test server and app2 is on dev server... 

i am trying to binary load app1 into app2. however i cannot find anything to get this to load.

the server only contains App_Ids not names and they all state they are a (file) type. how do i get this to be a QVf and how can i binary load between the 2. i cannot find anything online and this user guide is pretty pointless considering the binary has to be the first line in the code, yet this is showing how to load from a QVD not a binary load between apps

LIB CONNECT TO 'DataFiles';
  LOAD * FROM [YourFile.qvd]

 any support / help identifying a fix on this mega issue would be appreciated, as currently all my process would now fail.

 i just seem to get this error:

 

The following error occurred: FileSize for \\X.X.X.X\d$\QlikResources\Apps\a05d2edc-c911-4957-8c77-f4799b687cde.qvf failed: boost::filesystem::file_size: The system cannot find the file specified [system:2]: "\\X.X.X.X\d$\QlikResources\Apps\a05d2edc-c911-4957-8c77-f4799b687cde.qvf": no such file or directory

luciano_pw
Partner - Contributor II
Partner - Contributor II

@LeeSmithBtn, I tested with binaries on the same server. In this case, from what I understand, it's no longer necessary to provide the path - only the app ID (binary [a1b2c3d4e5f67890]). However, I have no idea how to read from another directory. If you find any way, please share it with us.

LeeSmithBtn
Partner - Creator
Partner - Creator

@luciano_pw  - as soon as i find a solution i will of course post it here... 

Currently, i am finding no way at all in many combinations to binary from an alternate path. if i bring the app to current server, it works fine. 

but it would be a huge process to migrate all apps an potential open issues with moving apps around to binary load from.

i cant believe there is not a work around, as this must be a normal process for many companies

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @LeeSmithBtn 

Please contact our Support to review this together with you. Feel free to cite this article.

All the best,
Sonja

LeeSmithBtn
Partner - Creator
Partner - Creator

thanks @Sonja_Bauernfeind  - have raised a support ticket.

Now kind of stuck not being able to reload anything. ill await the contact from support

LeeSmithBtn
Partner - Creator
Partner - Creator

@luciano_pw -

I have had an update from support, that there is now no way to binary load from a source app / ID of an app on an alternate server... 

apparently this is less secure and actually exporting apps and moving them around locations or even saving data to QVDs taking up more resource and cost is a better alternative and more secure i assume... 

my apps are currently stored in secure locations, with strict access rules attached. so i am now going to have to break this secure chain, because there is now no way to binary load from server to server. 

this should have been an option for the user / management to switch off binary loading to stop files being locked, not to remove the whole feature that has been around for as long as i can remember and is actually extremely useful.

 

not sure how many customers upgrading to a newer version of sense will be aware of this, as this could cause major headaches for large organisations who may utilise binary loading. 

 

perhaps this needs a huge warning adding to users when upgrading because i am now on a newer version and going to have to spend hours trying to unravel this mess.

 

 

luciano_pw
Partner - Contributor II
Partner - Contributor II

Thanks for the information, @LeeSmithBtn. I haven’t seen whether there was any official announcement besides this post about the removal of this feature, but it’s a shame. If there wasn’t, it’s going to catch a lot of people by surprise.

Contributors
Version history
Last update:
2 weeks ago
Updated by: