topic Re: QDS is overwriting the Allowexecute Command in QlikView

QDS is overwriting the Allowexecute Command in windows 2008 server

shree909 — Mon, 26 Jan 2026 18:19:17 GMT

Hi Folks, Recently we updated our qlikview from 11.2 SR 15 to 12.1 SR 8, on windows 2008 Box. To run the external Commands like "Execute" modified the batch file in Settings .ini changed AllowExecuteCommand=1 on C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch When a task is triggered from the QMC, QDS is changing the value from 1 to 0 and qvws are getting failed. When the same upgrade was done on windows 2012 it works fine. Not sure why that is behaving weird , is that due to Windows server 2008 or something else. Thanks for your help in advance. Thanks sree

Re: QDS is overwriting the Allowexecute Command

shree909 — Wed, 01 Nov 2017 18:11:43 GMT

Was able to find out after doing some research Navigate to: C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch Settings.ini file Press Enter on the keyboard to insert a blank line below the AllowExecuteCommand=1 line This will apply only to windows 2008 server, with 2012 it works fine. Thanks

Re: QDS is overwriting the Allowexecute Command in windows 2008 server

spcpeters — Thu, 13 Sep 2018 08:07:21 GMT

Ran into the same issue, will try out your solution. Thanks!

Re: QDS is overwriting the Allowexecute Command in windows 2008 server

Chip_Matejowsky — Thu, 13 Sep 2018 18:37:46 GMT

Hi Stephan,

Have a look at the Public Qlik Knowledge Base: https://qliksupport.force.com/articles/000030062

If you have further questions, just update the thread.

Best Regards,

Chip

Re: QDS is overwriting the Allowexecute Command in windows 2008 server

rwunderlich — Thu, 13 Sep 2018 18:49:29 GMT

Or read the original blog post. Which has the title spelled correctly

Authorizing the Script EXECUTE Statement | Qlikview Cookbook

Re: QDS is overwriting the Allowexecute Command in windows 2008 server

spcpeters — Fri, 14 Sep 2018 06:08:32 GMT

Thanks both.

I've updated the AllowExecuteCommand=1 setting in the .ini file. The issue I'm running into is the same as the topic poster: the AllowExecuteCommand statement reverts back from 1 to 0. Strangely, this only seems to have occured after a few days. It runs fine in the time before that, with multiple scripts calling external programs.

I just tested the solution of the topic poster of inserting a blank line after the statement, but that also gets reverted back within a couple of minutes.

Running 12.20 SR5 by the way.