ArcGIS Server 11.1 Utility Network and Data Management Patch 2

Esri announces the ArcGIS Server 11.1 Utility Network and Data Management Patch 2. This patch addresses several functional issues with the 11.1 utility network release. Apart from those explicitly listed, the patch also targets performance issues in the enterprise system, specifically related to the utility network with an emphasis on enhancing quality and performance in the areas of validate, update subnetwork, and reconcile. It is recommended for all utility network customer using ArcGIS Enterprise 11.1.

This Utility Network and Data Management patch is cumulative and includes all fixes from earlier Utility Network and Data Management patches. These fixes are listed below under Issues addressed with this patch.

• BUG-000162973 - Remove the option recompile from branch versioned query statements
• BUG-000162360 - Performing an isolation trace with a directional device near the isolated section returns incorrect trace results.
• BUG-000161813 - Honor directional devices when calculating flow direction in loops.
• BUG-000161112 - Reduce ArcSOC memory footprint by not cloning class definition
• BUG-000160068 - Evaluate batch calculation should reset validationstatus requireValidation
• BUG-000161000 - Incorrect Line Number reported on invalid arcade
• BUG-000159579 - In ArcGIS Pro, the Utility Network connected traces do not honor User Defined Barriers when Filter Function Barriers are configured.
• BUG-000159117 - The Export Subnetwork tool does not include domain descriptions in the JavaScript object notation (JSON) for text or string fields included in the Result Fields.
• BUG-000158963 - Improve the performance of trace when returning aggregated geometry results.
• BUG-000158962 - Improve the trace performance when returning results that contain a large number of associations.
• BUG-000158628 - A downstream trace runs indefinitely in an infinite loop when specifying a target tier in some scenarios.
• BUG-000157838 - When using the Validate Network Topology tool, an edit operation failed and returns a General Function Failure error.
• BUG-000157809 - Validating a topology fails and the following error message, "Edit operation failed. ERROR: General function failure [Topology entry (edge eid: xxxx) not found for feature" is returned.
• BUG-000157992 - Phase propagation loses phase in certain 'loop' situations.
• BUG-000157709 - In ArcGIS Utility Network, the dirty area of an updated subnetwork which intersects other sub-network geometry invalidates all intersected sub-networks and makes them dirty.
• BUG-000157672 - When working in a utility network, an asynchronous validation at the full extent timeouts after two hours.
• BUG-000156421 - Provide a more informative error message when failures are encountered with a large number of starting points when running a Trace.
• BUG-000156042 - Passing privileges on a feature class in SAP HANA through database roles does not work in ArcGIS Pro.
• BUG-000155331 - Attribute propagation for the 'phaseenergized' attribute of an electric line conductor in an electric utility network is occurring in the upstream direction despite terminals set on transformer to only allow for downstream flow.
• BUG-000149393 - The Validate Network Topology tool fails and returns the error message, "Error building network: Topology Engine::query from_to_ junctions(): Topology entry not found".
• BUG-000149291 - The utility network error is not created when a structure junction is placed coincident to a shared endpoint by Electric Lines with a different asset type.
• BUG-000149046 - The Ignore Barriers At Starting Point parameter is not honored for Filter Barriers placed on line features.
• BUG-000148077 - Adjacent subnetworks do not show up in the results of Downstream Utility Network Trace.
• BUG-000146928 - The Validate Network Topology tool fails on specific dirty area extent and returns the error message, "Error 999999 (Topology entry (from junction eid) not found.)".

To avoid conflicts this patch also addresses:

• BUG-000160150 - Allow applyEdits with UseObjectIDsForAdds to accept adds without object ids.
• BUG-000158867 - Allow extracting a subset of a full model utility network for tracing in the field.
• BUG-000156763 - Post must obtain the current list of modified tables for a version prior to the posting operation.
• BUG-000155261 - The Conflict Manager fails to display conflicts when a subtype group layer is published as a referenced feature service.
• BUG-000154794 - Subnetwork traces stop unexpectedly by associations not present in the network index
• BUG-000154758 - Improve query performance during the update subnetwork operation.
• BUG-000154369 - Avoid rewriting the element associations pages when not necessary.
• BUG-000154328 - The Evaluate Rules geoprocessing tool does not consider selected rows from tables.
• BUG-000148398 - Poor asynchronous validate performance at the full extent in the Default version.

