ok -- Looking through the table, I could see some old searches which had a different string the in the config field. Those rows have been deleted. The tickets are still there, let's see if the errors still get generated.

Had to roll back queues got messed up. Rows with ID 1 & 21 seem to be the ones to cause the issues, but I would need advice on how to adjust the remaining rows.

This is original table

A log of what I am trying:
1. Removing my old custom searches via the gui seems to have helped.
2. I renamed one of the "Open" rows to see what is going on in the drop down
- the table now looks like this:

alexmetcalfe The solution provided works .. because for it also deletes ALL my tickets!

Um. there is no way that deleting all your custom searches deletes your tickets. They are two completely different tables. Deleting all the queues (including system defaults) would cause you to not be able to see them though... but then that would mean that you deleted all the queues no just your custom ones.

From your first screen shot it looks like:
15, and id=17 and higher are your custom queues.

      ntozier Yeah - I know. That's what threw me. All the queues were gone from the menu bar, and no tickets visible at all.

      Now with the table as it is in the second screengrab, things seem ok.

        Great!

        Should I close this thread then?

        5 days later

        Hi Ntozier,

        Yup. This can be closed.

        Possibly more idiot/Alex proof instructions would be to:
        o Remove the old custom searched via the GUI, not the database.
        o Remove the rows from the ost_queue table where staff_id is something other than "0"

        ntozier changed the title to [resolved] DB Error #1064 - part 2.
        Write a Reply...