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

Potential workarounds

• Roll back your upgrade to a version earlier than November 2023
• 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.

An update will be provided as soon as there is more information to share.

 

Internal Investigation ID(s) 

QB-25096
QB-26125

Environment

• Qlik Sense Enterprise on Windows November 2023 and above

[Christoph_Wi]

Same issue here! - Any News? - Pls Fix
Many Thx

[Sonja_Bauernfeind]

Hello @anily86 

No fix version is available yet. Please communicate with the support agent who'll be working on you for this issue.

Hello @Christoph_Wi 

Please log a support ticket with us, providing us with log files, versions used, and information about symptoms and whether or not this is happening in your development, UAT, or production environment. 

Qlik is actively working on providing a fix, but in the meantime support is your best bet.

All the best,
Sonja 

[sreehari_m]

We are on Nov 2022 Patch 12 and we have the issue in this version too. A case is already submitted from our side. 

[chris-s]

I'm facing the exact same issue with a customer on their production environment. Unfortunately, this issue isn't listed as "known issue" for the latest version, otherwise we wouldn't have upgraded.

We're currently trying to move the Apps folder onto a Windows/Samba share instead of the NetApp based storage, which will be magnitudes slower and is therefore not a permanent solution.

If this doesn't fix the issue, we'll have to do a rollback, which will be fun since it's a cluster installation that we'll restore from backups... an advance notice would've been really nice.

[tens]

Any News about this bug resolution ?

[alvarodn]

Ayer me escribierón de soporte y me comentaron que ya han conseguido reproducir el error y que ahora pueden empezar a buscar la solución, esperemos que pronto lo tengan solucionado

[Albert_Candelario]

@rene_eykelberg 

Thanks for sharing the information and remind about Qlik NDA's, furthermore you should not disclose our Support case comments in public forums.

We are progressing within the investigation and we made great progress as shared above while this still remains a very complex issue, neither assume this is a defect on Qlik's code as also mentioned.

This issue is a priority for us and we will keep updating you on our progress towards its conclusions.

Cheers,

Albert

[lucadibenedetto86]

Hi @Albert_Candelario ,

is there any update about the progression of the analysis of the issue? It's really difficult to apply the workarounds suggested in the topic so we really hope that you are able to find a solution as soon as possible.

Thanks in advance for your support.

Luca

[rsanz]

I agree, we are stuck in May 2023 after a painful rollback and it's almost a year old version.

Thanks in advance

Rafael

[chris-s]

Two weeks ago, my customer and I did a workaround and moved (only) the Apps folder onto another server with windows shares (a few hundred GB worth of data), but this isn't a permanent solution.

We are also eagerly waiting on a fix and this workaround works in the meantime.