Errors are used to track inconsistent features in a utility network. Inconsistent features are those participating in situations that violate restrictions for a utility network. Errors are created when a topology is enabled or validated, and when subnetworks are updated.
Errors created for utility network features are organized in the following sections based on the operation that caused the error:
Features that are edited are evaluated when the network topology is validated or enabled. If these features violate restrictions or network rules, or create any other invalid situation, errors are produced. Invalid situations are those that are not supported due to restrictions or rules in the utility network. These situations are listed in the tables below.
Information about errors is stored and accessed differently depending upon the utility network version used. To learn more, see View errors.
Enable and validate network topology
Errors result from enabling a network topology or after validating a network topology. To fix an error, the associated network features must be corrected.
The following table lists details about the error including the situation that produces it, suggested actions for resolving the error, and the feature type it can be associated with. In the Solution column, Option 1 is often the most useful and has the least impact. However, some options depend on other factors, so the first option may not be the best for your particular case. Some options are flagged with (Admin), as they require the network topology be disabled. Examples of this are adding a domain network, assigning terminal configurations, and changing the edge connectivity policy for a feature at the asset group and asset type levels.
| Error ID | Description and situation | Solution | Feature type |
|---|---|---|---|
0 | Wrong data type. The field has invalid data type. A field has been assigned the wrong data type. For example, an integer data type for the field was expected instead of a string data type. | Option 1: Correct the data type for the field. | Point, Line, Junction Object, Edge Object |
1 | The geometry field is NULL or the geometry for the network feature is empty. For example, the shape field is NULL. | Option 1: Inspect the Network Source ID and Feature Guid of the dirty area to identify the associated feature in error. Delete and re-create the feature. A dirty area is created in the lower left-hand corner of the Service Territory extent for each feature with NULL or empty geometry. After corrections are made, ensure all dirty areas created are validated. | Point or Line |
2 | Subtype is unknown. For example, the Asset Group attribute for a network feature has a value of Unknown. | Option 1: Update the asset group attribute to a value other than Unknown. | Point or Line |
3 | Get subtype group value failed. Could not locate the asset group field in the source table or the field is NULL or 0. For example, the Asset Group attribute for a network feature is NULL. | Option 1: Update the asset group attribute. | Point or Line |
4 | Line feature has fewer than two vertices. A linear network feature has one or no vertices. For example, a line has a single To and From vertex. | Option 1: Add vertices to the line. Option 2: Delete and re-create the line. | Line |
5 | Line feature has length within tolerance. The length of a linear network feature is too short and fits within the network tolerance. For example, the network tolerance is 1 meter and a line in the network is 90 cm. | Option 1: Adjust the length of the line feature. Option 2: Adjust the network tolerance. (Admin) | Line |
6 | Geometry error—Could not locate the vertex along the line feature. The network topology cannot get the list of vertices associated with a linear network feature. | Option 1: Revalidate the network topology. Option 2: Delete the vertex, validate the network topology, and create another vertex if needed. | Line |
7 | Invalid connectivity. A network point feature is not connected to any other feature. For example, a service point is not connected to anything. | Option 1: Connect the point feature. Option 2: Delete the point feature. | Point or Line |
8 | Invalid connectivity—No junction edge rule exists. There is no junction-edge rule to support the connectivity between a point and a line, for example, a low-voltage line and the high side of a circuit breaker. | Option 1: Review rules in network properties and change the asset group and asset type of the point or line feature to satisfy an existing junction edge connectivity rule. Option 2: Add a rule to allow connectivity between the origin and destination features. (Admin) | Point, Line, Junction Object, Edge Object |
9 | Invalid connectivity—More than one junction edge rule applicable. This is an ambiguous situation where more than one rule exists that allows a line to connect to a device feature. It is also possible to receive this error if more than one device exists at the endpoint of a line. For example, a medium-voltage line is connected to a circuit breaker with junction-edge rules that allow the medium-voltage line to connect to either the source or load side of the circuit breaker. Until the terminal connectivity is established, there will be ambiguous connectivity. | Option 1: Use the Modify Terminal Connections pane to specify which terminal on the device the line connects to. Option 2: Ensure that only a single rule exists to allow connectivity between the edge and feature terminal. (Admin) | Point and Line |
10 | Invalid connectivity—Two edge features with different asset type attributes cannot connect. When two edge features share an endpoint and do not have an intermediate junction, they must be from the same asset type to establish connectivity in the network topology. For example, a medium-voltage/overhead single-phase line and a medium-voltage/overhead three-phase line are snapped together. | Option 1: Modify the asset type attributes of the edge features to match. For example, if the asset type for one feature is incorrect, modify it to match the other. Option 2: Insert a valid junction feature to connect the two edge features. There must be a supporting edge-junction-edge rule to support these features. | Line |
11 | A linear network feature has an endpoint with nothing connected to it. For example, a pipe has nothing connected to one of its endpoints. | Option 1: Place an appropriate point feature at the end. | Line |
12 | There are more than two lines connected to a point in an edge-junction-edge connectivity situation. For example, two medium-voltage overhead lines and a medium-voltage underground line are connected via a riser. Since geometric coincident-based connectivity is checked when the network topology is validated, this situation can occur while editing and then be discovered or marked with an error when the network topology is updated. | Option 1: Delete the extra lines or lines. | Point and Line |
13 | A linear feature that only allows endpoint connectivity has a point or another line feature placed midspan. For example, a tap is snapped to a midspan vertex on a lateral with an edge connectivity policy of end vertex. This does not honor the edge connectivity policy for the line. | Option 1: Relocate the feature to a vertex that honors the line edge connectivity policy. Option 2: Delete the point or line feature. Option 3: Change the edge connectivity policy for the feature. (Admin) | Point and Line |
17 | There is no containment rule to support the containment association between two features. | Option 1: Re-create the association. Option 2: Re-create the features and associations. | Point, Line, Junction Object, Edge Object |
18 | There is no structural attachment rule to support the structural attachment association between two features. | Option 1: Re-create the association. Option 2: Re-create the features and associations. | Point, Line, Junction Object, Edge Object |
19 | A linear network feature is multipart. Multipart features are not allowed. For example, this could be a multipart transmission pipe. | Option 1: Modify the feature so it is not multipart. Option 2: Delete the line and re-create it. | Line |
20 | Self-intersecting line. A linear network feature loops back and intersects itself. For example, a valid looped pipe has missing z-values. | Option 1: Place a vertex on each line segment at the point of intersection. Adjust the z-value for each vertex to add vertical space between the lines. Option 2: Split the line into single features. | Line |
21 | A linear network feature has vertices existing in the same x,y,z location. For example, a gravity pipe has missing z-values. | Option 1: Offset one of the vertices (x and y or z). Option 2: Delete one of the vertices. | Line and Edge Object |
22 | The linear network feature in the map possesses segments that are not present in the network topology. For example, a section of a main pipe is unaccounted for in the network topology. | Option 1: Revalidate the network topology. Option 2: Delete the problem segments, validate the network topology, and re-create the segments if needed. | Line |
23 | A network feature has an asset type other than the defined asset types for the asset group it belongs to. For example, a pole has a padmounted asset type. Padmounted is not an asset type defined for the Poles asset group. | Option 1: Fix the asset type for that feature. | Point, Line, Junction Object, Edge Object |
25 | Stacked point features. Two or more points are geometrically coincident. For example, a service point and a voltage regulator have the same x,y,z coordinates. Some features cannot exist in the same location, while others can. For more information, see Coincident features. | Option 1: Offset one of the points (x and y or z). Option 2: Delete one of the points. | Point |
31 | Association record is referencing an invalid from or to globalid. The association record (connectivity, containment, or structural attachment) references an invalid from or to GlobalID. An association record persists the from and to GlobalID values of objects participating in the association in the FROMGLOBALID and TOGLOBALID fields of the association record. If either of these fields references a value that is not present, an error is reported. | To resolve the association error, locate and delete the remaining feature that participates in the association. The feature can be re-created with a new GlobalID. | Point or Junction Object |
32 | Error setting weight values. This occurs when the attribute has an inline network attribute assigned and the value exceeds the max value for the reserved bits in the network topology. This is determined by the coded value domain used to create the inline network attribute. | Change the attribute value to fall within the range of allowable values for the coded value domain. Review the attribute values for the network feature in the dirty areas table. Inspect attribute fields that have an inline network attribute assigned to determine the specific attribute to edit. The Attributes and Assignments section of the network properties includes details about which network attributes are inline and the domain associated with the network attribute. Assignments list the field that the network attribute is assigned. Explore the Domains view for the coded values allowed. | Point |
34 | Feature or object in unsupported containment relationship. This error can occur when a containment association rule is deleted and the feature still participates in a containment association that the rule supported. This error can also occur if the asset group or asset type attributes for the feature are modified and there are no supporting rules. | Option 1: Check the rules for allowable containment associations in the network properties and modify the feature's attributes. Option 2: Create a containment association rule to support the relationship. (Admin) | Point, Line, Junction Object, Edge Object |
35 | Feature or object in unsupported structural attachment relationship. This error can occur when a structural attachment association rule is deleted and the feature still participates in a structural attachment association that the rule supported. This error can also occur if the asset group or asset type attributes for the feature are modified and there are no supporting rules. | Option 1: Check the rules for allowable structural attachment associations in the network properties and modify the feature's attributes. Option 2: Create a structural attachment association rule to support the relationship. (Admin) | Point, Line, Junction Object, Edge Object |
36 | The line feature has an invalid terminal. An error is encountered when the line feature has a value (other than None or Single Terminal) for the From Terminal or To Terminal fields, and one of the following applies:
| If the device at the line's endpoint doesn't support terminals, you have these options:
If there is no user device at the endpoint of the line, you have these options:
If the device supports terminals but the From Terminal/To Terminal device terminal value on the line is not a value in the terminal configuration, you have these options:
| Point and Line |
37 | A feature with the Subnetwork Tap category was found midspan to multiple lines. An error is encountered when subnetwork tap features have the following unsupported conditions:
| Edit the line and tap features to ensure the tap feature is midspan to only one line and not only located at the endpoint of line features. | Point and Line |
38 | Devices with multiple terminals cannot be midspan. An error is encountered when a device with terminals (terminal configuration) is connected to a line midspan. Even though the line feature supports midspan connections (Any Vertex Edge Connectivity), features with terminals should not be midspan. | Option 1: Relocate the device feature to a vertex at the endpoint of the line. Option 2: Replace the midspan device feature with a feature that does not have a terminal configuration. | Point and Line |
39 | Point feature has invalid terminal configuration. The device feature has an invalid value for the Terminal configuration attribute. This is used to store the valid path for the device feature. | Inspect and edit the Terminal configuration attribute for the specific feature in error. Option 1: Modify the path assigned to the feature using the Modify Terminal Path pane. Option 2: While it is recommended to use the Modify Terminal Path pane, it is also possible to manually edit the Terminal configuration attribute using the Attributes pane to point to a valid path. Tip:Use the network properties to find the valid paths for the feature by determining the Terminal Configuration Name for the specific asset group and asset type, and inspect the Terminal Configurations section for the Valid Paths. | Point |
43 | Self-intersecting edge object A from/to junction object for an edge object references the same feature. | Modify the junction-edge connectivity association for the edge object so that the associated from and to junction objects are unique. | Edge Object |
44 | Stacked junction objects | Option 1: Modify the connectivity association so that only a single junction object exists at the location. Option 2: Delete one of the junction objects. | Junction Object |
Update subnetwork
The following errors can result from updating a subnetwork in a utility network. To fix an error, the associated network features must be corrected. The table below lists details about the error including the situation that produces error, the suggested action for resolving it, and the feature type for which the error is generated.
In the Solution column, Option 1 is often the most useful and has the least impact. However, some options depend on other factors, so the first option may not be the best for your particular case. Some options are flagged with (Admin), as they require the network topology be disabled. Examples are adding a domain network, assigning terminal configurations, and changing the edge connectivity policy for a feature at the asset group and asset type levels.
| Error ID | Description and situation | Solution | Feature type |
|---|---|---|---|
24 | Invalid line feature was discovered during update subnetwork. An invalid line feature exists based on the Valid Lines value for the tier. For example, the subnetwork definition for subnetworks in a medium-voltage tier does not allow low-voltage lines. Lines created with asset group and asset types not defined in the Valid Lines property for the tier are flagged during the Update Subnetwork process. | Option 1: Disconnect or break traversability to the line. Option 2: Update the asset group and asset type attribute for the line feature to comply with the Valid Lines property for the tier's subnetwork definition. Refer to the network properties to review the Tiers subsection of the specific domain network. Option 3: Make adjustments to the subnetwork definition to include the line or device features by adding their corresponding asset group and asset type as Valid Lines. (Admin) | Line |
26 | Invalid device feature was discovered during update subnetwork. An invalid device feature exists based on the Valid Devices values defined for the tier. For example, the subnetwork definition for subnetworks in a medium-voltage tier does not allow service points. Devices created with asset group and asset types not defined in the Valid Devices property for the tier are flagged during the Update Subnetwork process. | Option 1: Disconnect or break traversability to the points. Option 2: Update the asset group and asset type attribute for the device feature to comply with the Valid Devices property for the tier's subnetwork definition. Reference the network properties to review the Tiers subsection of the specific domain network. Option 3: Make adjustments to the subnetwork definition to include the line or device features by adding their corresponding asset group and asset type as Valid Devices. (Admin) | Point |
27 | Invalid parent subnetwork discovered during update subnetwork. An invalid parent subnetwork from a subnetwork controller is discovered during update subnetwork. This can occur for hierarchical domain networks if geometric coincidence was used to establish connectivity to a subnetwork that is not the direct parent. For hierarchical domain networks, subnetworks must have parent subnetworks that are of a higher rank by a value of 1. For example, in a gas network the isolation zone (tier rank of 3) is directly connected to the system zone (tier rank of 1) instead of the pressure zone (tier rank of 2). | Option 1: Ensure your subnetworks are correctly configured within their tier rank. Subnetworks must have a parent subnetwork that is of a higher tier rank by a value of 1. To learn more, see Tier rank. Option 2: If the connectivity is incorrect, correct it. For example, connect the value to the pressure zone first. | Point |
28 | Disjoint subnetwork discovered during update subnetwork. A disjoint subnetwork was discovered in a tier that does not support this type. Updating the subnetwork will create errors for subnetwork controllers if the subnetwork is disjoint and the Support Disjoint Subnetwork property is set to False for the subnetwork definition of the tier. | Option 1: Review the network properties for the specific tier and ensure that all subnetwork controllers that have the same subnetwork name are traversable to each other to prevent disjoint subnetworks. A subnetwork trace can be used to determine traversability. Option 2: Enable support for disjoint subnetworks in the subnetwork definition. (Admin) | Point |
29 | Inconsistent subnetwork name on multiple subnetwork controllers in the same subnetwork discovered during update subnetwork. A subnetwork controller feature was found with an inconsistent subnetwork name when updating the subnetwork. This occurs when multiple subnetwork controllers are traversable to one another but do not have the same subnetwork name. For example, a mesh subnetwork named BPDJ_20 has four subnetwork controllers; one has A_26 instead of BPDJ_20 listed for the Subnetwork Name attribute. | Option 1: If the subnetwork name for the subnetwork controller is wrong, rename it using the Modify Subnetwork Controller pane. Option 2: If the subnetwork controller should not be defining the subnetwork, break traversability by disconnecting this controller from the rest of the subnetwork features. | Point |
30 | Inconsistent parent subnetwork name on multiple parent subnetwork controllers in the same subnetwork discovered during update subnetwork. A subnetwork controller feature was found with an inconsistent parent subnetwork name when updating a set of subnetworks for a hierarchical domain network. This occurs when multiple subnetwork controllers define a parent subnetwork and one is found with a different subnetwork name. | Option 1: If the subnetwork name for the subnetwork controller is wrong, rename it using the Modify Subnetwork Controller pane. Option 2: If the subnetwork controller should not be defining the subnetwork, break traversability by disconnecting this controller from the rest of the subnetwork features. | Point |
33 | Inconsistent controller asset group/asset type. The asset group or asset type of subnetwork controller has been modified. The asset group and asset type for subnetwork controller features cannot be modified. This is to ensure the terminal configuration that is assigned to a specific asset group and asset type for device features stays consistent with what is being stored for the subnetwork controller. | Option 1: Change the asset group and asset type back to the original value for the subnetwork controller. Option 2: To safely make edits to the asset group and asset type fields of a subnetwork controller, disable the subnetwork controller from the device feature before making edits to these attributes. | Point |
40 | Invalid junction feature was discovered during update subnetwork. An invalid junction feature exists based on the Valid Junctions value for the tier. Junctions created with asset group and asset types not defined in the Valid Junctions property for the tier are flagged during the Update Subnetwork process. View the errors for invalid features and inspect the asset group and asset type. Also review the network properties for the utility network. Under Tiers, in the Valid Junctions column, review the asset groups and asset types that have been defined. | Option 1: Change the asset group and asset type of the invalid feature based on the Valid Junctions in the subnetwork definition. Option 2: Change the subnetwork definition for the tier to include additional valid junctions. See Set or modify the subnetwork definition for more information. | Point |
41 | Invalid junction object was discovered during update subnetwork. An invalid junction object exists based on the Valid Junction Objects value for the tier. Junction objects created with asset group and asset types not defined in the Valid Junction Objects property for the tier are flagged during the Update Subnetwork process. View any errors for invalid objects and inspect the asset group and asset type. Also review the network properties for the utility network. Under Tiers, in the Valid Junction Objects column, review the asset groups and asset types that have been defined. | Option 1: Change the asset group and asset type of the invalid object based on the Valid Junction Objects in the subnetwork definition. Option 2: Change the subnetwork definition for the tier to include additional valid junction objects. See Set or modify the subnetwork definition for more information. | Junction Object |
42 | Invalid edge object was discovered during update subnetwork. An invalid edge object exists based on the Valid Edge Objects value for the tier. Edge objects created with asset group and asset types not defined in the Valid Edge Objects property for the tier are flagged during the Update Subnetwork process. View any errors for invalid objects and inspect the asset group and asset type. Also review the network properties for the utility network. Under Tiers, in the Valid Edge Objects column, review the asset groups and asset types that have been defined. | Option 1: Change the asset group and asset type of the invalid object based on the Valid Edge Objects in the subnetwork definition. Option 2: Change the subnetwork definition for the tier to include additional valid edge objects. See Set or modify the subnetwork definition for more information. | Edge Object |