topic Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork). in ArcGIS Network Analyst Questions

ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

SOTIRIOSTRIANTOS — Thu, 27 Jul 2023 07:15:04 GMT

i am gettting a random error, when building a network dataset using ArcGIS Pro 3.1.2 and arcpy. The error message is: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork). Failed at Wednesday, July 26, 2023 5:04:01 PM (Elapsed Time: 3.42 seconds)

If i rerun the process it doesnt occur.

Below is the Build.txt log. No error is logged in the BuildErrors.txt. Any ideas?

Building Network: 0.0 seconds (0.0 total) - 0 MB memory [5:03:59 PM] Refine Cleaning Area: 0.2 seconds (0.2 total) - 0 MB memory [5:03:59 PM] Extract Geometry and Attribute Values: 0.1 seconds (0.3 total) - 4094 MB memory [5:03:59 PM] Extracting GreeceRoadNetwork: 0.0 seconds (0.3 total) - 4094 MB memory [5:03:59 PM] 0 features: 0.0 seconds (0.3 total) - 4094 MB memory Extracted GreeceRoadNetwork, 166 features, 390 vertices (min/max hierarchy values = 1/4): 1.4 seconds (1.7 total) - 4094 MB memory Extracting Geometry and Attribute Values Is Done: 0.0 seconds (1.7 total) - 4094 MB memory Deleting Network Elements: 0.0 seconds (1.7 total) - 4094 MB memory [5:04:00 PM] Deleted 163 edge elements: 0.0 seconds (1.7 total) - 4094 MB memory Deleted 78 junction elements: 0.0 seconds (1.8 total) - 4094 MB memory Network Elements Deleted: 0.0 seconds (1.8 total) - 4094 MB memory Matching connectivity: 0.0 seconds (1.8 total) - 7877 MB memory [5:04:00 PM] 0 vertices: 0.0 seconds (1.8 total) - 7877 MB memory Matching connectivity done Node Count: 390 Nodes Thrown Out: 58 System Junctions Created: 76 0.0 seconds (1.8 total) - 7877 MB memory Creating Junctions: 0.0 seconds (1.8 total) - 7877 MB memory [5:04:00 PM] Created 76 Junctions: 0.0 seconds (1.8 total) - 7877 MB memory Defining Edges: 0.0 seconds (1.8 total) - 9924 MB memory [5:04:00 PM] Defined 166 Edges: 0.0 seconds (1.8 total) - 9924 MB memory Creating Edges: 0.0 seconds (1.8 total) - 9924 MB memory [5:04:00 PM] Created 166 Edges: 0.1 seconds (1.9 total) - 9924 MB memory Populated hyperedge system weights: 0.0 seconds (1.9 total) - 9924 MB memory Extracting Turns: 0.1 seconds (2.0 total) - 9924 MB memory [5:04:01 PM] Extracting RestrictedTurns: 0.0 seconds (2.0 total) - 9924 MB memory [5:04:01 PM] Extracted RestrictedTurns, 0 features: 0.0 seconds (2.0 total) - 9924 MB memory Turns Extracted: 0.0 seconds (2.0 total) - 9924 MB memory Network Built: 0.0 seconds (2.0 total) - 9924 MB memory [5:04:01 PM]

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Thu, 27 Jul 2023 14:29:47 GMT

Hi. I've never seen this error before, but I'd like to investigate. Would you be able to share your data? If you can't share it publicly, you can send me a private message through this system and we can work something out.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

SOTIRIOSTRIANTOS — Tue, 05 Sep 2023 09:54:22 GMT

Hello there, I apologize for my delayed response. I spent some time observing how my colleague uses ArcGIS Pro, and I noticed an issue when they utilize the 'Validation Topology' and 'Merge to Largest' tools. The problem arises when there are more than three segments involved.

In the example below, we started with six initial segments that we wanted to merge into the largest segment. However, when we used the mentioned tool, it created multiple segments instead of merging the six initial segments.

Image 1: The segments we intended to merge.

Images 2, 3, and 4: Post-merge using the 'Merge to Largest' validation.

Image 5: The segment before using the 'Merge to Largest' tool.

When validating topology using ArcGIS Desktop 10.7.1, the 'Merge to Largest' tool works as expected, and we have never encountered the 'ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).' issue.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

ZachBodenner — Wed, 06 Sep 2023 19:53:09 GMT

Hello, I am also having this issue when running an Append operation. Did you ever find a solution? @MelindaMorang ?

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Wed, 06 Sep 2023 20:31:51 GMT

I have asked some members of another team (the ones who own the topology editing tools) to review this thread. I don't have any answers for you yet.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

ZachBodenner — Wed, 06 Sep 2023 20:43:56 GMT

Thanks for following up! If it makes a difference to your research, my layers don't have any topology associated with them.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Wed, 06 Sep 2023 21:19:39 GMT

Okay, if that's the case, please describe your workflow in more detail. It sounds like it's different from what the original user described. Please also share your data, if you're able. That would be very helpful in diagnosing and fixing the issue.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

ZachBodenner — Thu, 07 Sep 2023 13:12:14 GMT

I wish I could say it was particularly specific - all I'm doing is running an append, from a egdb feature class into a fgdb feature class. The schemas are similar but not identical, and I'm running the append using the field map. The append takes a while and seems to finish before throwing the error and resulting in no records appended. The target has attribute rules applied, but I have successfully appended into this feature class before. This seems to be a new issue.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Thu, 07 Sep 2023 15:51:05 GMT

To make sure I understand: You are not running the Build Network tool, correct? You're running the Append geoprocessing tool to append records from an egdb feature class to an fgdb feature class. Are these feature classes part of a network dataset? (The data you shared does not involve a network dataset.)

If your workflow has nothing to do with Network Analyst or topology, then it's unlikely to be related to the problem the original creator of this thread reported. It's not related to Network Analyst, so this isn't really the right area within Esri Community to get help for that. It's outside my area of expertise, so I can't really help you. Sorry! I recommend posting your question to the general ArcGIS Pro page at https://community.esri.com/t5/arcgis-pro-questions/bd-p/arcgis-pro-questions. Or, call Support. That may be a faster way to get help.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

ZachBodenner — Thu, 07 Sep 2023 16:13:25 GMT

I will do that thank you.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

SOTIRIOSTRIANTOS — Thu, 07 Sep 2023 16:28:45 GMT

@MelindaMorangI have sent you a private message. Thank you for your time in advance.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Thu, 07 Sep 2023 17:04:20 GMT

FYI, I have responded. Esri Community's private mail function does not seem to alert you by e-mail. Very annoying.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Mon, 11 Sep 2023 20:46:35 GMT

Thank for the data you sent via a private message. I am able to reproduce the error with Build Network, and I logged an issue for my team to investigate it. Unfortunately, I don't have a short-term workaround for the problem.

I have also asked some people who work with topology rules to take a look at it, since it seems likely that this is the real problem. They may follow up with you for more details or data.

Re: ERROR 160276: A row with this OID already exists. Failed to execute (BuildNetwork).

MelindaMorang — Fri, 22 Sep 2023 17:24:33 GMT

I wanted to follow up on the Build Network error. We were able to install a fix for this problem, and it will be available in the upcoming Pro 3.2 release. I'm still not sure whether some part of your editing workflow caused the network to end up in a bad state, but our changes will allow the network to build successfully.