Subnetwork Controller Import Error

[MarkCederholm]

Could somebody please explain fully "ERROR 002128: The subnetwork controller name already exists" in the GP tool ImportSubnetworkControllers?  I understand that a controller cannot be assigned to the same subnetwork twice, but I cleaned those up.  The tier in question is "Pipe Distribution Isolation", and the controller in question is "Controllable Valve,Emergency".  Can a controller, even if bidirectional, only be assigned to one subnetwork?  If so, why did the tool not complain about other valves earlier in the import file?  [And no, there are no duplicate port assignments.]

[MarkCederholm]

I just tried to duplicate this problem with Esri tech support, and this time my original "a/b" approach worked just fine with the GP tool.  At this point, I'm a bit stumped as to why it was failing before.  There are limitations to special characters, as given in the documentation:

Set a subnetwork controller—ArcGIS Pro | ArcGIS Desktop 

but I don't recall using an illegal character.  The only other reason I can think of is that I might have had unremoved subnetwork controllers when I was experimenting with the import script.

[MelissaJarman]

Thanks for sending an update Mark. I was wondering if there was somehow a controller using the same subnetwork controller name in the Subnetworks table from previous attempts/tests.

The import process is basically setting the device feature as a subnetwork controller, just like the process of using the Modify Subnetwork Controller pane while working with an active map.

I appreciate your updates on this one. If you do come across an instance where you are receiving this error falsely please contact us back and we can investigate. 

Here are some general guidelines when importing controllers or setting device features as subnetwork controllers:

• The name of a new subnetwork is unique within the utility network.
• The name of the subnetwork controller is unique within the tier.