topic Re: QS 3.0 bug ? : EXECUTE CMD statement does not work in Management & Governance

QS 3.0 bug ? : EXECUTE CMD statement does not work

edwinwitvoet — Fri, 01 Jul 2016 07:41:28 GMT

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?

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

erwinvink — Mon, 04 Jul 2016 09:43:25 GMT

Same problem here, no solution found yet. Was working until QS 2.2.4. After update execute won't work anymore.

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

eliran — Mon, 04 Jul 2016 12:09:38 GMT

Same here, working fine on 2.2.4 server, not working on Sense Server 3.0.0

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

dionverbeke — Mon, 04 Jul 2016 13:10:57 GMT

To allow Execute in Qlik Sense, you must enable Legacy mode.

Dion

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

eliran — Mon, 04 Jul 2016 13:23:22 GMT

It *was* working before, other then upgrading the server, there was no change.

I think it's a bug in the version.

There is already a ticket open on the subject at Qlik.

This is the relevant info to enable it on previous versions

https://help.qlik.com/en-US/sense/3.0/Subsystems/Hub/Content/Scripting/ScriptRegularStatements/Execute.htm

https://help.qlik.com/en-US/sense/3.0/Subsystems/Hub/Content/LoadData/disable-standard-mode.htm

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

edwinwitvoet — Mon, 04 Jul 2016 14:57:08 GMT

Exactly. Thanks for your replies.

Where did you see that there is a ticket open @ Qlik?

I have submitted a support request myself on July 1st, but haven't heard anything yet.

Any workarounds?

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

eliran — Mon, 04 Jul 2016 19:35:28 GMT

What I have done, is scheduling a windows based task.

It's not the solution I need, but that's what I got at the moment.

I hope Qlik will issue a fix soon.

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

dionverbeke — Mon, 04 Jul 2016 20:36:06 GMT

It says it there:

This statement is not supported in standard mode. See File system access restriction

I hope they find a better way to run external commands. Like R.

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

erwinvink — Tue, 05 Jul 2016 15:54:36 GMT

Hi Dion,

Thanks for your answer. But like I said, execute was working before the update. That means that I know how to disable standard mode etc.. After the update, none of the settings was changed but execute isn't working anymore. This have nothing to do with standard mode. For your information, I (and I guess Edwin also, cause he said he checked everything twice) enabled legacy mode and add override security settings to the settings.ini file.

So far as I can see, it's a bug in the update and nothing else.

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

edwinwitvoet — Tue, 05 Jul 2016 16:12:15 GMT

That's correct.

Today Qlik Support confirmed that this is now officially listed as a bug report in 3.0 and given high priority. Solution / workaround is expected in the coming days. Keep you posted ...

Information from Qlik Support below:

Related Bug : Legacy mode in Sense 3.0. does not work

Bug Id : QLIK-61452

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

dionverbeke — Wed, 06 Jul 2016 13:42:43 GMT

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

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

dionverbeke — Wed, 06 Jul 2016 13:44:29 GMT

And indeed if the bug is fixed...

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

Anonymous — Thu, 07 Jul 2016 13:23:43 GMT

Try adding the following entries in the Settings.ini file

[Settings 7]

OverrideScriptSecurity=1

AllowExecuteCommand=1

Make sure to restart the Qlik services

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

edwinwitvoet — Thu, 07 Jul 2016 18:19:43 GMT

Thanks for the tip. Tested on QS 3.0.

Does not work ....

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

Tue, 09 Aug 2016 15:23:27 GMT

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

Re: QS 3.0 bug ? : EXECUTE CMD statement does not work

Levi_Turner — Wed, 10 Aug 2016 20:09:27 GMT

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.