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

[SOTIRIOSTRIANTOS]

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]

[MelindaMorang]

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.

[SOTIRIOSTRIANTOS]

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.

[MelindaMorang · Accepted solution]

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.

[MelindaMorang]

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.

[SOTIRIOSTRIANTOS]

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

[MelindaMorang]

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

[ZachBodenner]

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

[MelindaMorang]

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.

[ZachBodenner]

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