Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
QlikView document not loaded: LoadDocument caught exception -129 - possibly corrupt file
Article Number: 000063182 | Last Modified: 2020/08/06Description
A QlikView document is not loaded into memory. Logs show these errors:
20190124T232819.000Z0001-01-01 00:00:0020190125T101832.000Z1300ErrorDOC loading: LoadDocument caught exception -129
20190124T232819.000Z0001-01-01 00:00:0020190125T101832.000Z1300ErrorDOC loading: Failed to load document path-of-the-document possibly corrupt file.
The document is not actually corrupt, and it can be opened in other environments.
Environments:
QlikView 12.10 or higher
Resolution
The "possibly corrupt file" message, in this case, is just a possibility that the server is considering, but it doesn't always reflect the reality.
Exception -129 is usually a symptom of resource issues, in particular when it comes to RAM.
Consider troubleshooting options in Troubleshooting Qlik Engine "Internal Inconsistency Type A" Error
Exception -129 is usually a symptom of resource issues, in particular when it comes to RAM.
Consider troubleshooting options in Troubleshooting Qlik Engine "Internal Inconsistency Type A" Error
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us