XY Table To Point - RuntimeError: Object: Error in getting OverwriteOutputOptions

[RyanBohan]

I am running into the strangest error message using the XY Table to Point GP tool.  I am on version 3.5.5

• Traceback (most recent call last):
  File "c:\program files\arcgis\pro\Resources\ArcToolbox\scripts\XYTableToPoint.py", line 297, in <module>
  
  ^
  File "c:\program files\arcgis\pro\Resources\ArcToolbox\scripts\XYTableToPoint.py", line 70, in xy_table_to_points
  
  File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 587, in overwriteOutputOptions
  return self._gp.OverwriteOutputOptions
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  RuntimeError: Object: Error in getting OverwriteOutputOptions

It appears to be happening both on CVS files as well as a Esri Table saved to the GDB. I have tried different tables, and all give the same error.

Any tips or tricks would be greatly appreciated

[ChrisUnderwood]

Hello @RyanBohan , the error message does mention the Overwrite option. What is yours set to ?

[RyanBohan]

Hi Chris, great thought, it’s embedded. I’ve also tried disabling and re-enabling it.

[RyanBohan]

It appears you can also do a two step process.  

• Make XY Event Layer (temp layer, not saved anywhere)
• Export Feature.

[JoshMakesMaps]

Ran into this exact error. The issue is that Pro is failing to parse C:\Program Files\ArcGIS\Pro\Pro.settingsConfig.

In my case the file had been deployed as MSI-style KEY=VALUE plain text instead of XML:

ALLUSERS=1
CHECKFORUPDATESATSTARTUP=0 
LOCK_AUTH_SETTINGS=True 
ADMIN_SETTINGS_PATH="C:\Program Files\ArcGIS\Pro\" 
ArcGIS_Connection=True
...

Pro tries to parse that as XML at runtime, the parser aborts on the first character, and every downstream call that reads OverwriteOutputOptions (which is most GP tools) throws the RuntimeError you're seeing.

Worth checking yours. Open Pro.settingsConfig in a text editor and if it doesn't start with <?xml or an XML root element, that's the problem. Rewriting it as valid XML with the same settings preserved fixed it for me, and XYTableToPoint ran cleanly right after.

<?xml version="1.0" encoding="utf-8"?>
<Settings>
  <CheckForUpdatesAtStartup>False</CheckForUpdatesAtStartup>
  <LockAuthSettings>True</LockAuthSettings>
  <ArcGISConnection>True</ArcGISConnection>
...
</Settings>

If your deployment was pushed by IT, it would likely require admin level privs to adjust the file and push to all users.