This question may be related to a resolved thread.
I am working on a client site that was upgraded to 2.3.1 before I was brought on to work on it from what I assume was 1.x. We are making further design and modifications, so I migrated the site to our dev servers and received this same error. I have migrated all site files and the db twice. I am still getting the above error that I have never seen before and have not been able to resolve. The site is running fine on the live servers.
I am wondering if there could be some db issues leftover from the upgrade that could be causing the error. I ask because I am experiencing the same issue as the user in the previous thread. Any ideas?