We're aware of an issue with the client area throwing a database error and our developers are working on this.
This is now resolved.