that is a database error. tough to tell where it is coming from though.
I have created a support ticket so we can look into this issue further.
To view and edit your support ticket, please log into your support history:
If anyone else is experiencing this same issue, please append to this thread.