topic Re: AllowExecuteCommand setting violation detected in QlikView

AllowExecuteCommand setting violation detected

Tue, 13 Sep 2016 03:26:31 GMT

Hi Guys.

Error : AllowExecuteCommand setting violation detected

i'm getting this error while trying execute a batch files, it works fine when i'm using QV11, i just upgrade my qvs into QV12.

i've try this 2 solution :

1. i already try add this line : AllowExecuteCommand=1 in settings.ini (already restart all services but it doesn't work.)

2. already try to change user preference, tab security, check script (allow database write and execute statement)

i've seen this thread :

Allow EXECUTE statement in QlikView 12

https://community.qlik.com/thread/211162

Any Solution ?

Thanks.

Re: AllowExecuteCommand setting violation detected

kaushiknsolanki — Tue, 13 Sep 2016 06:54:41 GMT

Hi,

Hope you have done the setting in Edit Script, Settings, "Can Execute External Command".

Regards,

Kaushik Solanki

Re: AllowExecuteCommand setting violation detected

Tue, 13 Sep 2016 11:07:57 GMT

Yes, i have..

Re: AllowExecuteCommand setting violation detected

krishnacbe — Tue, 13 Sep 2016 14:40:15 GMT

Check whether the user has access to execute batch scripts.

Local Policy Groups -> Login as Batch User

The user should be part of this group. Hope this helps

Re: AllowExecuteCommand setting violation detected

Wed, 14 Sep 2016 08:19:40 GMT

which one ? my qlikview service run as Administrators Group

i double click the batch file, it works fine. but i want to make it works in my qlikview file and schedule in qlikview server.

i guess add this script "AllowExecuteCommand=1" is useless...

Please Qlikview Support Team.. Help Me..

Re: AllowExecuteCommand setting violation detected

krishnacbe — Wed, 14 Sep 2016 18:35:10 GMT

Follow below process in your server and verify whether the Service account is added here.

1. In the Control Panel -> Open Administrative Tools -> Local Security Policy

2. Open Local Policies and highlight User Rights Assignment.

3. Locate Log on as a batch job. Open the properties and check the service account is part of this.

As you have logged into the server with the same credential you were able to run the batch. But the above settings will allow the batch to run remote that is by QMC/Windows task

Re: AllowExecuteCommand setting violation detected

mjamesking — Thu, 01 Dec 2016 19:47:22 GMT

I've just come across this problem where my scheduled tasks were failing due to this setting violation following an upgrade to QVS12. I struggled for a while, contact support and we worked out what I was doing wrong. Solution below:

1. I'd already tried the suggested solution to add AllowExecuteCommand=1 to Settings.ini. Stopped qlikview services, restarted services after saving the change. Didn't work.

2. Turns out i was updating the wrong Settings.ini file. I was updating the one in the QllikView Server folder. The one you need to update is here C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch

Update the Settings.ini file here, setting AllowExecuteCommand=1 stop services, save changes, restart services.

3. Fixed.

Re: AllowExecuteCommand setting violation detected

stevedark — Wed, 25 Jan 2017 21:35:53 GMT

Hi mjamesking‌,

Thanks for sharing up this solution - just saved me a lot of head scratching.

aditya.christian‌ did this work for you also? Please mark it as the correct answer if it did.

Steve

Re: AllowExecuteCommand setting violation detected

cva1962 — Mon, 03 Apr 2017 05:05:52 GMT

Thanks for sharing.

This helpt me at once in QV 12.10 SR4 upgrade from 12.10 IR!!!

Christer

Re: AllowExecuteCommand setting violation detected

rwunderlich — Mon, 03 Apr 2017 07:34:07 GMT

Also see

QV 12.10 “Can Execute External Programs” is back | Qlikview Cookbook

Re: AllowExecuteCommand setting violation detected

yurigodoz — Tue, 19 Sep 2017 16:12:48 GMT

After searching across a community and finding no solution, decide to "tweak" the server.

I found a "Settings.ini" file in the path C:\Users\USER\AppData\Roaming\QlikTech\QlikViewBatch.

Yes, in the folder of the user running the service.

In my case solved the problem.

Re: AllowExecuteCommand setting violation detected

benjaminway — Fri, 27 Oct 2017 16:26:20 GMT

If you have a multi-node environment you only need to do this on the Publisher servers with QDS and only QDS needs to be restarted. Verified on both 11.20 and 12.10.

Re: AllowExecuteCommand setting violation detected

Anonymous — Fri, 03 Nov 2017 08:53:23 GMT

This works for me as well. Updating the Settings.ini in the roaming profile works perfectly when added under windows path C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch

Re: AllowExecuteCommand setting violation detected

gballester — Mon, 19 Feb 2018 14:39:40 GMT

Excelent!!! Work for me!!!

Re: AllowExecuteCommand setting violation detected

warfollowmy_ver — Tue, 20 Feb 2018 00:22:55 GMT

At us this adjustment sometimes becomes = 0, it is necessary to put everything manually again.

Urgently! Again a terrible bug! EXECUTE Command Failed

Re: AllowExecuteCommand setting violation detected

Anonymous — Wed, 07 Mar 2018 14:25:14 GMT

This works for me well. Tks so much!

Re: AllowExecuteCommand setting violation detected

warfollowmy_ver — Mon, 19 Mar 2018 08:25:19 GMT

Was there anyone other than me who met the situation when this setting itself becomes = 0 about once a month after the update to SR2-3?

Re: AllowExecuteCommand setting violation detected

lennyvz1 — Tue, 10 Apr 2018 13:44:02 GMT

It looks like changing the settings.ini file is the proper solution to this issue, but I have a client experiencing the same issue as warfollowmy_verysoonwhere that setting reverts back to 0 at seemingly random times.

Has anyone seen an actual fix for the setting randomly resetting itself?

Re: AllowExecuteCommand setting violation detected

pgrenier — Fri, 18 May 2018 14:08:14 GMT

Thanks for this solution, it corrected the problem for us as well (QV 12.0.20400.0 SR5)

Re: AllowExecuteCommand setting violation detected

lennyvz1 — Fri, 18 May 2018 14:34:26 GMT

It's a bug QV-12269

No real word on when the fix for it will be released.