topic Re: Subnetwork Controller Import Error in Gas and Pipeline Questions

Subnetwork Controller Import Error

MarkCederholm — Thu, 18 Oct 2018 17:10:54 GMT

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.]

Re: Subnetwork Controller Import Error

MarkCederholm — Thu, 18 Oct 2018 19:21:07 GMT

The tool works if I assign each valve to only one subnetwork. This complicates things as I will have to work out the logic to assign valves singly without leaving orphaned subnetworks. I'm still puzzled as to why the tool allowed a number of multiple assignments to pass before it finally failed.

Re: Subnetwork Controller Import Error

RobertKrisher — Fri, 19 Oct 2018 14:32:53 GMT

As long as each row is referencing a different terminal you should be fine. Is it possible that the other valve were each referencing different terminals and this latest valve has two or more rows referencing the same terminal?

Re: Subnetwork Controller Import Error

MarkCederholm — Fri, 19 Oct 2018 14:47:15 GMT

No, that's not the case. I verified that the valve in question had a unique name, but I'll do some more digging in case the row number in the error message was misleading.

Re: Subnetwork Controller Import Error

MarkCederholm — Tue, 23 Oct 2018 22:23:07 GMT

I have verified via the Pro SDK that I can only assign one emergency valve terminal as an isolation subnetwork controller -- if I try to assign the other terminal to the adjacent subnetwork, it fails. [Update: I also verified it manually using the Modify Subnetwork Controller pane]

Apparently, the reason the same valve kept failing in the GP tool, no matter where it was in the CSV file, is that the file is digested and then controllers are processed in the order that valves are retrieved from the GDB.

Re: Subnetwork Controller Import Error

RobertKrisher — Tue, 23 Oct 2018 22:27:05 GMT

Mark,

That definitely seems like a bug (I'm assuming a manual test would also fail), if you haven't already logged a bug with Esri I'd definitely do that. Each terminal on an emergency valve should definitely be able to act as its own isolation controller. Are you going to be at GeoConX?

Re: Subnetwork Controller Import Error

MarkCederholm — Tue, 23 Oct 2018 22:32:41 GMT

Unfortunately, no -- 2 others from my department are going. I'll go ahead and start a support request and see what Esri has to say about this.

Re: Subnetwork Controller Import Error

MelissaJarman — Thu, 25 Oct 2018 19:33:24 GMT

Mark -

Please let us know the case number after you contact our support team.

ERROR 002128: The subnetwork controller name already exists

The error you received should be returned when the subnetwork controller name used in the CSV file is not unique within the specified tier.

Re: Subnetwork Controller Import Error

MarkCederholm — Mon, 29 Oct 2018 14:49:51 GMT

Case #02207792

Re: Subnetwork Controller Import Error

MarkCederholm — Mon, 29 Oct 2018 17:01:55 GMT

Well, I finally found a way to get it to work. I was trying to find a way to assign unique controller names, but the GP tool kept telling me that it was an invalid name, and could only get it to accept the valve name without modification (for example, if the valve name was "FLS272", I could not get "FLS272a" to work. This morning I tried using "Port Name/Valve Name" (e.g. "Port One/FLS272") and the tool ran without an error.

Re: Subnetwork Controller Import Error

MarkCederholm — Tue, 30 Oct 2018 16:15:15 GMT

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.

Re: Subnetwork Controller Import Error

MelissaJarman — Tue, 30 Oct 2018 16:45:59 GMT

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.