Qlik Community


Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Support Case Portal has moved to Qlik Community! Read the FAQs to start exploring Support resources.

Unable To Export Large Objects To Excel

Digital Support
Digital Support

Unable To Export Large Objects To Excel

Attempting to export a large table from a document on the QlikView AccessPoint fails.

Right-clicking on the object and selecting Send to Excel will either fail or only export 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 a default time limit of 180 seconds, and a 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 later


Edit or add the following config parameters in C:\ProgramData\QlikTech\QlikViewServer\Settings.ini and then restart the services. 


QvExportTimeLimitSec is the time limit in seconds. Use -1 if you do not want to apply a limit. The default values are 180 on the QlikView Server and -1 on Desktop. 

QvExportMemoryLimitMB is the memory limit for exporting objects in MB. Use 0 if you do not want to apply a memory limit. 

The setting needs to be applied in the settings.ini file in as a [Settings 7] property.


[Settings 7]

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 > System > 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.

Labels (1)
Contributor III
Contributor III

I had similar problem with export Large Objects To Excel from AccesPoint.

After changes parametr in stittings to:


Error not show, and export going to end, but end User dont get file,

file create only on Server Temporary Folder, and do not send to User.

Tryed in Chrome and Edge, equal result.

With small file evrething ok.

What the problem, and how fix it?



We use Cluster QlikView Server with 2 nod.
"Alternate Temporary Files Folder Path" assigned shared network path for correct use in cluster.




Digital Support
Digital Support

Hello @Fran_by  

You mentioned that the file is created? So when a user initiated an export, a file it is correctly written on disk in the Temporary file location?

  • If the file is correctly created, then you may be looking at an issue between the client and the server. 
  • Do all users experience the same issue?
  • What if you do the export from the same machine? (locally on the server)
  • You may also want to look at the debug trace of Chrome while trying the export to see if that throws any errors.


For further troubleshooting, I would suggest taking this topic and the answers to my questions over to the QlikView forums for better visibility! 🙂 

Version history
Revision #:
2 of 2
Last update:
‎2020-11-03 07:39 AM
Updated by: