We don't know how this error occurs. It is not specific to WorklogPRO and can happen to any add-on as discussed here. Solving this error requires you to run DDL statements in your database. What you need to do is: