KB-1577 "Expected 256, was 257" exception regarding Appian engine security token prevents engine startup

pauline.delacruz — Fri, 01 Aug 2025 15:50:51 GMT

Current Revision posted to Appian Knowledge Base by pauline.delacruz on 8/1/2025 3:50:51 PM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

The alpha-numeric string in the Appian engine security token, appian.sec (located at <APPIAN_HOME>/conf), is being read as having 257 characters instead of 256 characters. This can happen when the appian.sec file is opened, even when the string contained in the file is not altered.

Action

Complete one of the following steps to resolve this issue:

Generate a new Custom Security Token using the Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Note: for High Availability and Distributed Installations, the appian.sec file must be exactly the same across each server to enable authorized connections between the engines and specified application servers.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: July 2025

Tags: engines, infrastructure, service manager

KB-1577 "Expected 256, was 257" exception regarding Appian engine security token prevents engine startup

Parmida Borhani — Mon, 23 Jul 2018 03:17:38 GMT

Revision 10 posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:17:38 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

The alpha-numeric string in the Appian engine security token, appian.sec (located at <APPIAN_HOME>/ear/suite.ear/conf), is being read as having 257 characters instead of 256 characters. This can happen when the appian.sec file is opened, even when the string contained in the file is not altered.

Action

Complete one of the following steps to resolve this issue:

Generate a new Custom Security Token using the Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, infrastructure, service manager

KB-1577 "Expected 256, was 257" exception regarding Appian engine security token prevents engine startup

Parmida Borhani — Tue, 08 May 2018 05:35:01 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 5/8/2018 5:35:01 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

Complete one of the following steps to resolve this issue:

Generate a new Custom Security Token using the Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX "Expected 256, was 257" exception regarding Appian engine security token prevents engine startup

Jordan Horwat — Fri, 04 May 2018 09:11:08 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 5/4/2018 9:11:08 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

Complete one of the following steps to resolve this issue:

Generate a new Custom Security Token using the Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX

Jordan Horwat — Thu, 03 May 2018 14:27:23 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 2:27:23 PM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

The alpha-numeric string in the Appian Engine Security Token, appian.sec (located at <APPIAN_HOME>/ear/suite.ear/conf), is being read as having 257 characters instead of 256 characters. This can happen when the appian.sec file is opened, even when the string contained in the file is not altered.

Action

DRAFT KB-XXXX "Expected 256, was 257" exception regarding Appian Engine Security Token prevents engine startup

Jordan Horwat — Thu, 03 May 2018 11:08:02 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 11:08:02 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

Complete one of the following steps to resolve this issue:

Generate a new Custom Security Token using the following Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX "Expected 256, was 257" exception regarding Appian Engine Security Token prevents engine startup

Jordan Horwat — Thu, 03 May 2018 11:05:05 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 11:05:05 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

One of the following steps can be taken to resolve the issue:

Generate a new Custom Security Token using the following Appian documentation and replace the existing appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX "Expected 256, was 257" exception regarding Appian Engine Security Token prevents engine startup

Jordan Horwat — Thu, 03 May 2018 11:01:22 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 11:01:22 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

One of the following steps can be taken to resolve the issue:

Generate a new Custom Security Token using the following Appian documentation. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX "Expected 256, was 257" exception regarding the Appian Engine Security Token causes Appian engine startup to fail

Jordan Horwat — Thu, 03 May 2018 10:54:58 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 10:54:58 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

One of the following steps can be taken to resolve the issue:

Generate a new Custom Security Token using the following Appian documentation. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX

Jordan Horwat — Thu, 03 May 2018 10:47:10 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 10:47:10 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

One of the following steps can be taken to resolve the issue:

Generate a new Custom Security Token using the following Appian documentation. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager

DRAFT KB-XXXX

Jordan Horwat — Thu, 03 May 2018 10:46:41 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 5/3/2018 10:46:41 AM

Symptoms

Appian engines fail to reach RUNNING state, PRIMARY mode, and the following exception is printed in the service_manager.log file (located at <APPIAN_HOME>/logs):

java.lang.IllegalArgumentException: byte array given isn't the right length. Expected 256, was 257.
 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:146) ~[guava-19.0.jar:?]
 at com.appian.komodo.gateway.model.SecurityToken.fromInputStream(SecurityToken.java:49) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule.provideSecurityToken(ConfigurationModule.java:212) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:31) ~[core-1.83.0.jar:1.83.0]
 at com.appian.komodo.config.ConfigurationModule_ProvideSecurityTokenFactory.get(ConfigurationModule_ProvideSecurityTokenFactory.java:10) ~[core-1.83.0.jar:1.83.0]

Cause

Action

One of the following steps can be taken to resolve the issue:

Generate a new Custom Security Token using the following Appian documentation. Upon saving the file, ensure that the file contains exactly 256 characters.
Delete the last character of the alpha-numeric string contained in the current appian.sec file. Upon saving the file, ensure that the file contains exactly 256 characters.

Note: for High Availability and Distributed Installations, ensure that these changes are reflected across each server. The appian.sec file must be exactly the same across each server to enable authorized connections between the engines and specified application servers.

Affected Versions

This article applies to Appian 17.3 and later.

Last Reviewed: May 2018

Tags: engines, service manager