KB-1878 Tempo fails to render for a renamed user


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.


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. 


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