KB-1731 Engines fail to start after upgrade with “ShaMismatchException” or "EngineReplayException"

pauline.delacruz — Tue, 05 Aug 2025 15:53:52 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 8/5/2025 3:53:52 PM

Symptoms

Following an upgrade, the Appian Engines fail to start successfully. One of the following errors are also observed in the service_manager.log:

K sha256 was <sha>, but the transaction log sha was <sha>

ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for <engine>: 
TransactionReplayFailedEvent{createdInstant=engineId=<engine>, startTransactionId=Optional[0], transactionsReplayedCount=***, 
cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, 
caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engine(s) were improperly shut down before upgrading and there are transactions that have not been checkpointed. Attempting to proceed with an upgrade can result in silent data corruption.

An Appian on Kubernetes (AoK) site can encounter this issue if the Service Manager finalizer is removed during the site shutdown prior to the upgrade.

Action

Self-Managed Appian

Restore the site to a backup from prior to the upgrade.
Perform a clean shutdown as documented in the Update Guide.
Ensure that there are no checkpointing errors in the service_manager.log. See KB-2068 for detailed information on how to understand checkpointing in the logs.
Re-attempt the upgrade.

Appian on Kubernetes

Stop the site by deleting the Appian CR. Since the Service Manager pods will be unable to start, deleting the CR will require removing the Service Manager finalizer as well.
Change the Appian version in the Appian CRD back to the Appian version prior to the upgrade.
1. Note that if your CRD specifies a tag for component images as well, the tags must also be updated.
Start the site back up. Some components may not come up successfully, but this is expected. Wait until all of the Service Manager pods are in a Ready state.
Re-attempt the upgrade. Do NOT remove the Service Manager finalizer while shutting the site down.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: August 2025

Tags: engines, installation, infrastructure, service manager

KB-1731 Engines fail to start after upgrade with “ShaMismatchException” or "EngineReplayException"

Parmida Borhani — Tue, 01 Feb 2022 06:46:47 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 2/1/2022 6:46:47 AM

Symptoms

Following an upgrade, the Appian Engines fail to start successfully. One of the following errors are also observed in the service_manager.log:

K sha256 was <sha>, but the transaction log sha was <sha>

ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for <engine>: 
TransactionReplayFailedEvent{createdInstant=engineId=<engine>, startTransactionId=Optional[0], transactionsReplayedCount=***, 
cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, 
caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engine(s) were improperly shut down before upgrading and there are transactions that have not been checkpointed. Attempting to proceed with an upgrade can result in silent data corruption.

Action

Restore the site to a backup from prior to the upgrade.
Perform a clean shutdown as documented in the Update Guide.
Ensure that there are no checkpointing errors in the service_manager.log. See KB-2068 for detailed information on how to understand checkpointing in the logs.
Re-attempt the upgrade.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2022

Tags: engines, installation, infrastructure, service manager

KB-1731 Engines fail to start after upgrade with “ShaMismatchException” or "EngineReplayException"

Parmida Borhani — Tue, 01 Feb 2022 06:41:01 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 2/1/2022 6:41:01 AM

Symptoms

Following an upgrade, the Appian Engines fail to start successfully. One of the following errors are also observed in the service_manager.log:

K sha256 was <sha>, but the transaction log sha was <sha>

ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for <engine>: TransactionReplayFailedEvent{createdInstant=engineId=<engine>, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engine(s) were improperly shut down before upgrading and there are transactions that have not been checkpointed. Attempting to proceed with an upgrade can result in silent data corruption.

Action

Restore the site to a backup from prior to the upgrade.
Perform a clean shutdown as documented in the Update Guide.
Ensure that there are no checkpointing errors in the service_manager.log. See KB-2068 for detailed information on how to understand checkpointing in the logs.
Re-attempt the upgrade.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2022

Tags: engines, installation, infrastructure, service manager

KB-1731 Engines fail to start after upgrade with “ShaMismatchException” or "EngineReplayException"

Parmida Borhani — Mon, 31 Jan 2022 06:22:12 GMT

Revision 11 posted to Appian Knowledge Base by Parmida Borhani on 1/31/2022 6:22:12 AM

Symptoms

Following an upgrade, the Appian Engines fail to start successfully. One of the following errors are also observed in the service_manager.log:

K sha256 was <sha>, but the transaction log sha was <sha>

ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for <engine>: TransactionReplayFailedEvent{createdInstant=engineId=<engine>, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engine(s) were improperly shut down before upgrading and there are transactions that have not been checkpointed. Attempting to proceed with an upgrade can result in silent data corruption.

Action

Restore the site to a backup from prior to the upgrade.
Perform a clean shutdown as documented in the Update Guide.
Ensure that there are no checkpointing errors in the service_manager.log. See KB-2068 for detailed information on how to understand checkpointing in the logs.
Re-attempt the upgrade.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2022

Tags: engines, installation, infrastructure, service manager

KB-1731 Engines fail to start after upgrade with “ShaMismatchException” or "EngineReplayException"

Parmida Borhani — Thu, 20 Jan 2022 05:32:05 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 1/20/2022 5:32:05 AM

Symptoms

Following an upgrade, the Appian Engines fail to start successfully. One of the following errors are also observed in the service_manager.log:

K sha256 was <sha>, but the transaction log sha was <sha>

ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for <engine>: TransactionReplayFailedEvent{createdInstant=engineId=<engine>, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engine(s) were improperly shut down before upgrading and there are transactions that have not been checkpointed. Attempting to proceed with an upgrade can result in silent data corruption.

Action

Restore the site to a backup from prior to the upgrade.
Perform a clean shutdown as documented in the Update Guide.
Ensure that there are no checkpointing errors in the service_manager.log. See KB-2068 for detailed information on how to understand checkpointing in the logs.
Re-attempt the upgrade.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: January 2022

Tags: engines, installation, infrastructure, service manager

KB-1731 Engines fail to start-up after migration with "EngineReplayException" observed in service_manager.log

Jordan Horwat — Fri, 28 Sep 2018 14:34:08 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 9/28/2018 2:34:08 PM

Symptoms

Engines fail to start up during this step of the upgrade with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down without being checkpointed before they were copied over to the new environment.

Action

Shut down Appian engines as documented in the Update Guide before migrating the engine KDB files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Jordan Horwat — Fri, 28 Sep 2018 10:23:36 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 9/28/2018 10:23:36 AM

Symptoms

Engines fail to start up during this step of the upgrade with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down without being checkpointed before they were copied over to the new environment.

Action

Shut down Appian engines as documented in the Update Guide before migrating the engine KDB files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Thu, 20 Sep 2018 15:43:54 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 9/20/2018 3:43:54 PM

Symptoms

Engines fail to start up during this step of the upgrade with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down without being checkpointed before they were copied over to the new environment.

Action

Shut down Appian engines as documented in the update guide before migrating the engine KDB files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Tue, 18 Sep 2018 09:44:08 GMT

Revision 6 posted to Appian Knowledge Base by Tejas Kargutkar on 9/18/2018 9:44:08 AM

Symptoms

Engines fail to start up during an upgrade with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down without being checkpointed before they were migrated.

Action

Shut down Appian engines as documented in the update guide before migrating the engine KDB files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Thu, 13 Sep 2018 13:20:50 GMT

Revision 5 posted to Appian Knowledge Base by Tejas Kargutkar on 9/13/2018 1:20:50 PM

Symptoms

Engines fail to start up after migration with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down before they were migrated.

Action

Shut down Appian engines as documented in the update guide before migrating the engine KDB files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Thu, 13 Sep 2018 13:14:12 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 9/13/2018 1:14:12 PM

Symptoms

Engines fail to start up after migration with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down before they were migrated.

Action

Shut down Appian engines as documented in the update guide before migrating the engine kdb files and redo the migration.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Tue, 11 Sep 2018 17:30:44 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 9/11/2018 5:30:44 PM

Symptoms

Engines fail to start up after migration with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down before they were migrated.

Action

Shut down Appian engines as documented in the update guide before migrating the engine kdb files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Tue, 11 Sep 2018 17:25:57 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 9/11/2018 5:25:57 PM

Symptoms

Engines fail to start up after migration with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down before they were migrated.

Action

Shut down Appian as documented in the update guide before migrating the engine kdb files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure, service manager

DRAFT KB-XXXX Engines fail to start-up after migration with "EngineReplayException" observed in service-manager.log

Tejas Kargutkar — Tue, 11 Sep 2018 17:25:30 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 9/11/2018 5:25:30 PM

Symptoms

Engines fail to start up after migration with the following error observed in the <APPIAN_HOME>\logs\service_manager.log:

[KomodoEventBus-60] ERROR com.appian.komodo.engine.status.ReplayStateProvider - Error replaying transactions for analytics00: TransactionReplayFailedEvent{createdInstant=engineId=analytics00, startTransactionId=Optional[0], transactionsReplayedCount=***, cause=com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update}, caused by: com.appian.komodo.engine.EngineReplayException: Replaying request with transaction id *** did not result in an update

Cause

Engines were improperly shut down before they were migrated.

Action

Shut down Appian as documented in the update guide before migrating the engine kdb files.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: September 2018

Tags: engines, infrastructure