KB-1878 Tempo fails to render for a renamed user

Rebecca Jonas — Thu, 28 Feb 2019 16:43:44 GMT

Current Revision posted to Appian Knowledge Base by Rebecca Jonas on 2/28/2019 4:43:44 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_DDMMYY.txt present under <APPIAN_HOME>\_admin\_scripts.

Run the SQL queries present in this file on the primary database to resolve this as described in step 10 of KB-1089.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Thu, 28 Feb 2019 11:33:42 GMT

Revision 10 posted to Appian Knowledge Base by Tejas Kargutkar on 2/28/2019 11:33:42 AM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_DDMMYY.txt present under <APPIAN_HOME>\_admin\_scripts.

Run the SQL queries present in this file on the primary database to resolve this as described in Step 10 of this Knowledge Base article.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Thu, 28 Feb 2019 11:33:29 GMT

Revision 9 posted to Appian Knowledge Base by Tejas Kargutkar on 2/28/2019 11:33:29 AM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_DDMMYY.txt present under <APPIAN_HOME>\_admin\_scripts.

Run the SQL queries present in this file on the primary database to resolve this as described in Step 10 of this Knowledge Base article..

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Mon, 25 Feb 2019 12:11:06 GMT

Revision 8 posted to Appian Knowledge Base by Tejas Kargutkar on 2/25/2019 12:11:06 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_DDMMYY.txt present under <APPIAN_HOME>\_admin\_scripts.

Run the SQL queries present in this file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Mon, 25 Feb 2019 12:10:46 GMT

Revision 7 posted to Appian Knowledge Base by Tejas Kargutkar on 2/25/2019 12:10:46 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_DDMMYY.txt present under <APPIAN_HOME>\_admin\_scripts.

Run the SQL queries present in this file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Rebecca Jonas — Mon, 25 Feb 2019 12:01:15 GMT

Revision 6 posted to Appian Knowledge Base by Rebecca Jonas on 2/25/2019 12:01:15 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_*date*.txt.

Run the SQL queries present in this file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Rebecca Jonas — Mon, 25 Feb 2019 11:21:38 GMT

Revision 5 posted to Appian Knowledge Base by Rebecca Jonas on 2/25/2019 11:21:38 AM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application server log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian. This issue will occur if the SQL queries are not run after renaming the users.

Action

The rename users script will generate the text file renameUsers_postExecution_commands_*date*.txt as a part of the rename users script.

Run the SQL queries present in this file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Fri, 22 Feb 2019 22:07:25 GMT

Revision 1 posted to Appian Knowledge Base by Tejas Kargutkar on 2/22/2019 10:07:25 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application-server.log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.2019-02-19 21:14:06,524 [http-nio-8080-exec-1]

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1]

ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian.

The above issue will happen if the SQL queries are not run after renaming the users.

Action

The rename users script will generate a text file named "renameUsers_postExecution_commands_*date*.txt" as a part of the rename users script.

Run the SQL queries present in the above file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Fri, 22 Feb 2019 17:10:21 GMT

Revision 4 posted to Appian Knowledge Base by Tejas Kargutkar on 2/22/2019 5:10:21 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application-server.log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian.

The above issue will happen if the SQL queries are not run after renaming the users.

Action

The rename users script will generate a text file named "renameUsers_postExecution_commands_*date*.txt" as a part of the rename users script.

Run the SQL queries present in the above file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Fri, 22 Feb 2019 17:08:13 GMT

Revision 3 posted to Appian Knowledge Base by Tejas Kargutkar on 2/22/2019 5:08:13 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application-server.log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.[http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian.

The above issue will happen if the SQL queries are not run after renaming the users.

Action

The rename users script will generate a text file named "renameUsers_postExecution_commands_*date*.txt" as a part of the rename users script.

Run the SQL queries present in the above file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: February 2019

Tags: rename users, database, infrastructure

DRAFT KB-XXXX Tempo fails to render for a renamed user

Tejas Kargutkar — Fri, 22 Feb 2019 17:07:50 GMT

Revision 2 posted to Appian Knowledge Base by Tejas Kargutkar on 2/22/2019 5:07:50 PM

Symptoms

Tempo fails to render for a renamed user with the following error observed in the application-server.log:

ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.2019-02-19 21:14:06,524 [http-nio-8080-exec-1] 
ERROR com.appiancorp.tempo.abdera.TempoEntryAdapter - Error retrieving entries.com.appiancorp.suiteapi.common.exceptions.InvalidUserException: [InvalidUserException] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
ERROR org.hibernate.util.JDBCExceptionReporter - Duplicate entry *username* for key 'usr_username_uc'[http-nio-8080-exec-1] 
ERROR org.hibernate.AssertionFailure - an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session)org.hibernate.AssertionFailure: null id in com.appiancorp.security.user.User entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:82) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:190)

Tempo works as expected for all other users.

Cause

Renaming users involves executing SQL queries on the primary database of Appian.

The above issue will happen if the SQL queries are not run after renaming the users.

Action

The rename users script will generate a text file named "renameUsers_postExecution_commands_*date*.txt" as a part of the rename users script.

Run the SQL queries present in the above file on the primary database to resolve this issue.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: February 2019

Tags: rename users, database, infrastructure