Binary command is not working anymore after update Qlik Sense Enterprise

[mcoolen01]

Recently (a week ago) we installed the Qlik Sense Enterprise update. Everything looked okay, but in the QMC - tasks I noticed that my apps were no longer reloaded anymore. The issue was (is) that because of security reasons the Binary commandline no longer accepts app-id's. You need to refer to a proper .qvf file name (including the extention).

Now, adding the .qvf extention to the app-id and refer to this new name in the Binary commandline works, but than it is no longer possible to open the original app. Qlik Sense only knows the app-id without extention!

So how do I solve this?
I tried to export the original app that is used into the Binary commandline to a separate folder and used this folder in the dataconnection applicable. That is working okay.

But now I have the issue that the exported (qvf) file is not being reloaded. How can I make this file being reloaded again. If that is succeeding, my issue is over.

What I am hoping for is that the exported qvf file can be imported into the work-stream of Qlik Sense and can be used without issues in the Binary commandline. But I think that when I will import the exported qvf file, Qlik Sense will leave out the extention again which created my issue all over again.

Can somebody help me with this matter please?
I would be very greatfull.

Gr. Michel

[pablolabbe]

Hi Michel, this change to block binary load for security reasons broken several customers apps reloads.

Probably you have renamed the binary file in the apps folder inside the Qlik shared folder . "Don´t do that" because you will break the reference between the file and the repository and the app will unavailable in QMC for reload and visualization from Hub.  

They only allow reading files that are not part of your environment, for migration or maintenance purposes, but you cannot use this strategy anymore as a datasource for other apps.

My recommendation is to create a new layer of QVDs to be share among apps , if you don't have it.

[Nagaraju_KCS]

We were facing same issue when qlik upgrade, we followed below steps 

1. Export the Source App: Export the original app that contains the source data model (the one being binary loaded).

2. Import the QVF: In the Qlik Sense Hub or QMC, import the exported .qvf file. This assigns it a NEW and valid AppID in the Qlik Repository.

3. Publish: Publish this newly imported app to a stream so it can be accessible.

4. Create a New Reload Task: In the QMC, create a reload task for this newly imported app. This solves your problem of the exported file not being reloaded.

5. Update the Binary Load Script: In your target application's script, update the Binary command to point to the newly imported app's AppID.

Hope this helps!

[Lech_Miszkiewicz · Accepted solution]

Hi @mcoolen01 

We faced the same issue and we used available solution which can be added to settings.ini file:

Specific settings.ini Settings for Binary Load:
EnableQvfPathValidation=0:
This setting you can placed under [Settings 7] in settings.ini and it disables the path validation for QVF files during binary loads. Disabling this validation allows for binary loads from locations that might otherwise be restricted by the default security settings. By default file is located in C:\ProgramData\Qlik\Sense\Engine\settings.ini

As usual once you do this restart services and of you go.

This is old discussion about it:

https://www.linkedin.com/posts/anjali-gupta-3a1101a5_qlik-binaryload-bi-activity-7343249965508435972...

cheers

[Nagaraju_KCS]

This is the simple and good one - I will try this 

[Lech_Miszkiewicz]

of course - it works back again as normal as before and does not require any gymnastics suggested by others 🙂

[mcoolen01]

Hey Lech_Miszkiewicz,

Thank you very much for your help. A few minutes ago I implemented your solution (changed .ini) and it worked perfectly.

Again, thanks.

Lots of regards from Holland,
Michel