ArcGIS Server 11.5 Utility Network Patch 3

Esri announces the ArcGIS Server 11.5 Utility Network Patch 3. This patch addresses several functional issues with the 11.5 utility network release. Apart from those explicitly listed, the patch also targets validate and reconcile for the Utility Network, with an emphasis on enhancing quality and performance. It is recommended for all utility network customers using ArcGIS Enterprise 11.5. This Utility Network patch is cumulative and includes all fixes from earlier Utility Network and Data Management patches. This patch deals specifically with the issues listed below under Issues addressed with this patch.

As part of the patch installation, the ArcGIS Server service is stopped and restarted. The restart may take several minutes depending on the number of services published on the ArcGIS Server site.

This patch can be uninstalled as outlined in the Uninstalling this patch on Windows and Uninstalling this patch on Linux sections below.

Esri recommends developing a rollback plan before installing patches. For those utilizing a highly available environment, refer to the help topic on how to apply patches in a highly available environment for guidance.

• BUG-000184727 - The Validate Network Topology tool returns a DBMS error when the IN list query for Oracle contains more than 1,000 values.
• BUG-000184239 - Full extent validation fails with error 999999 general function failure.
• BUG-000184460 - Reconcile fails and returns the "ERROR 160276: A row with this OID already exists." error message.
• BUG-000183017 - When updating subnetworks, an applock error occurs and includes the globally unique identifier (GUID) of the object being locked.
• BUG-000182056 - When using direct-write, subnetlines and controllers in the subnetworks table are marked as dirty during network topology disablement.
• BUG-000179935 - Utility network associations validated in a version are posted and reappear in the default version.
• BUG-000171936 - Running the Validate Network Topology tool fails after three hours for more than two million dirty areas.

To avoid conflicts this patch also addresses:

