Unusual error: No row with the given identifier exists

Description:

You are getting an ObjectNotFoundException from Hibernate with the message subject of:

No row with the given identifier exists

This error occurs only when you click the "View List" quick link under "Reports" on the default home page.

A workaround is to navigate to View > Repository in orders to select the desired report to run.

2017-07-11 14:32:14,705 ERROR ErrorPageHandlerAction,[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)':118 - Error UID a3c8f9a0-333a-4a39-9f2b-5e530b1bc7e6
org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.jaspersoft.jasperserver.api.metadata.user.domain.impl.hibernate.RepoUser#5961]
at org.hibernate.impl.SessionFactoryImpl$2.handleEntityNotFound(SessionFactoryImpl.java:419)
at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:154)
at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:143)
at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:174)
at org.hibernate.proxy.pojo.javassist.JavassistLazyInitializer.invoke(JavassistLazyInitializer.java:190)
at com.jaspersoft.jasperserver.api.metadata.user.domain.impl.hibernate.RepoUser_$$_javassist_19.toClient(RepoUser_$$_javassist_19.java)

Resolution:

Most likely, there were changes made to the repository and this is a side effect.  In fact, in this particular case, the developer had deleted some rows in the database manually. 

We highly recommend using only the officially supported APIs to make any changes to the repository.  These APIs are certified and maximize compatibility of customization between versions.  You can also use the export/import functions to make changes more safely. 

Direct repository DB modification is highly risky and should not be used unless it is a critical recovery issue with clear and specific understanding of the change involved. 

You should always keep a DB backup before making any changes for easy recovery.

In this particular case, the rows were removed from this table.  System ran fine after restoring the deleted rows.

SELECT * FROM JASPERSERVER.JIUSER AS OF TIMESTAMP TO_TIMESTAMP('01-JUL-2017 12:30:00', 'DD-MON-YYYY HH:MI:SS')