https://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appianen-USTelligent Community 12https://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appianTue, 30 Oct 2018 15:41:13 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fabf0e06-9cb4-4480-9719-348a682d7400Jordan Horwathttps://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appian#commentsCurrent Revision posted to Appian Knowledge Base by Jordan Horwat on 10/30/2018 3:41:13 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When a user clicks on an action in Appian, the user cannot see its configured task but gets a message saying &quot;Action successfully completed&quot;. It is possible that there is an underlying issue in the Appian Engines if an error similar to the following is seen in <strong>db_PA*.log</strong>:</p> <pre>YYYY-MM-DD HH:MM:ss [PA000XX] {paXXX.kdb 15388} (Default) ERROR .a.p.ANLYZE.i &quot;Unexpected Exec Engine 1 was trying to send an Incremental Update.&quot; </pre> <h2 id="cause">Cause</h2> <p>The above error means that the analytics engines could not recognize the execution engines. This occurs when .KDB files are copied over to an incorrect directory. It may be possible this issue originated during a migration that took place in the past.</p> <p>The inconsistent engine will start but the errors in the logs will block it from taking on any new processes. This is the reason why the action skips to the success message directly without starting the process.</p> <h2 id="action">Action</h2> <p>In order to get the problematic engine to receive new processes, please migrate the .KDB files into the correct directory from a backup. Make sure that all .KDB files from the source installation directory are copied to the corresponding engine directory in the target environment.</p> <p>If restoring from a backup is not possible, please contact Appian Support for further assistance.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, installation, processes, infrastructure</div> https://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appian/revision/2Mon, 30 Jul 2018 04:09:42 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fabf0e06-9cb4-4480-9719-348a682d7400Parmida Borhanihttps://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appian#commentsRevision 2 posted to Appian Knowledge Base by Parmida Borhani on 7/30/2018 4:09:42 AM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When a user clicks on an action in Appian, the user cannot see its configured task but gets a message saying &quot;Action successfully completed&quot;. It is possible that there is an underlying issue in the Appian Engines if an error similar to the following is seen in <strong>db_PA*.log</strong>:</p> <pre>2015-11-11 20:57:33 [PA000XX] {paXXX.kdb 15388} (Default) ERROR .a.p.ANLYZE.i &quot;Unexpected Exec Engine 1 was trying to send an Incremental Update.&quot; </pre> <h2 id="cause">Cause</h2> <p>The above error means that the analytics engines could not recognize the execution engines. This occurs when .KDB files are copied over to an incorrect directory. It may be possible this issue originated during a migration that took place in the past.</p> <p>The inconsistent engine will start but the errors in the logs will block it from taking on any new processes. This is the reason why the action skips to the success message directly without starting the process.</p> <h2 id="action">Action</h2> <p>In order to get the problematic engine to receive new processes, please migrate the .KDB files into the correct directory from a backup. Make sure that all .KDB files from the source installation directory are copied to the corresponding engine directory in the target environment.</p> <p>If restoring from a backup is not possible, please contact Appian Support for further assistance.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, installation, processes, infrastructure</div> https://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appian/revision/1Fri, 24 Feb 2017 14:01:50 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fabf0e06-9cb4-4480-9719-348a682d7400Nick Vigilantehttps://community.appian.com/support/w/kb/350/kb-1128-error-a-p-anlyze-i-unexpected-exec-engine-x-was-trying-to-send-an-incremental-update-error-thrown-when-running-an-action-in-appian#commentsRevision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 2:01:50 PM<br /> <div class="row content_container"> <h2 id="symptoms">Symptoms</h2> <p>When a user clicks on an action in Appian, the user cannot see its configured task but gets a message saying &quot;Action successfully completed&quot;. It is possible that there is an underlying issue in the Appian Engines if an error similar to the following is seen in <strong>db_PA*.log</strong>:</p> <pre>2015-11-11 20:57:33 [PA000XX] {paXXX.kdb 15388} (Default) ERROR .a.p.ANLYZE.i &quot;Unexpected Exec Engine 1 was trying to send an Incremental Update.&quot; </pre> <h2 id="cause">Cause</h2> <p>The above error means that the analytics engines could not recognize the execution engines. This occurs when .KDB files are copied over to an incorrect directory. It may be possible this issue originated during a migration that took place in the past.</p> <p>The inconsistent engine will start but the errors in the logs will block it from taking on any new processes. This is the reason why the action skips to the success message directly without starting the process.</p> <h2 id="action">Action</h2> <p>In order to get the problematic engine to receive new processes, please migrate the .KDB files into the correct directory from a backup. Make sure that all .KDB files from the source installation directory are copied to the corresponding engine directory in the target environment.</p> <p>If restoring from a backup is not possible, please contact Appian Support for further assistance.</p> <h2 id="affected-versions">Affected Versions</h2> <p>This article applies to all versions of Appian.</p> </div> <p>Last Reviewed:&nbsp;February 2017</p> <div style="clear:both;"></div> <div style="font-size: 90%;">Tags: engines, processes</div>