Task Lists As Failed - But Script Log Seems Successful

[JustinDallas]

Hello Folks,

I looked through my tasks on the QMC and I saw that one failed. 

However, when I look at the script log, I see that the script says it finished successfully.

Has anyone else seen such behavior? 

[Flosom]

Hi,

I'm facing the same issue. Were you able to get a resolution?

[JustinDallas]

I'm not sure what I did.  I think I restarted the server and it went away?  You might also want to put your version of QS in your post too in case it's version specific. 

[Flosom]

Hi,

Yes, I too got the issue resolved for the time being by restarting the servers. Still not sure what the exact issue was. Our version of QS is Qliksense November 2021 Patch 4.

[BTIZAG_OA]

Anyone got clue why this happening? I think its visual bug because script log seems alright

[Tino]

Hi all,

Did you guys were able to solve the problem? If yes, how is your setup, what was the root cause and how did you solve it?

We have the same issue since upgrading to November 2023 Patch3. We have a DEV and a PROD environment. Both environments are multi-node installations. The Root folder is on a NetApp. In the Engine logs it is obvious that Qlik struggles to store the final app into the root folder.

Reloading the app in the data load editor results some times into error 9010 and sometimes it works. Furthermore the issue itself is not consistent. Sometimes the reload tasks work as expected and in the next moment some of them fail. I have also to point out, that it´s independent of which scheduler node and/or engine node the reload is performed.

There are log records like this:

• QF: CopyRename exception: Rename from \\<PATH_TO_CIFS_SHARE>\PROD\Apps\<some_app_id>.new to \\<PATH_TO_CIFS_SHARE>\PROD\Apps\<app_id_of_published_app> failed: RenameFile failed in CopyRename
• QrsPlugin: Could not replace collection [\\<PATH_TO_CIFS_SHARE>\PROD\Apps\<add_id_of_published_app>] with [\\Kuka.int.kuka.com\s\QSENSE_SYSTEM\PROD\Apps\Transactions\DEAU1SVQSEN16.kuka.int.kuka.com\<some_unknown_id>]

We have already raised a ticket which is still in progress and has been recently escalated to the R&D. Any possible impact from e.g. Antivirus, or locked sessions from the network storage have been already investigated and can be excluded on a first view.

Although we have already a ticket which is in work, I´ve decided to share this information here with much as possible information regarding the environment. The reason therefor is to find out, whether there are some similarities between the environments of the affected systems.

I would highly appreciate If you could share some more information, or in case the topic has been solved, the way how you´ve solve it. I will keep this post also updated as soon as there are some significant information.

Best regards
Tino

[BTIZAG_OA]

Hello Tino,

I was raised a ticket too but its closed very quickly with the suggestion that i should check qliksense folder share settings 😄 which is shared btw. You should feel lucky that you escalated your ticket please inform us with the solution. Same log records also occurs in out qlik sense site, somehow windows cannot replace/rename the qvf file also we always encountered this with big sized qvfs.

[NadiaB]

Are there any errors in the Engine logs or Scheduler logs related to that specific reload?

[Tino]

Hi BTIZAG_OA,

Thanks for your feedback.
I our case this occurs also with "small" apps (40 MB disk size).

[Tino]

Hi Nadia,

yes there are records in the logs, but there is no sufficient info within the log (has been checked also by the Qlik Support). Furthermore and after some more investigation I´ve noticed that in every case of a failed reload task, it fails at the same sequence (Process Monitor). In this sequence a new app (<some_random_app_id>.new) is created which will be renamed in the next step into <app-id-of-the-published-app>. At this point an access denied occurs. I have to point out that all previous file activities as well as all following file activities work as expected.

As the Qlik Support is already working on this topic, I´m trying to share as much as possible information here, in order to find out if there are any kind of similarities with other affected users, which could help to identify the root cause.

Best regards
Tino