This patch should be installed on all ArcGIS Server installations related to the ArcGIS Server site.

The ArcGIS product listed in the table must be installed on your system before you can install a patch. Each patch setup is specific to the ArcGIS product in the list. To determine which products are installed on your system, please see the How to identify which ArcGIS products are installed section. Esri recommends that you install the patch for each product that is on your system.

Step 1. Download the appropriate file to a location other than your ArcGIS installation location.

Step 2. Make sure you have write access to your ArcGIS installation location.

Step 3. Double-click ArcGIS-111-S-UNDM2-Patch.msp to start the setup process.

NOTE: If double clicking on the MSP file does not start the setup installation, you can start the setup installation manually by using the following command:

Complete the following install steps as the ArcGIS Install owner. The Install owner is the owner of the arcgis folder. This patch should be installed on all ArcGIS Server installations related to the ArcGIS Server site.

The ArcGIS product listed in the table must be installed on your system before you can install a patch. Each patch setup is specific to the ArcGIS product in the list. To determine which products are installed on your system, please see the How to identify which ArcGIS products are installed section. Esri recommends that you install the patch for each product that is on your system.

Step 1. Download the appropriate file to a location other than your ArcGIS installation location.

Step 2. Make sure you have write access to your ArcGIS installation location, and that no one is using ArcGIS.

Step 3. Extract the specified tar file by typing:

Step 4. Start the installation by typing:

This will start the dialog for the menu-driven installation procedure. Default selections are noted in parentheses ( ). To quit the installation procedure, type 'q' at any time.

When a hotfix or patch for ArcGIS has been applied, it may also be necessary to upgrade your geodatabase depending on the nature of fixes included. See the Upgrade the Geodatabase section on the Geodatabase management page for your individual DBMS platform for more information. Executing the steps below will not cause any harm if your geodatabase is already at the required level, so the recommended approach is to follow the steps as outlined. If your database is already at the required level, you will get a message indicating so.

Upgrading from ArcGIS Server requires the use of Python. If you are working with ArcGIS Server on Windows or Linux, you can access the appropriate Python 3 environment by using the python.exe which is included with the framework/runtime components of ArcGIS Server. Additionally, on Windows a script batch file is available to launch the Python 3 environment.

To perform the upgrade, create a script using this example Python syntax, and name the script upgrade_gdb.py.

On Windows, run the upgrade script explicitly using the Python 3 environment. If ArcGIS Server is installed to the default location, the script can be executed with either of the following commands:

Or

On Linux, launch the Python 3 environment using the following commands:

source /<arcgis_server_installation_directory>/arcgis/server/framework/etc/arcenv
unset LD_PRELOAD
unset CONDA_DEFAULT_ENV

And then execute the upgrade script with the following command:

wine "Z:\<arcgis_server_installation_directory>\arcgis\server\framework\runtime\ArcGIS\bin\Python\envs\arcgispro-py3\python.exe" <path_To>\upgrade_gdb.py

To uninstall this patch on Windows, open the Windows Control Panel and navigate to installed programs. Make sure that "View installed updates" (upper left side of the Programs and Features dialog) is active. Select the patch name from the programs list and click Uninstall to remove the patch.

To remove this patch on versions 10.7 and higher, navigate to the <Product Installation Directory>/.Setup/qfe directory and run the following script as the ArcGIS Install owner:

Restart your ArcGIS services.

To determine which ArcGIS products are installed, choose the appropriate version of the PatchFinder utility for your environment and run it from your local machine. PatchFinder will list all products, hot fixes, and patches installed on your local machine.

PatchFinder for Windows

PatchFinder for Linux/Unix