Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate database error #74

Open
hsnellen opened this issue Aug 5, 2021 · 5 comments
Open

Validate database error #74

hsnellen opened this issue Aug 5, 2021 · 5 comments

Comments

@hsnellen
Copy link

hsnellen commented Aug 5, 2021

I'm using the "Validate Database" tool and when I run my database through it, I receive this error:
image

My database does contain the table "GeologicEvents" so I wasn't able to make sense of the error.
Any thoughts?

@ethoms-usgs
Copy link
Collaborator

Can you send the gdb? And in the meantime, have you run the tool from ArcCatalog?

@hsnellen
Copy link
Author

CunninghamMtn.gdb.zip

Yeah I tried this in both ArcMap and Pro.

@ethoms-usgs
Copy link
Collaborator

Unfortunately, I couldn't reproduce the error. The tool ran correctly (once I added a GeoMaterialDict table - see Issue 73) so I don't know what it is going on.

Could you open the script file in a text editor and change line 38 to debug = True and run the tool again? That will print out more messages which might indicate something.

There are a number of empty tables and one called SysInfo, which I have never seen. If you won't be filling them out, I would delete them.

@hsnellen
Copy link
Author

Apologies for the late response, I ended up getting the database that I posted above to start working with the tool. However I've encountered this same error with another database.
So I deleted all tables that don't have any data, and then received an error exactly as the one listed above, but instead of saying "GeologicEvents" doesn't exist, it says "StandardLithology".
I went into the script and changed line 38 as you suggested but no dice.
I'll attach the database I'm currently experiencing this issue with and hopefully you can re-create the error.
Salome_GeMS.gdb.zip

@ethoms-usgs
Copy link
Collaborator

Darn. Again, no error.
With the debug flag set to True, could you send all of the messages that get printed? Open the Geoprocessing > Results pane, right-click on Messages from a run of the tool that failed, pick Copy, and paste the contents here.

image

Or, I think the workaround at this point would be to delete StandardLithology since it is empty and you aren't using it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants