1. Connection string may not be correct. You should test before saving the project. You can do it now.

2. Check the permissions

3. Index error logs should be checked. You can examine the errors received in the scan with the developer report via GEODI.

4. DBmetas may not be correct

5. Jsettings files should be syntax validated, you can use https://jsonformatter.curiousconcept.com/ site for this validation.

6. Check the correctness of the column, table and GEODI project names and their names on the Table/Column/Project database.

Every reindex After the initial index, each subsequent indexing (scheduled or manually) after the first index may generate version for tables w/o manual) can create versions for tables without a primary key. This does not affect the discovery results , or reports bu but only impacts the GEODI Index index size.

GEODI indexing generates logs errors for such tables in the error logs. Please check . Check the error log to see wihih which tables are affected.

GEODI, by By default, GEODI requires a primary key (PK) column to exist. So unless you set otherwise this be present. This situation does not occur . You may also unless otherwise specified. Additionally, you can choose to put add a PK to your tables (a best practice). A For GEODI, a PK column for GEODI is a column with is one that has a unique value in each row.

If your table has a PK but you are still get the errorencountering errors, then the primary key column name should must be registered to recorded in GEODI by defining a DB meta.