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

v2.11.2 Validate Database error #69

Closed
LLeBlanc110 opened this issue Aug 28, 2023 · 2 comments
Closed

v2.11.2 Validate Database error #69

LLeBlanc110 opened this issue Aug 28, 2023 · 2 comments

Comments

@LLeBlanc110
Copy link

Ran the tool with "Compact GDB" and everything else unchecked and received the following error -

image

in text -

Validate Database

Parameters

Input geodatabase or geopackage C:\Users\EBollen\Documents\ArcGIS\Projects\FlagMountain\FlagMountain_EMRI21.gdb
Output workspace C:\Users\EBollen\Documents\ArcGIS\Projects\FlagMountain\Validation
Validate standalone file
Validate embedded metadata
Report errors with _ID, not OBJECTID false
Skip topology checks false
Refresh GeoMaterialDict false
Delete unused Glossary and DataSources rows false
Compact GDB false
Open report when done true

Messages

Start Time: Monday, August 28, 2023 1:51:43 PM
This version of the tool is up to date
Metadata not checked. File needs to be in XML format.
Traceback (most recent call last):
File "C:\Users\EBollen\Documents\ArcGIS\gems-tools-pro-2.11.2\Scripts\GeMS_ValidateDatabase.py", line 1549, in
rule2_1_results = rule2_1(db_dict, is_gpkg)
File "C:\Users\EBollen\Documents\ArcGIS\gems-tools-pro-2.11.2\Scripts\GeMS_ValidateDatabase.py", line 1204, in main
database dictionary. If blank, it is an extension"""
AttributeError: module 'GeMS_utilityFunctions' has no attribute 'eval_bool'

Failed script Validate Database...
Failed to execute (ValidateDatabase).
Failed at Monday, August 28, 2023 1:51:45 PM (Elapsed Time: 1.70 seconds)

@ethoms-usgs
Copy link
Collaborator

I have seen this error a couple times now with the new version of the tool which includes some edits to GeMS_utilityFunctions. It's like the new file is not getting found by Pro; it goes looking for the older version. Try closing Pro and either deleting the older toolbox folder or, when you download v 2.11.2, put it in a different folder and try to access the tool there. And, in Pro, access the tool from the Catalog pane, not by going to geoprocessing history and running a saved entry. I don't know for sure that's important, but it should guarantee that Pro is not running any cached files.

@LLeBlanc110
Copy link
Author

That fixed it, thanks!

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