topic Urgently! Again a terrible bug! EXECUTE Command Failed in QlikView

Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Mon, 19 Feb 2018 23:51:49 GMT

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?

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

marcus_sommer — Tue, 20 Feb 2018 15:42:37 GMT

My settings.ini from the server is in a different place:

\\OurServer\Drive\QlikViewServer\ProgramData\QlikViewServer\

If there are several settings.ini they may conflict with eachother.

- Marcus

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Tue, 20 Feb 2018 23:12:59 GMT

There are a lot of settings, I still have not found all the descriptions of the settings.

Whatever it was that I pointed out is responsible for the execution of external commands.

And this file sometimes breaks for unknown reasons.

I could write a snot that will slow down the service, open the file, change it, close it, start the service. But this is not right, the developer must make flexible stable settings, rather than heaps of configuration files, which not everyone even knows about.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Wed, 21 Feb 2018 01:18:40 GMT

Excellent. Only now I found out that because of yesterday's error a part of the repository was incorrectly updated, now I restore the backup and I will do anew update.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Sun, 18 Mar 2018 23:07:26 GMT

It happened again.

When will it be fixed?

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

Anonymous — Wed, 21 Mar 2018 15:18:42 GMT

We are experiencing the same issue since upgrading to QV12. The Allowexecutecommand = 1 resets itself to 0 every few weeks. We are assuming that something is corrupting the settings file to reset it to factory settings. We are using windows audit logging now to try to see which process is accessing the file next time this happens.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Thu, 22 Mar 2018 01:18:54 GMT

Obviously, I already began to think that I was the only one ...

I think the more people will react to this the sooner they correct the mistake.

You could not make screenshots of the page about in the console in the system. There is a hypothesis that failures occur due to updates from version to version, some modules of the program for some reason belong to older versions.

I'd like to check it out. Your screen would help.

A couple of days ago I deleted everything related to QlikView all the folders everywhere, I cleaned the registry. I installed everything again, returned the distribution settings and rights for documents from this my topic https://community.qlik.com/thread/295157 and all modules in the system in the console in about became the same version, let's see how everything will work .

But this is only a hypothesis.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

Anonymous — Thu, 22 Mar 2018 14:34:22 GMT

Show me what screen you are interested in seeing.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Thu, 22 Mar 2018 23:16:35 GMT

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

warfollowmy_ver — Fri, 30 Mar 2018 02:28:29 GMT

The reason most likely was found out. We purchased 11 version of the product, have since been updated to new versions including version 12. If you re-install the 12th version, then the license is not suitable. But if you first install version 11 and install 12 versions on top, then everything works. Therefore, some of the program modules were old. This is also a program error.

Most likely because of errors of incorrect updating which should not be, we began to test services failures as program modules were from different versions and worked incorrectly.

That is, we should not have been updated to version 12 since we have a key from 11. It turned out yesterday when communicating with support. About the upgrade bug from 11 to 12 version with the old key, I also told them.

Yesterday night, 11 versions were installed on the new server. While everything works.

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

Anonymous — Tue, 09 Oct 2018 13:46:35 GMT

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

Re: Urgently! Again a terrible bug! EXECUTE Command Failed

daniel_martin_a — Thu, 28 May 2020 11:16:48 GMT

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.