Reload from QVDs fails with: Failed to open file in write mode for file: \\SRVR\folder\XXX.qvd

[Sonja_Bauernfeind]

Reload from QVDs failing in Qlik Sense April 2020 or later and QlikView 12.50 with System error: Failed to open file in write mode for file: \\servername\foldername\XXX.qvd

Other symptoms may include:

• Errors for sharingViolation in the logs
• QVDs being locked requiring manual unlocking of files via the Open Files menu.

Environments:

• Qlik Sense April 2020 or later (see fix versions)
• QlikView 12.50 to 12.50 SR2 (see fix versions) 

Resolution:

The behaviour was adjusted in:

• QlikView 12.50 SR3
• Qlik Sense April 2020 Patch 8
• Qlik Sense June 2020 Patch 7
• Qlik Sense September 2020 Patch 2
• Qlik Sense November 2020 IR

Manual Workaround:

Implement the following ini setting EnableQvdAsyncWrite=0.

Steps for Qlik Sense:

• Stop the Qlik Sense Engine and Qlik Sense Service Dispatcher services on all nodes with engines.
• For each of the nodes: open Notepad as Administrator
• Open the Settings.ini file (by default located in C:\ProgramData\Qlik\Sense\Engine\Settings.ini)

[Settings 7]
EnableQvdAsyncWrite=0

• Please make sure Enter/Return are pressed to create a new blank line after the last setting.
• Save the file
• After these changes have been made on all nodes, start the Qlik Sense Engine and Qlik Sense Service Dispatcher services on each node.

Steps for QlikView:

• Reloads in QlikView are carried out by the QVB.exe. So we need to change the settings.ini for the QVBs, rather than the QlikView Server.
• Stop all currently running reloads (qvb.exe). 
• Stop the QlikView Distribution Services on all nodes
• For each node running a Distribution Service, open Notepad as an Administrator
• Open the QVS Settings.ini file (by default, located in C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch)
• Modify the Settings.ini using this schema:

[Settings 7]
EnableQvdAsyncWrite=0

• Ensure that the entry is entered under [Settings 7] section and not under the [Authentication] section (if entered under [Authentication] section, the entry will not be read by the QVS)
• Save the file 
• These changes have been made on all nodes running reloads.
• Start the Distribution Services 

Cause:

There is an optimization in QVD writing in the April 2020 release and later of Qlik Sense Enterprise for Windows and in QlikView 12.50, which gives a noticeable performance boost but on some systems can lead to hung reload jobs. The reason for hung reloads is not immediately related to the optimization itself, but rather to the new write speed.

Product Defect ID:

• QLIK-102376
• QV-20266

[qliker2]

Hi Sonja,

thanks for this article! Is the resolution resolving this problem in newer versions automatically or do you have to implement the manual workaround anyways?

And should the resolution also work for the problem, you described in 2013 here: Concurrent Read and Write from/to a QVD file may r... - Qlik Community - 1711386

...so if you have concurrent read/write access?

[Sonja_Bauernfeind]

Hello @qliker2

This does not require manual configuration if the issue you were seeing is related to this specific setting and you have upgraded.

However, it will not resolve Concurrent Read and Write from/to a QVD file may result in one of the tasks failing. Read and Write at the same time will continue to cause file locks and the schedule will need to be adjusted.

All the best,
Sonja

[fmarvnnt]

It happens again on a multi-node site with 2 Back Ends and Version Aug 2023 P5 running (

EnableQvdAsyncWrite=0

already inserted monthes ago)

FMa