Load Data Using Workspace - Error 160276: A row with this OID already exists

[strmside]

I have successfully created a migration workspace but when I am loading data using "Load Data Using Workspace" tool, it fails at the same spot every time with the error "ERROR: 160276: A row with this OID already exists."  Before this error it has appended hundreds of thousands of features already to multiple feature classes.  I recognize it is skipping some rows due to domain mismatch but that should not cause this failure.  I am using Pro 3.5.1.  I am not using a later version due to the bug with the Apply Error Resolutions tool.  Below is the last details of the error, everything above these lines was successful.  I left one successful message for streetlights before it hits a new feature class, support structures.  It seems to process this data successfully EXCEPT the append at the end.  Features from other source feature classes have already loaded into structurejunction successfully.  The Esri documentation states this error has no known resolution.  Are there different troubleshooting steps I can take to try to resolve?

.....8358 row(s) from C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ElectricFacilityData\Streetlight were appended to C:\LocalArcGISWork\migration_workspace_v3\xxx_AssetPackage.gdb\ElectricDevice

Processing C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ElectricFacilityData\SupportStructure -> C:\LocalArcGISWork\migration_workspace_v3\xxx_AssetPackage.gdb\StructureJunction

WARNING 001156: Failed on input OID 1, could not write value 'Y' to output field GROUNDED

WARNING 001156: Failed on input OID 2, could not write value 'Y' to output field GROUNDED

WARNING 001156: Failed on input OID 3, could not write value 'N' to output field GROUNDED

WARNING 001156: Failed on input OID 4, could not write value 'N' to output field GROUNDED

WARNING 001156: Failed on input OID 5, could not write value 'N' to output field GROUNDED

WARNING 001156: Failed on input OID 6, could not write value 'N' to output field GROUNDED

WARNING 001156: Failed on input OID 7, could not write value 'N' to output field GROUNDED

WARNING 001156: Failed on input OID 8, could not write value 'Y' to output field GROUNDED

WARNING 001156: Failed on input OID 9, could not write value 'Y' to output field GROUNDED

WARNING 001156: Failed on input OID 10, could not write value 'Y' to output field GROUNDED

WARNING 003819: Exported 21,164 rows that were skipped to \\ceanet1\profiles$\ashleys\Documents\ArcGIS\Projects\MyProject_new_351\scratch.gdb\fc_b76aaff9613b4...

ERROR 160276: A row with this OID already exists.

Failed to execute (Append).

Failed script Load Data Using Workspace...

Failed to execute (LoadDataUsingWorkspace).

Failed at Monday, January 26, 2026 10:10:06 AM (Elapsed Time: 18 minutes 3 seconds)

[gis_KIWI4]

@strmside - I have never seen this one before.
Are you mapping OIDs in your workspace?

[strmside]

No, the error is a red herring.

[TedHoward2 · Accepted solution]

I would ignore ERROR 160276 for now. I think that's a post processing issue, ie. warnings have occurred while loading and now DLT needs to handle exporting rows. 160276 may be an error occurring with that.

Instead look at the 001156 warning, which tells me the GROUNDED field cannot accept the data you are trying to load. For example, text values cannot be added to numeric fields, and text values cannot be added to text fields if the values are longer than the field length. I would assume it's the former since you are trying to load single characters to the field.

[strmside]

It knows to skip those rows, and produces an output of rows skipped. I do not think this is the problem.  Previous feature classes processed just fine with some attribute errors, again, rows that were skipped are outputted as errors.  

[TedHoward2]

Hmm interesting that previous loads with warnings did not produce the error. It would be good if you could submit a ticket so we can have a reproducible case.

[strmside]

Ok, thank you.  Just wanted to point out that the run had 7 previous issues just like the one I posted, but was able to append rows and/or skip rows and keep moving.  Here is an excerpt from a couple of those that kept the tool moving instead of failing altogether.

Processing C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ConductorInfo -> C:\LocalArcGISWork\migration_workspace\xxx_AssetPackage.gdb\ElectricEdgeObject

WARNING 001156: Failed on input OID 1, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 2, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 3, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 4, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 5, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 6, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 7, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 8, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 9, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 10, could not write value 'ACSR' to output field CONDUCTORMATERIAL

WARNING 003819: Exported 30,978 rows that were skipped to \\ceanet1\profiles$\ashleys\Documents\ArcGIS\Projects\MyProject_new_351\scratch.gdb\fc_aa5d3db8c4084...

30978 row(s) from C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ConductorInfo were appended to C:\LocalArcGISWork\migration_workspace\Chugach_Electric_AssetPackage.gdb\ElectricEdgeObject

Processing C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ConductorInfo -> C:\LocalArcGISWork\migration_workspace\Chugach_Electric_AssetPackage.gdb\ElectricEdgeObject

WARNING 001156: Failed on input OID 1, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 2, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 3, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 4, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 5, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 6, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 7, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 8, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 9, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 001156: Failed on input OID 10, could not write value 'AL' to output field CONDUCTORMATERIAL

WARNING 003819: Exported 75,354 rows that were skipped to \\ceanet1\profiles$\ashleys\Documents\ArcGIS\Projects\MyProject_new_351\scratch.gdb\fc_8c34d2f7fa874...

75354 row(s) from C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ConductorInfo were appended to C:\LocalArcGISWork\migration_workspace\Chugach_Electric_AssetPackage.gdb\ElectricEdgeObject

Processing C:\LocalArcGISWork\elec_fac_data_for_sql.gdb\ConductorInfo -> C:\LocalArcGISWork\migration_workspace\Chugach_Electric_AssetPackage.gdb\ElectricEdgeObject

[strmside]

@RobertKrisher I was wondering if you have seen this, does it relate to Pro version or should I be submitting a ticket via my client?

[RobertKrisher]

@TedHoward2 can you comment on the question from @strmside ?

[TedHoward2]

I do not think a newer version of Pro would make a difference.