Transaction problems after switching server

Monday 27 February 2006 11:43:28 am

Hi!

I've reinstalled an eZ site on a new server, by doing the following:

- installing a new plain eZ installastion and adding my sitestyle
- dumped the db from the old server and imported it again on the new server

Frontend works perfectly, but when I log into admin and try creating content, I receive the following error:

<b>
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 with the information on this page.
The current transaction ID is TRANSID-dc80a3e389cfc9b9c4db182fa79d1495 and has been logged.
Please include the transaction ID and the current URL when contacting the system administrator.
</b>

Turning on debug gives me this:

<b>Notice: eZMySQLDB::query(1 rows, 0.708 ms) query number per page:15 Feb 27 2006 19:36:54

INSERT INTO ezcontentobject_attribute (contentobject_id, version, language_code, contentclassattribute_id, attribute_original_id, sort_key_int, sort_key_string, data_type_string, data_text, data_int, data_float) VALUES('0', '1', 'nor-NO', '1', '0', '0', 'new article', 'ezstring', 'New article', NULL, '0.000000')

Notice: eZMySQLDB::query(-1 rows, 0.459 ms) query number per page:16 Feb 27 2006 19:36:54

INSERT INTO ezcontentobject_attribute (contentobject_id, version, language_code, contentclassattribute_id, attribute_original_id, sort_key_int, sort_key_string, data_type_string, data_text, data_int, data_float) VALUES('0', '1', 'nor-NO', '152', '0', '0', '', 'ezstring', '', NULL, '0.000000')

Error: eZMySQLDB Feb 27 2006 19:36:54

Query error: Duplicate entry '0-1' for key 1. Query: INSERT INTO ezcontentobject_attribute (contentobject_id, version, language_code, contentclassattribute_id, attribute_original_id, sort_key_int, sort_key_string, data_type_string, data_text, data_int, data_float) VALUES('0', '1', 'nor-NO', '152', '0', '0', '', 'ezstring', '', NULL, '0.000000')
</b>

I'm not sure how I can resolve this, any ideas?

Tuesday 28 February 2006 10:53:53 am

Thanks :)

I guess that's it, unfortunately I don't have permissions to alter tables, but I'll try emailing my ISP.

One thing tough, I don't really understand how this has happended?

I used mysqldump --lock-tables --opt --compatible=mysql40 when creating the dump. And I have done that before with success.