UNIQUE constraint on index 's01_ManagedTemplates_2' Fatal Error

[wcw]

Getting this error. Can someone from Miva shed some light on what this means? I think 2.mvx of ManagedTemplates is a new index with 5.5.

Runtime error in /mm5/5.00/features/tui/tui_db.mvc @ [00000038:0000004c]: features/tui/tui_db.mv: Line 1477: MvQUERY: Inserted record violates UNIQUE constraint on index 's01_ManagedTemplates_2' Fatal Error

Miva Merchant has encountered a fatal error and is unable to continue. The following information may assist you in determining the cause of the error:

Error Code: MER-TUI-DTB-00055
Description: Inserted record violates UNIQUE constraint on index 's01_ManagedTemplates_2'
Other Information:

[Alex Kruglyak]

Re: UNIQUE constraint on index 's01_ManagedTemplates_2' Fatal Error

There were no new indexes added to the Template UI in 5.5.

This error typically means that you're trying to add a record that's already been defined in the index.

Best way to fix this is to pack the table(s) with this issue.

[wcw]

Re: UNIQUE constraint on index 's01_ManagedTemplates_2' Fatal Error

Well, here is something odd. In my beta 5.5 store there is a 2.mvx for managedtemplates in a mivasql setup. However, when I go to my 2 year old store which has been upgraded to 5.5 and also uses mivasql, there is NO 2.mvx for that database. How can that be?

In the store that has a 2.mvx it appears this is on the upper(filename). Neither of these stores have the error I described above. The store owner says they have tried naming the template several different names and still get the error. It sounds like they have the error from a previous page creation. But I have no idea how to tell what the duplicate is so one can be deleted.

[sebenza]

Re: UNIQUE constraint on index 's01_ManagedTemplates_2' Fatal Error

Did anyone figure out the solution to this?