Unable To Export Large Objects To Excel After Upgrading to November 2017 due to additional configuration parameters.
After upgrading to QlikView November 2017 release or newer, attempting to use Excel Export by right-clicking > "Send to Excel", the export will fail or file will bring only partial data.
The following line will be registered in the QlikView Server Events log file:
System: XlsxExport: Exception(29803) is caught. Normally this is caused by over-sized excel file. Please check the Cpu time and Memory Limit for excel export feature. Now we have default time limit of 180 seconds, and memory limit of 0 MB for QlikView Server.
In this case 0MB means no limit on the size of the Excel export.
- QlikView 12.20 (November 2017) and up
November 2017 introduces additional configuration parameters for Data Export. See article QlikView November 2017 Export to XLSX
for more information.
Edit or add the following config parameters in C:\ProgramData\QlikTech\QlikViewServer\Settings.ini and Restart Services:QvExportTimeLimitSec=-1
QvExportTimeLimitSec (Use -1 if you don't want time limit; Default Values:-->On Server: 180 Desktop: -1)
Time limit for exporting object to Xlsx. Integer number in seconds.
QvExportMemoryLimitMB (Use 0 if you don't want memory limit;)
Memory limit for exporting object to Xlsx. Integer number in MB.The setting needs to be applied in the settings.ini file in as a [Settings 7] property. Example:
Please note that if the setting is added under the [Authentication] property, it will not be read by the QlikView Server Service.
Also note that this issue can be caused by an issue with the customer's Alternate Temporary Files Folder Path in the QMC under QMC > Systtem > Setup > QVS > Folders. If the path isn't correct or points to a folder that no longer exists, all Excel exports will fail. You will see entries in QVS event logs regarding the bad path.Please, note that on 12.40 SR2, SR3 this work around does not apply as there is a product defect, so even changing the above configuration you will still get same error message.
Please, contact support for further updates.