<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Qlik Sense Enterprise on Windows: Error -129 or -128 when reloading app in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Error-129-or-128-when-reloading/ta-p/1713809</link>
    <description>&lt;P&gt;Error -129 or -128 when reloading app.&amp;nbsp; This error appear after a reload of a large amount of data.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;2018-05-25 11:23:25 &amp;nbsp; &amp;nbsp; &amp;nbsp;-129 =&amp;nbsp;&lt;BR /&gt;2018-05-25 11:23:49 &amp;nbsp; &amp;nbsp; &amp;nbsp;Execution Failed&lt;BR /&gt;2018-05-25 11:23:49 &amp;nbsp; &amp;nbsp; &amp;nbsp;Execution finished.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Other errors that may be seen when executing reload script and running out of memory resources include:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;&lt;FONT face="courier new,courier"&gt;Data profiling could not be completed&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;The following error occurred:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;-128&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In the Engine audit and system logs:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;&lt;FONT face="courier new,courier"&gt;Command=Reload app;Result=-128;ResultText=Error: Internal error&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;-129&lt;/STRONG&gt; or &lt;STRONG&gt;-128&lt;/STRONG&gt; are most frequently caused by resource constraints; the system is out of memory.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Review the application to optimize it*&lt;/LI&gt;
&lt;LI&gt;Schedule the task at different times (if a scheduled task is failing that otherwise functions when run manually)&lt;/LI&gt;
&lt;LI&gt;Scale out, allowing for a dedicated reload node&lt;/LI&gt;
&lt;LI&gt;Add additional resources&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;BR /&gt;* While increasing resources is of course an option, the application can be reviewed to ensure it has been optimized. One possible action to take for example is to remove the synthetic keys that are not useful to the data model.&lt;/P&gt;
&lt;P&gt;Synthetic keys aren't always the root cause when something goes wrong but it can be hard to foresee what the impact might be. Therefore, always make sure that synthetic keys are removed from the data model.&lt;BR /&gt;The engine may end up using an excessive amount of time and/or memory when the number of composite keys/Synthetic Tables increases,&amp;nbsp;depending on data amounts, table structure and other factors. Unfortunately, the actual limitations are virtually impossible to predict, which leaves only trial and error as a practical method to determine them.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;For more information about Synthetic keys:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://community.qlik.com/t5/Knowledge-Base/Best-Practice-for-Synthetic-keys-Synthetic-Tables/ta-p/1712575" target="_blank" rel="noopener"&gt;Best Practice for Synthetic keys/Synthetic Tables&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Knowledge-Base/FAQ-Why-should-synthetic-keys-be-removed-from-QlikView/ta-p/1711249" target="_blank" rel="noopener"&gt;FAQ: Why should synthetic keys be removed from QlikView applications?&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environments:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;BR /&gt;&lt;LI-PRODUCT title="Qlik Sense Desktop" id="qlikSenseDesktop"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Apr 2026 05:13:51 GMT</pubDate>
    <dc:creator>Sonja_Bauernfeind</dc:creator>
    <dc:date>2026-04-22T05:13:51Z</dc:date>
    <item>
      <title>Qlik Sense Enterprise on Windows: Error -129 or -128 when reloading app</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Error-129-or-128-when-reloading/ta-p/1713809</link>
      <description>&lt;P&gt;Error -129 or -128 when reloading app.&amp;nbsp; This error appear after a reload of a large amount of data.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;2018-05-25 11:23:25 &amp;nbsp; &amp;nbsp; &amp;nbsp;-129 =&amp;nbsp;&lt;BR /&gt;2018-05-25 11:23:49 &amp;nbsp; &amp;nbsp; &amp;nbsp;Execution Failed&lt;BR /&gt;2018-05-25 11:23:49 &amp;nbsp; &amp;nbsp; &amp;nbsp;Execution finished.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;Other errors that may be seen when executing reload script and running out of memory resources include:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;&lt;FONT face="courier new,courier"&gt;Data profiling could not be completed&lt;/FONT&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;The following error occurred:&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;-128&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;In the Engine audit and system logs:&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;&lt;FONT face="courier new,courier"&gt;Command=Reload app;Result=-128;ResultText=Error: Internal error&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;-129&lt;/STRONG&gt; or &lt;STRONG&gt;-128&lt;/STRONG&gt; are most frequently caused by resource constraints; the system is out of memory.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;Review the application to optimize it*&lt;/LI&gt;
&lt;LI&gt;Schedule the task at different times (if a scheduled task is failing that otherwise functions when run manually)&lt;/LI&gt;
&lt;LI&gt;Scale out, allowing for a dedicated reload node&lt;/LI&gt;
&lt;LI&gt;Add additional resources&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;BR /&gt;* While increasing resources is of course an option, the application can be reviewed to ensure it has been optimized. One possible action to take for example is to remove the synthetic keys that are not useful to the data model.&lt;/P&gt;
&lt;P&gt;Synthetic keys aren't always the root cause when something goes wrong but it can be hard to foresee what the impact might be. Therefore, always make sure that synthetic keys are removed from the data model.&lt;BR /&gt;The engine may end up using an excessive amount of time and/or memory when the number of composite keys/Synthetic Tables increases,&amp;nbsp;depending on data amounts, table structure and other factors. Unfortunately, the actual limitations are virtually impossible to predict, which leaves only trial and error as a practical method to determine them.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;For more information about Synthetic keys:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://community.qlik.com/t5/Knowledge-Base/Best-Practice-for-Synthetic-keys-Synthetic-Tables/ta-p/1712575" target="_blank" rel="noopener"&gt;Best Practice for Synthetic keys/Synthetic Tables&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Knowledge-Base/FAQ-Why-should-synthetic-keys-be-removed-from-QlikView/ta-p/1711249" target="_blank" rel="noopener"&gt;FAQ: Why should synthetic keys be removed from QlikView applications?&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environments:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;BR /&gt;&lt;LI-PRODUCT title="Qlik Sense Desktop" id="qlikSenseDesktop"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Apr 2026 05:13:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Enterprise-on-Windows-Error-129-or-128-when-reloading/ta-p/1713809</guid>
      <dc:creator>Sonja_Bauernfeind</dc:creator>
      <dc:date>2026-04-22T05:13:51Z</dc:date>
    </item>
  </channel>
</rss>

