Bug! Quickly! QlikView November 2017 SR1 and SR2 and SR3. Tell the developers!

[warfollowmy_ver]

Bug! Quickly! QlikView November 2017 SR1 and SR2 and SR3. Tell the developers!

After reload script the document in desktop, triggers do not see macros!

While I understood this, I broke my head! Tell the developers!

Open the document in the latest version of the desktop QV and click on the reload... If you run the macro after opening, everything works, if you first reload, then does not see the trigger of macro...

[warfollowmy_ver]

Our company paid for support only the first year. It is in fact useless, and we refused it, pay for the fact that we will look for bugs and report - this is humor.

There are also users who use the desktop version and I do not have to talk about support, I also want to remind you that today's support xlsx format was done almost 10 years after - it's about support and development.

It's very bad that they will not pass on the information, then I will not write anything here anymore, because it's pointless.

[xtrimf]

I have November 2017 SR1 and have the same issue.

Workaround: adding this line to settings.ini "EnableBnfReload=0" solved this problem.

Its still a bug thou...

[warfollowmy_ver]

and SR3

[sfatoux72]

‌Yes it works well

You could also add the ///$bnf off tag at the top of the script (The tag must be in the first 50 characters of the script).

[warfollowmy_ver]

I checked it works. But I have many users of the terminal desktop client, I do not understand what this affects, what is the use of it.

In addition, the vendor claims that it does not recommend disabling it http://www.qlikisrael-support.com/Knowledgebase/Article/GetAttachment/258/2098704.

It is important for me to understand why such a mistake occurs, is it normal? Now I will disconnect, and then because of this there may be new errors in future.

I'm trying to understand why this is even happening and is this a mistake that they will fix?

[sfatoux72 · Accepted solution]

‌No it’s not normal, it’s a bug introduced with the new BNF script reload mode.

The bug is reported to Qlik R&D and they work to correct it.

In the meantime, you need to stop the new “BNF script reload mode” on application where it’s necessary, like recommended by Qlik on the same document.

[warfollowmy_ver]

Clear. For us, this is too time-consuming. There are no problems at the access point. And I will not update the desktop version until I fix it. Thanks for the distinct answer.

[warfollowmy_ver]

and SR4

[Anonymous]

Spent much of the day troubleshooting this as it worked fine in our previous setup (12.10.206 SR8).  We upgraded to 12.20.206 SR5 early this week and found the .bat files were terminating without generating an email.  After much research, what I found is exactly what everyone is discussing here, it is a bug.  After many trial and errors, I found a simple solution to the problem.  I went back to our old environment (12.10.206 SR8) and copied the qv.exe file.  I placed the copy of the file on the desktop of the new server using the admin account.  I then edited the .bat file to point to the old version of the qv.exe on the desktop and not the qv.exe under C:\Program Files\QlikView.

You may need to edit the Windows Task and delete the 'Actions' and create a new one that points to the new/altered file.  Windows Task Scheduler once again firing OnPostReload.  Hope this helps!

Example .bat file

"C:\Users\qvservices\Desktop\Qv.exe" /l /NoSecurity "C:\ProgramData\QlikTech\Documents\08QlikView_Dashboards\Email_Test.qvw"