QMC Reload Failure Despite Successful Script in Qlik Sense Nov 2023 and above

[Sebastian_Linser]

Reload fails in QMC even though script part is successfull in Qlik Sense Enterprise on Windows November 2023 and above.

When you are using a NetApp based storage you might see an error when trying to publish and replace or reloading a published app.

In the QMC you will see that the script load itself finished successfully, but the task failed after that.

ERROR QlikServer1 System.Engine.Engine 228 43384f67-ce24-47b1-8d12-810fca589657
 Domain\serviceuser QF: CopyRename exception:
 Rename from \\fileserver\share\Apps\e8d5b2d8-cf7d-4406-903e-a249528b160c.new 
to \\fileserver\share\Apps\ae763791-8131-4118-b8df-35650f29e6f6 
failed: RenameFile failed in CopyRename

ExtendedException: Type '9010' thrown in file
 'C:\Jws\engine-common-ws\src\ServerPlugin\Plugins\PluginApiSupport\PluginHelpers.cpp'
 in function 'ServerPlugin::PluginHelpers::ConvertAndThrow'
 on line '149'. Message: 'Unknown error' and additional debug info:
 'Could not replace collection 
\\fileserver\share\Apps\8fa5536b-f45f-4262-842a-884936cf119c] with
[\\fileserver\share\Apps\Transactions\Qlikserver1\829A26D1-49D2-413B-AFB1-739261AA1A5E],
 (genericException)'

<<< {"jsonrpc":"2.0","id":1578431,"error":{"code":9010,"parameter":
"Object move failed.","message":"Unknown error"}}

ERROR  Qlikserver1  06c3ab76-226a-4e25-990f-6655a965c8f3
  20240218T040613.891-0500  12.1581.19.0  
Command=Doc::DoSave;Result=9010;ResultText=Error: Unknown error
  0  0  298317  INTERNAL&
emsp; sa_scheduler  b3712cae-ff20-4443-b15b-c3e4d33ec7b4
  9c1f1450-3341-4deb-bc9b-92bf9b6861cf  Taskname  Engine  Not available
  Doc::DoSave  Doc::DoSave  9010  Object move failed.
  06c3ab76-226a-4e25-990f-6655a965c8f3

Resolution

Qlik Sense Client Managed version:

• May 2024 Initial Release
• February 2024 Patch 4
• November 2023 Patch 9

Potential workarounds

• Change the storage to a file share on a Windows server

Cause 

The most plausible cause currently is that the specific engine version has issues releasing File Lock operations. We are actively investigating the root cause, but there is no fix available yet.

Internal Investigation ID(s) 

QB-25096
QB-26125

Environment

• Qlik Sense Enterprise on Windows November 2023 and above

[Albert_Candelario]

@ashokbalakrishnan  please confirm you can see them:

Cheers,

Albert

[ashokbalakrishnan]

Thanks @Albert_Candelario. I can see the patch 9 for Nov 2023. 

[tens]

Hi Albert,

As Qlik says that patch 4 is correcting a Qlik security issue (https://community.qlik.com/t5/Support-Updates/Qlik-Sense-Enterprise-for-Windows-New-Security-Patches...). Does it correct this bug (QB-26125) too ? 

Thank you 

Tens

[Albert_Candelario]

Yes, it has the QB-26125 remediation too.
Sense Enterprise on Windows release notes - Februa... - Qlik Community - 2417825

Cheers,

Albert

[Jaden]

Possible Manual Solution:

So, we had this same problem. We had 3 QMC tasks fail and won't run despite the error log saying it completed.

We upgraded to Nov 2023 SR8 the night before this article was published. If your experience is similar to ours, I found a manual workaround. (Keep in mind if you have many tasks failing this will take a long time and might just be best to rollback until a proper fix is in place.)

Steps to manually fix this error:

1. Take a screenshot of your task info so you can recreate it later.

2. Duplicate the app that keeps failing. Ensure you can run this task manually in the hub. Ensure that the app is the same version, etc. as the published app.

3. Delete the published app that is failing to reload.

4. Publish the app that you duplicated in step 2.

5. Use your screenshot from step 1 to set up a brand new reload task for this app.

6. Ensure you can run the task successfully by pressing "Start".

Repeat these steps for any other apps that are failing. Again this is a very manual process but it worked well for us because we only had errors with 3 tasks. 

I hope this helps.

-Jaden

Qlik Sense Enterprise on Windows 

[chris-s]

This workaround only works in very specific instances. Only if you don't have any community sheets and if you don't care about users' bookmarks and stories and if you don't use Mail & Deploy or Nprinting for automated report generation.

Also, there is no guarantee, that the new app with the new task won't start failing as well.

I wouldn't advise anyone to try this workaround; just install the latest patch and everything will be fine again.

[Jaden]

@chris-s Yep, hence I say "just rollback until you can make the proper fix". We don't have any community/NPrinting reports of our apps so it will work if that's the case in your environment. The tasks have been running for a few days now and are updating fine.

[DanielBarbosa1]

Hi @Albert_Candelario I would like to let you know that we have found the following error Command=Doc::DoSave;Result=9010;ResultText=Error: Unknown error in a customer's environment that has Qlik Sense May 2023 Patch 16 version and I would like to know if there is any way to confirm that it is the same bug?

[Albert_Candelario]

@DanielBarbosa1 it should not be as this was very specific, I strongly recommend to look at https://community.qlik.com/t5/Official-Support-Articles/How-to-troubleshoot-the-AppSerializer-SaveAp...

Cheers,

Albert