Server Error: Unable to register cleanup Synchronization with TransactionManager

As per log it's saying handled not specific exception under SQL exception. That might be causing disturbing the ACID properties. Have look at the configuration given in the link as and where required.forum.appian.com/.../Configuring_Relational_Databases.html

What is the output of <APPIAN_HOME>/server/_scripts/diagnostic/checkengine<sh|bat>?

From the log, it looks like there is an issue retrieving data from the Design Engine, rather then the database. After you restarted the server, did you also restart the Appian Engines?

@Sally Mason,

Engines are working fine i.e All engines are in OKAY status. After restarted Server was running with no issues.
Since the issue is happening several times, I just want to analyze the root cause.
The business data source has been configured through Admin console instead of .xml configuration. I suspecting that, this is the root cause.
Kindly add your suggestions.

In the log provided, there is a write error:
n error occurred while trying to write to the entity “COB_Client_Plan” [id=45c4551d-7dc6-4a71-aca4-432fc61eca8f@8720, type=COB_Client_Plans (id=3042)]

The incorrect encoding "“" & "”" is seen on the name of the entity. This issue occurs when multiple different language sets or encoding is used, so I would check the encoding of the table and database in question, and update the broken characters to let the query execute.

Ref:
www.i18nqa.com/.../utf8-debug.html
dev.mysql.com/.../charset-conversion.html

Let us know if this resolves your issue?

On further research, it appears that this is a bug that has already been reported.

Thanks Sally.
Do we have fix available or any workaround for this?

The workaround is to move the data source to the -ds.xml and remove from the Admin Console.

I have moved the data source configuration to .xml ...Now the server is running with no issues.

@eduardo: We are facing the same issue. Does any fix is available for this issue?