GEMS errors in current ArcPro version

[JMSFRMN]

I hadn't used the GEMS toolbox since last October and in Desktop not Pro. Ran just fine. I have a new project and have to use the tools in Pro and I am getting odd results. Using the Build Polygons tool and sometimes it will run and say it has run successfully but no polygons are created. Other times it runs and errors out with messages about bad syntax, or s licensing issues. I have never seen these pop up before.

And to make it even more confounding sometimes the MakePolygons too runs, errors out, and then does actually create the polygons.

Anyone else having issues?

[JMSFRMN]

These are the errors that showed up when I ran it just now.

Make Polygons

Tool Path

P:\COGS\20250507-65568-C250766\GEMS_toolbox\gems-tools-pro-master\GeMS_Tools.tbx\MakePolys

Parameters

Input feature dataset P:\COGS\20250507-65568-C250766\From_Tao\TEMP\USGS_GQ-797_GEMS.gdb\GeologicMap
Save old MapUnitPolys true
Label points feature class P:\COGS\20250507-65568-C250766\From_Tao\TEMP\USGS_GQ-797_GEMS.gdb\GeologicMap\MapUnitPoints
Simple mode (no error reporting) false

Messages

Start Time: Monday, June 9, 2025 11:28:16 AM
This version of the tool is up to date: GeMS_MakePolys3.py, version of 24 June 2022
GeMS_MakePolys3.py, version of 24 June 2022
Saving MapUnitPolys
Selecting all non-concealed lines
Continuing in reporting mode
Organizing label points
Emptying MapUnitPolys
Adding features from memory to P:\COGS\20250507-65568-C250766\From_Tao\TEMP\USGS_GQ-797_GEMS.gdb\GeologicMap\MapUnitPolys
Looking for errors and changes
Preparing report layers
Traceback (most recent call last):
 File "P:\COGS\20250507-65568-C250766\GEMS_toolbox\gems-tools-pro-master\Scripts\GeMS_MakePolys3.py", line 261, in
 
 File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\utils.py", line 186, in fn_
 return fn(*args, **kw)
 ^^^^^^^^^^^^^^^
 File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy_mp.py", line 4665, in addDataFromPath
 return convertArcObjectToPythonObject(self._arc_object.addDataFromPath(*gp_fixargs((data_path, web_service_type, custom_parameters,), True)))
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: Failed to add data. Possible credentials issue.

Failed script Make Polygons...
Failed to execute (MakePolys).
Failed at Monday, June 9, 2025 11:28:54 AM (Elapsed Time: 37.85 seconds)

[wynaut]

Hi there! This tool can be a little finnicky in my experience. Are you able to send a copy of the geodatabase you're working on to debruhld@dnr.sc.gov? I'd like to see if I can replicate your issue.
If your work is super time-sensitive, the standard ArcGIS tool Feature to Polygon can work in a pinch, as long as the topology is good to go in your ContactsAndFaults feature class.

[JMSFRMN]

Hi Darby Thanks for the response. I’ve used these tools for years now and never have seen these errors. We tested it across 3 machines, a couple versions of ArcPro. Desktop ArcMap too. Can I send you a Wetransfer with the geodatabase? James Freeman, Principal DIGITAL<https://www.digitaldataservices.com/> DATA SERVICES, INC. (o) 303.986.6740 | (d) 720.668.8043 From: Darby DeBruhl ***@***.***> Sent: Monday, June 9, 2025 2:27 PM To: DOI-USGS/gems-tools-pro ***@***.***> Cc: James Freeman ***@***.***>; Author ***@***.***> Subject: Re: [DOI-USGS/gems-tools-pro] GEMS errors in current ArcPro version (Discussion #129) Hi there! This tool can be a little finnicky in my experience. Are you able to send a copy of the geodatabase you're working on to ***@***.******@***.***>? I'd like to see if I can replicate your issue. If your work is super time-sensitive, the standard ArcGIS tool Feature to Polygon can work in a pinch, as long as the topology is good to go in your ContactsAndFaults feature class. — Reply to this email directly, view it on GitHub<#129 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BTMRWPKGU7Q4W7635GLB4UD3CXUY3AVCNFSM6AAAAAB65O5WMWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNBRGM2TINI>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[wynaut]

Just wrote you back. :)
You describe a bunch of different errors - just to be clear, are you getting all of these after running the tool multiple times on one geodatabase? Or are you making different attempts on different geodatabases, and getting a different error each time?