Binary Load General Script Error

[Noor51]

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

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? 

[igoralcantara]

If the original file has section access and the user running the file is not an admin in the section access, this might be the cause of the problem.

You cannot remove section access after you load it.

[Noor51]

Ok I understand that I can't get rid of the section access, but how do I solve the issue with the running this load script.

[igoralcantara · Accepted solution]

Try this test: remove the section access and check if this removes the error. If so, you need a version of the app without section access to be your source app. 

[Noor51]

Thanks for the quick response.  

Another Question, What if the app is build by different tables rather than one single table? 

Our apps is based on connecting different tables. so it is not a normalized single table, is there a quick way to convert that app into a QVD with the same structure ?

[TiDriv3r]

Would like to adress to the same topic. 
After Nov24 and Patch8 I am not able to Binary load. I have the message "General Error" and no hint in the server logs, what the issue might be... wondering what happend.
I did test a new application with inline code. A second application with binary on it. So there is no section access or other security rules interventing... 

What else I can try? 

[datamind]

Hi TiDriv3r,
Did you get it resolved?

[TiDriv3r]

Hi and thanks for reaching out! 🙂

Regrettably, not yet...
I switched my concept to storing all model QVDs and loading them using LOAD * FROM qvdlibary\*.qvd; (example).

Nevertheless, I would like to understand what exactly happened to learn how to avoid similar situations in the future.

Before implementing this workaround, I also checked the following:

• Setting Legacy Mode to 1 (including server restart) did not help.

• A simple setup without Section Access had the same problem.

• No environmental path changes were made.

• Folder access (Qlik apps, etc.) was granted without restrictions for both the service and developer users.

What else could be causing this issue?

[MartijnWanders]

Hi TiDriv3r,

Same problem here and could not find the issue. No section access at all. Even the same problem with a new app and one table. QlikSense is updated to Nov 2024 with all paths.

I hope they find the issue. Thank you for pointing out the QVD solution.

[B_Duncan · Accepted solution]

Patch 7 for Nov 2024 broke this. From the release notes:

QB-29696

Ensure that there is no attempt to try to open or write files outside whitelisted folders

Fixed security issue where Engine would try to read and write to any path specified against Engine API. Solution of the fix adds path restrictions (with whitelisted folders) on e.g. OpenDoc and ExportApp, and restrictions to how relative paths are used in folder connections and lib references in the script. Relative paths should not be allowed to point outside of the scope set. It's not recommended to disable this fix, but can be disabled in case of emergency. To disable the fix, you need to add EnableQvfPathValidation=0 into Engine's Settings.ini file.

Qlik didn't give much info on what these "whitelisted folders" are or what they mean by "relative paths" not being allowed. Putting that parameter in the engine Settings.ini file does allow the Binary Loads to work again.

The patch breaks the architecture for a production secure binary load process as described in https://community.qlik.com/t5/Deployment-Framework/Qlik-Sense-Secured-binary-loads/td-p/1486144 and elsewhere.