Major Database Error

[T.J]

Hi all,

Running Catalog 6 and was well and good untill i moved one section in to another..... Got an error message stating "unable to re-order sections: Catalog Section.sSectionTemplate can not be a zero value" exited the catalog and was not prompted to do a backup. Re-running catlog brought the the same error as before and the whole product and section tree was empty.

Managed to get the catalog running again by copying the "catalog section" table from an older backup of the database, catalog dedtected the orphan products and moved them in to a new section.

The problem is i can create, move and delete products as normal but doing anythng except rename and create sections brings up the above error and crashes the catalog.

Any ideas on solving this would be more than welcome as its causing major headaches at this end :-(

Many Thanks
Liam

[cdicken]

Hi Liam

Could you let me know a couple of things please

1) What operating system are you using?
2) What version of Actinic are you using?
3) Do you get the same error when you use cut/paste rather than drag/drop?

Also, try doing a 'Housekeeping | Compact Database' to see if that helps out.

[T.J]

We're running catalog 6.1.2 on Windows 2000 SP4, did try the compact database option but this didn't work. To be honest not tried cut 'n' paste but having said this managed to fix the error anyway - probably more by chance than anything else i had a back up from a few weeks ago and copied the "catalog section" table from this in to the damaged database. It created tons of orphened products but was able to move these in to correct sections and so far everything is working well again. Thanks for all your help!

Many Thanks
Liam

[T.J]

Hi all,

Its back :-( Everthing was working fine and then all of a sudden tried creating a new top level section and the error appeared again. Have been able to create new top level sections since the last time this happened so it seems to be a random thing. Once again i've got the catalog running by copying an old table over the damaged one although i still can't create top level sections without the error occuring.

Tried compacting the database but this hasn't worked.... Any ideas would be more than welcome

Many Thanks
Liam



****UPDATE****

Its fixed!!! A big thank you to Jan for providing the soloution, you've saved me tons of time, hassles and grey hairs :-)