This site has been archived. To learn more about our current products Ibexa Content, Ibexa Experience, Ibexa Commerce head over to the Ibexa Developer Portal

eZ Community » Forums » Developer » Fatal error: A database transaction...

Fatal error: A database transaction in eZ Publish failed.

Fatal error: A database transaction in eZ Publish failed.

Thursday 27 September 2012 1:44:52 pm - 6 replies

I get the folllowing error when running a importer

Fatal error: A database transaction in eZ Publish failed.The current execution was stopped to prevent further problems.You should contact the System Administrator of this site.The current transaction ID is TRANSID-e192633bf9007a18b9721201998c785a and has been logged.Please include the transaction ID and the name of the current script when contacting the system administrator.

Thanks for any help in advance.

Thursday 27 September 2012 4:01:35 pm

Go check the php / mysql error logs and coem back with the offending query

Thursday 27 September 2012 4:04:27 pm

(Looks like two of us were replying at the same time happy.gif Emoticon

In a nutshell, the message means that something about an SQL query failed.  This could be for various reasons like a table was locked or even in some cases, some part of an extension ot custom query or extended attribute filter just formed a bad SQL statement. 

The solution would be to grep for the transaction ID in your ezpublish log files (var/log/error.log) to find the actual error message that will help identify the underlying problem.  The actual ID above is just a unique hash and its only use is in assisting you in searching your log files.

Here is an earlier posts that started with someone having a similiar issue. I include them because the answers given are generic enough to be relevant to you as well:

and another:




Modified on Thursday 27 September 2012 4:05:26 pm by David Ennis

Thursday 27 September 2012 4:39:19 pm

95% of the time, fatal error due to SQL transaction occur in eZ Publish because of

  • an issue related to duplicate keys
  • a missing table : the one I face very often is when eZFind tables have not been created

As Gaetano said, check your logs, the answer should be there

Modified on Thursday 27 September 2012 4:39:41 pm by Arnaud Lafon

Thursday 27 September 2012 9:44:43 pm

I'm workmate from Shoaib and the most strange is that we don't have errors in the ezpublish logs althought we have active the debug parameters in EzPublish configuration.

The version of EzPublish is 4.3

These parameters are active.




We haven't no error in the logs of mysql. I look for the messages with TRANS ID but i can't find it in mysql logs.

Thanks in advance,


Modified on Thursday 27 September 2012 9:48:44 pm by RAUL GARCIA

Monday 01 October 2012 12:50:28 pm

The importer works now surprisingly and we do not know what the problem is. We assume that the transaction has a timeout and sometimes during the process it exceeds the allocated time and throws exception.

Tuesday 02 October 2012 3:38:57 am

Transactions ussually have no timeouts, but sometimes the mysql server is set up with a timeout on the connection: if there is no query being sent from client to server for a while, connection is dropped. This would iirc only happen while a query is not being executed, but it might still happen that there is a long lag between 2 queries in a ransaction, if the client-side does a lot of other stuff.


You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from