Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
warfollowmy_ver
Creator III
Creator III

Urgently! Again a terrible bug! EXECUTE Command Failed

Bug again...

This morning I went to work, I found out that a huge part of the documents had been updated with an oshbika. All of which have the execution of external commands.

For the second time break down the settings for the file

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

Authorizing the Script EXECUTE Statement | Qlikview Cookbook

AllowExecuteCommand

I apply the screen. I had to slow down the service, again make changes and start the services.

When these clever men make normally working settings not in the configuration files that break, but in the normal interface?

Developers understand the criticality of these moments?

Also it is unclear why this file is constantly updated, almost every minute?

11 Replies
Anonymous
Not applicable

In our case, Qlik's technical team recommended changes to the settings.ini that ended up resolving the issue. It is a known bug.

daniel_martin_a
Partner - Contributor II
Partner - Contributor II

Hi Mlindekeit.

Please, did you found a solution to QlikView not change it automatically?

I had same problem and I needed change from 0 to 1 for second time. I'm afraid it may happen again.

Thanks.

Regards.