• BUG-000184560 - The validate network topology operation unnecessarily counts the number of dirty areas.
• BUG-000183616 - The utility network isolation trace in ArcGIS Pro 3.5.6 and ArcGIS Enterprise 11.5 fails due to a service timeout.
• BUG-000183592 - Query operation on reference feature service sourced from PostgreSQL and PostGIS geometry type results in ST_setSRID using a spatial reference ID value of -1 causing avoidable conversion and degrading performance.
• BUG-000183319 - Post must get the can_post property from the write lock.
• BUG-000182524 - When using the parcel fabric and the Build Extent command, only use the lines in the visible map extent.
• BUG-000182397 - Shared feature templates stored on a reference feature service return an empty definition when a German special character is present in the attribute properties of the feature template.
• BUG-000182391 - createReplica REST operation fails against SAP HANA Cloud referenced feature services: "Unable to complete operation. Error in performing CreateReplica operation."
• BUG-000182187 - Performing a batch attribute calculation can break subsequent validation attribute rule evaluations.
• BUG-000182039 - Allow Evaluate Rules to terminate early without processing the entire input.
• BUG-000181414 - Optimize the overlap detection logic during the update subnetwork operation.
• BUG-000181367 - The internal reference counter is not being released when transactions are aborted (rolled back) leading to lock request errors.
• BUG-000181361 - Calculated Area is not calculated for some parcels in the parcel fabric.
• BUG-000179949 - The behavior of posting edits changes after upgrading from ArcGIS Enterprise 11.3 to 11.5 and returns the "Partial post violates relational integrity. [Inserted or updated rows require associations: (association object ID)]" error message.
• BUG-000179884 - There is a security vulnerability in ArcGIS Server Feature Services.
• BUG-000179851 - Update subnetworks fails with subnetwork is not dirty (active dirty controller, deleted clean controller)
• BUG-000179774 - A subnetwork trace operation for Update Subnetwork is inefficiently querying the Subnetworks table for each device that is a controller.
• BUG-000179357 - Running an isolation trace returns the error message "Warning 002535: No isolating feature was discovered" even when isolating features are expected to be present.
• BUG-000179322 - Evaluate calls differences on unmodified classes.
• BUG-000179206 - Performance degradation in Trace with subnetworks containing large cardinalities of connectivity associations with nonspatial objects.
• BUG-000178964 - Remove "hasContingentValuesDefinition": true property on layer resource for references feature services.
• BUG-000178701 - The full extent validation should check if the objects are dirty before exiting early.
• BUG-000178298 - Allow editing on simple branch versioned datasets without the ArcGIS Advanced Editing user type extension license.
• BUG-000178209 - Remove ArcGIS Advanced Editing user type extension license checks for specific endpoints in the Version Management Service.
• BUG-000177759 - Perform association expansion on a selected object in validate by selection set.
• BUG-000177471 - Optimize generation of the default replica name in the createReplica operation.
• BUG-000177433 - Unexpected layer extent updates due to improper initialization of M value when updating layer's metadata.
• BUG-000177314 - Update stored procedures for geodatabase metadata updates in the default transaction to use autonomous transactions.
• BUG-000177176 - Inconsistencies in the last_edited_date editor tracking field values may occur after executing the UpdateFeatures operation via the ArcGIS REST API.
• BUG-000177018 - When run on features modified in this version, evaluate rules operation assembles selection sets for layers that do not have attribute rules configured on them.
• BUG-000176927 - Inefficient branch versioning queries with log files and predicate filters are impacting performance and scalability.
• BUG-000176869 - The Update Subnetwork tool attempts to manage the 'supportingsubnetworkname' and 'supportedsubnetworkname' classes even when the class is not configured to support this behavior.
• BUG-000176825 - Evaluate operation is adding objectids to the selection set one at a time.
• BUG-000176553 - Georeferenced PDF exports of a layout show incorrect display of halo sizes for symbols in ArcGIS Pro 3.5.
• BUG-000176315 - GetEstimates request on feature service is causing significant performance issues when opening an ArcGIS Pro Map containing referenced feature services.
• BUG-000176098 - SQL Server wait event resource_semaphore contention encountered because branch versioned queries on large tables with low selectivity result in the optimizer generating massive memory grants.
• BUG-000176059 - Validate Network Topology leaves a sliver of dirty area that cannot be cleaned.
• BUG-000176040 - Isolation trace run with the option to Include Isolated Features returns huge numbers of features outside the Isolation Zone.
• BUG-000175851 - A query operation performed in ArcGIS Experience Builder on a referenced feature service returns the "Error: Underlying DBMS error - The geometry data type cannot be selected as DISTINCT because it is not comparable." error message in ArcGIS Server Manager.
• BUG-000170932 - Definition queries based on a shape-related field fail to verify the SQL expression for published feature service using ArcGIS Pro when standardized queries for the ArcGIS Server site are disabled.
• BUG-000170530 - The utility network isolation trace includes isolated features that return adjacent subnetworks.
• BUG-000169677 - In the ArcGIS REST Services Directory interface, a query on a query layer with SDO_Geometry fails when using an object IDs filter.
• BUG-000160615 - The ArcGIS Utility Network Topology for validation in the ArcGIS REST APIs requires a validateArea to be input which overrides all specified objects in the validationSet.
• BUG-000156661 - Labels get rotated when the map is rotated when working with a referenced Map Service Layer (MapServer) in ArcGIS Pro.
• BUG-000152968 - If the publisher database is different from the server database during publishing with ArcGIS Pro, and ArcGIS Server can access the publisher database, the PublishingTools makes a connection to every layer in the publisher database, leading to a performance issue with publishing.
• BUG-000141682 - Unexpected association conflicts occur in named versions after reconcile and post process with DEFAULT and Validate Network Topology within the UN_<>_ASSOCIATIONS table and Conflict Manager.
• BUG-000136527 - Uploading a GeoJSON file as a hosted feature service in the ArcGIS Enterprise portal does not honor any field types if the GeoJSON structure specifies the property value between quotations.

On Windows, the release date order of the patches does not matter when installing multiple patches. If an older patch is installed after a newer patch, the newer patch takes precedence and the fixes from the newer patch will remain. The ArcGIS Enterprise Patch Notification tool, when the option to install all available patches is activated, installs multiple patches in order of release date starting with oldest to newest.

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.

ArcGIS Enterprise 11.5
ArcGIS Server	ArcGIS-115-S-UN-Patch3.msp
Checksum      (SHA256)	11859B0BE4307C7241F70D7F8BEC1DD8999A55F32CD34AC322DA1A10092EB332

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

Step 3: Double-click ArcGIS-115-S-UN-Patch3.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:

On Linux, the release date order of the patches matters when installing multiple patches. If an older patch is installed after a newer patch, the older patch will replace the newer patch and the fixes in the newer patch will be removed. The ArcGIS Enterprise Patch Notification tool, when the option to install all available patches is activated, installs multiple patches in order of release date starting with oldest to newest.

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.

ArcGIS Enterprise 11.5
ArcGIS Server	ArcGIS-115-S-UN-Patch3-linux.tar
Checksum      (SHA256)	FC86B318B56CE58514E2A1A31077252B016DECA082DA3E8CC1470C26CC6A1458

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:

When installing this patch, it is necessary to upgrade your geodatabase to achieve full value from the fixes included. 

Upgrading from ArcGIS Server requires the use of Python. When 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.

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.

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.

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