Unable to register cleanup Synchronization with TransactionManager

Are these reports custom reports or were they created with Quick Apps?

As the error suggests, the issue is occurring while querying the data. Ensure that the database is up and reachable from your environment, and that your datasource is able to be verified successfully. You may also check that queries to the database from other rules/applications are able to complete successfully.

If there are no issues with database connectivity, then try adding the following line to the file at <Appian Home>/ear/suite.ear/resources/appian_log4j.properties:

log4j.logger.org.hibernate.util.JDBCExceptionReporter=DEBUG

then reproduce the error and see if there is any additional detail.

It looks like Query Entity is not able to get the data from database ,
Check your relational database is up or not.
please find below link it may helpful.
forum.appian.com/.../Configuring_Relational_Databases.html

@omkark, Please refer the below link
forum.appian.com/.../e-138449 for the same issue

Thanks for you responses. There was a problem in the JBOSS server. Restarting the server solved the issue. @Sally: The reports are custom reports (SAIL interface).

Hi Sally, I received this error again and we are not able to understand the root cause. It will great if you can help us in determining the root cause. This issue gets resolved when you restart the server, but, that's not the permanent solution. I have attached new lops with DEBUG=1. Please let me know if you have any questions.

relevant_logs_transaction_manager.txt

What is DEBUG=1? Do you mean you added the logger I mentioned previously?

Can you attach the complete log.

I would like to know how to resolve this issue as well, it was affecting the server quite frequently

Hi Tom, Apologies for the delayed response. Here are the logs attached with respect to error. I don't have the completed logs file for now since this issue is intermittent. Sometimes restarting server has worked. Currently, I am not facing this issue. Once I face this issue again, I will attach the complete logs.

relevant_logs_synchronization_clean_up.txt

Did you see any further details when log4j.logger.org.hibernate.util.JDBCExceptionReporter=DEBUG was enabled? We might also verify that the datasource connection properties in the app server are correct.