Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
rothtd
Creator III
Creator III

Exports to Excel fail after upgrade to April 2019 SR3 – resolved, recreated chart objects

After a recent upgrade to April 2019 SR3 we received reports of users receiving the "Export failed please check server log for more details (It's most likely that export process took too much server resources)" message. We successfully tested exports, so this was surprise. We were looking at KB46660 to increase the export limits but found that was not the issue. The issue was corrected by recreating the specific charts in the new version of Qlik. Hope this helps someone.

Symptoms:

  • Export fails for some objects works for others.
  • If a chart is throwing this error, it will always give the error regardless of the amount of data (even one row) is selected.
  • Error to end user is received immediately, not after the default 3 minute timeout
  • Could reproduce issue in QV Desktop – Excel document created with no data
  • QVS logs showed a slightly different error than shown in the support documents. It was identical except was “XlsxExport: Exception(3) is caught…”
  • Recreating the chart from scratch in the new version of QV Desktop resolves the error

 

 

rothtd_0-1593185367068.png

 

 

 

1 Solution

Accepted Solutions
rothtd
Creator III
Creator III
Author

FYI - this appears to be my issue (disabled expressions causing failed Excel export):

https://community.qlik.com/t5/QlikView-Deployment/April-2019-SR3-Export-to-Excel-with-Disabled-Expre... 

View solution in original post

1 Reply
rothtd
Creator III
Creator III
Author

FYI - this appears to be my issue (disabled expressions causing failed Excel export):

https://community.qlik.com/t5/QlikView-Deployment/April-2019-SR3-Export-to-Excel-with-Disabled-Expre...