QS 3.0 bug ? : EXECUTE CMD statement does not work

[edwinwitvoet]

After upgrading to QS 3.0 the EXECUTE cmd does not work.

Double checked all settings as documented here : Execute ‒ Qlik Sense

When running in QS3.0 the following error is shown : EXECUTE statement requires Override Security

Anyone else facing the same problem?

Any workaround?

[dionverbeke]

This is currently the statement from Qlik:

This is by design: this setting was disabled since QlikView 11.20 SR11 and in QlikView 12. It can be re-enabled by modifying the config for the QVB.exe

From the QV12 IR Release Notes:

4.1.1 Management of Unsafe Script Execute Commands

In this release, the AllowExecuteCommand has been set to 0 by default to mitigate against unsafe scripts. If you do not consider this to be a security risk you can switch the value back to 1 in the settings.ini file located in

C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch .

To find where in the tasks the Execute commands fail, set the settings flag EnableQVBLog to 1 in the settings.ini file located in: C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch When enabled, this setting records violation incidents in the QlikView Batch log located in: ProgramData\QlikTech\QlikViewBatch This setting must be configured in all nodes hosting the QDS service in a QlikView setup

[dionverbeke]

And indeed if the bug is fixed...

[Anonymous]

Try adding the following entries in the Settings.ini file

[Settings 7]

OverrideScriptSecurity=1

AllowExecuteCommand=1

Make sure to restart the Qlik services

[edwinwitvoet]

Thanks for the tip. Tested on QS 3.0.

Does not work ....

[#6]

Installed QS 3.01 but the problem still exist, anyone has any updates to this bug?

[Levi_Turner]

To update everyone here, this bug is slated to be fixed in 3.0.2 which has an anticipated GA release date around the tail end of August / early September.