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]

Hello all,

We are progressing within the investigating and achieving great milestones on it. Nonetheless, is a highly complex investigation due to all the factors involved on the same.

Rest assure this is a priority for our team and our most seasoned and skilled engineers are working tireless on this topic.

We will update the article and/or this comment section as we have further progress within the investigation.

Cheers,

Albert

[Albert_Candelario]

Hello all,

We are progressing further and we have identified were the issue was introduced on a 3rd party library been used by Qlik Sense Client Managed.

We are already identified a solution by reverting the version of such component and we are confident within the next steps that would be starting the testing of the solution during the incoming days before gets into a patch for the affected versions.

We will keep you updated within the further developments.

Cheers,

Albert

[fmarvnnt]

Solution is in progress to be inserted in a patch - right?

FMa

[Sebastian_Linser]

@fmarvnnt Yes the idea is to release this as a standard Qlik Sense patch for November 2023 and February 2024.

[tens]

Thanks for keeping us update about your debug 🤞

[alvarodn]

Nos esta sucediendo lo mismo con Qlikview, ¿a alguien más le pasa?

[tens]

Hello,

Any news about your solution implementation please ?

Thank you 

[Sonja_Bauernfeind]

Hello @tens 

We will update the thread once we have a new significant milestone ready to be shared. 

All the best,
Sonja 

[Albert_Candelario]

Hello all,

A quick update, testing is progressing as expected and we remain confident.

We will update you further within the new significant updates.

Cheers,

Albert

[tens]

Hi,

Thanks you for your feedback. Do you have any potential release date please ? We delayed the rollback but it begin to bé long for my customer.

Thanks you 

Tens