Error: 56050 Table does not exist while searchign for documents

RE: Error: 56050 Table does not exist while searchign for documents

Andrew Bila — Fri, 13 Jul 2018 17:27:19 GMT

I received Error: 56050 while trying to update an environment attribute. The cause was another attribute that was trying to update via an incorrect select statement (yes, my own fault). The select statement was trying to select from a column that didnt exist in the environment table. It seems obvious now but it took a few hours to diagnose.

It sounds like you are probably searching for an attribute that doesnt exist in the environment being searched which is why there wasnt a corresponding column name in the table. I would hope for your sake it is a flaw in the search parameters rather than a corrupted environment table but I could see how either one could cause this error.

RE: Error: 56050 Table does not exist while searchign for documents

canada18 — Sun, 31 May 2015 06:15:46 GMT

Thanks Peter for the response. I have found the table DMS_DOC and its view (V_DMS_DOC) where O_version is a required field but in the table it has empty records . Could this be problem? can you suggest what exactly to look for in the views

RE: Error: 56050 Table does not exist while searchign for documents

Peter Willmen — Sat, 30 May 2015 08:48:10 GMT

Have you checked you views?. I have seen this error if the view is looking for an attribute field that does not exist in the environment for some of the returned results

RE: Error: 56050 Table does not exist while searchign for documents

canada18 — Fri, 29 May 2015 22:08:57 GMT

how do we rebuild the environment? Do you mean rebuild a new environment in PW administrator?

RE: Error: 56050 Table does not exist while searchign for documents

canada18 — Wed, 27 May 2015 04:52:49 GMT

I do not have o_docguid column in my environment table, does this table exist in all the databases?

RE: Error: 56050 Table does not exist while searchign for documents

Jimmy Lau — Wed, 11 Feb 2015 01:40:49 GMT

Hi

I have 1 user who has similar problem. They found that their PW Environment table is corrupted. 2 columns: o_docguid and o_projectno are missing or empty. So, they rebuild the environment for all documents. The problem is resolved.

Hope it helps.