ArcGIS Server 11.3 Utility Network and Data Management Patch 1

Esri announces ArcGIS Server 11.3 Utility Network and Data Management Patch 1. This patch addresses several functional issues with the 11.3 utility network release. Apart from those explicitly listed, the patch also targets tracing, validate and update subnetwork subsystem of the Utility Network, with an emphasis on enhancing quality and performance. It is recommended for all utility network customers using ArcGIS Enterprise 11.3. This patch deals specifically with the issues listed below under Issues addressed with this patch.

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-000178622 - Reconcile fails in unique cases where the version was created, modified and/or reconciled within the initial ten minutes of the version being created.
• BUG-000178339 - Leaked application locks can cause the service process to crash
• BUG-000178338 - Workspace application locks leak can prevent users from reconciling, posting, or editing in a version.
• BUG-000176902 - Optimize the population of the logfile table by utilizing an array insert instead of single-row writes.
• BUG-000176744 - Avoid branch versioning reconcile serialization lock errors.
• BUG-000174795 - The conflicts operation in the REST endpoint retrieves the default representation of a feature using an incorrect moment.
• BUG-000173951 After upgrading 10.9.1.x and the earlier version of the SQL Server Enterprise geodatabase using ArcGIS Pro 3.0 and later, Sync Layers deletes the existing layers and creates new ones.
• BUG-000173367 - Rebind the pipe_name variable on each execution when returning rowids to its appropriate pipe
• BUG-000174354 - Reconciling by attribute with a branch versioned feature service does not detect conflicts even when conflicting features exist.
• BUG-000173979 - Encountering error “A database error was encountered. Please contact your system administrator to review server logs” when attempting to reconcile more than 1000 records on branch-versioned data.
• BUG-000173229 - The error "Insufficient permissions" is returned when executing reconcile asynchronously if the service was published by a database user without permissions for a different utility network.
• BUG-000172544 - Millisecond values of timestamps are truncated in certain internal operation for SAP HANA transaction management model
• BUG-000172543 - unexpected update to the layer's M (measurement) extent values during edit operation even if the layer has no measurement values
• BUG-000172542 - Lock wait timeout setting in SAP HANA transaction management model may potentially cause failure in concurrent editing.
• BUG-000172096 - Connections and locks from referenced services are never removed from Amazon Web Services (AWS) Aurora PostgreSQL geodatabase.
• BUG-000172060 - Editing branch versioned data with cascading attribute rules returns the error "ORA-00001: unique constraint violated" if the feature being edited has a large number of vertices.
• BUG-000172057 - Duplicates can be created when Update Subnetwork is run concurrently in default.
• BUG-000172025 - "ERROR 003644: A database error was encountered. Please contact your system administrator to review the server logs." is returned while upgrading an enterprise geodatabase after installing the ArcGIS Server Branch Versioning Data Consistency Patch for ArcGIS Server 11.1.
• BUG-000171936 - Running the Validate Network Topology tool fails after three hours for more than two million dirty areas.
• BUG-000171829 - Undoing an edit and applying a new edit after an Evaluate Rules operation returns the error message "Invalid branch moment".
• BUG-000171605 - The Enable Network Topology geoprocessing tool lags, stalls, or fails to progress for a utility network containing 14.5 million dirty areas.
• BUG-000171184 - The Update Subnetwork tool fails and returns the error message, "ERROR 001872: A database error was encountered."
• BUG-000170589 - High memory utilization by the SAP HANA service when serving large numbers of spatial query requests.
• BUG-000170275 - The Enable Network Topology tool performs slowly when there are a large number of errors.
• BUG-000169552 - Placing a filter barrier on the same line as a starting point that features a branched segment for an isolation trace returns incorrect results.
• BUG-000169442 - Support HANA Cloud application lock API for branch versioning transaction model
• BUG-000169138 - Posting edits in a branch-versioned feature layer fails due to a duplicate constraint violation error during conflict resolution if the ArcGIS Server Branch Versioning Data Consistency Patch is applied.
• BUG-000168662 - A function barrier does not honor the partial shape length when a starting point is placed along an edge with a directional trace.
• BUG-000168174 - The update subnetworks operation is not setting the subnetwork name correctly on boundary devices, which are subnetwork controllers.
• BUG-000167975 - Validate Network Topology fails with General function failure Invalid network element id error
• BUG-000167572 - Dirty areas with empty geometries are generated after validating a network topology.
• BUG-000166688 - Running Migrate ObjectID to 64 bit can recreate branch versioned class indexes incorrectly.
• BUG-000166025 - Improve the Enable and Validate network topology by selecting the required fields.
• BUG-000164368 - Remove the binding used for pagination queries offset and next values.
• BUG-000137206 - The Aggregate Geometry trace results are not honoring the mid-span end when using a filter function barrier.

To avoid conflicts this patch also addresses:

• BUG-000179884 - There is a security vulnerability in ArcGIS Server Feature Services.
• 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-000176927 - Inefficient branch versioning queries with log files and predicate filters are impacting performance and scalability.
• BUG-000176553 - Georeferenced PDF exports of a layout show incorrect display of halo sizes for symbols in ArcGIS Pro 3.5.
• BUG-000176107 - Network Dataset enters in a state of failure after performing an edit.
• 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-000174354 - Reconciling by attribute with a branch versioned feature service does not detect conflicts even when conflicting features exist.
• BUG-000173951 - After upgrading 10.9.1.x and the earlier version of the SQL Server Enterprise geodatabase using ArcGIS Pro 3.0 and later, Sync Layers deletes the existing layers and creates new ones.
• BUG-000173336 - Build Network GP Tool fails with ERROR 160114: A requested feature object could not be located when building Network Dataset on non-versioned SQL Server database
• BUG-000173231 - When running the exportTiles function in ArcGIS Enterprise in 11.3 and 11.4 at the REST endpoint, regardless of levels to be exported, jobs take over a minute longer to complete the export than other Enterprise versions, and get stuck on 'Manage Package info files' request.
• BUG-000173230 - When sending multiple POST requests in quick succession using the exportTiles function in ArcGIS Server, the first job succeeds, but the subsequent jobs fail.
• BUG-000173000 - While accessing branch version conflicts with the ArcGIS Pro Conflict Manager, "Additional conflicts found, but failed to process them. Enable diagnostic log to gather more information" is displayed as a warning in the Conflict Viewer.
• BUG-000172949 - Publishing from ArcGIS Pro to ArcGIS Enterprise generates ArcGIS Server to return the error message, "Failed to Update Service Item Data Json file to Portal".
• BUG-000172895 - The ArcGIS Experience Builder Select widget fails to query referenced map services with an in-memory join between different databases or workspaces
• BUG-000171743 - "/Generate" function within Portal for ArcGIS Sharing REST Endpoint does not change spatial reference from Web Mercator (WKID: 102100) when specifying differing WKID in "Publish Parameters".
• BUG-000171619 - The pop-up configuration is lost when publishing a service from ArcGIS Pro 3.3.x to ArcGIS Enterprise 11.3 if the ArcGIS Portal Directory is disabled.
• BUG-000171160 - The ArcGIS Routing service does not reflect changes made to the network dataset and requires a service restart to reflect changes.
• BUG-000170853 - Taking utility network data offline as simple features passes the wrong bit value in the createReplica call.
• BUG-000170852 - Creating associations does not honor the userGlobalIDs parameter in the applyEdits operation.
• BUG-000167572 - Dirty areas with empty geometries are generated after validate network topology.
• BUG-000166613 - The Export Map and Legend operation fails in ArcGIS Server REST API when listing a sublayer before a group layer in the dynamic layers parameter.
• BUG-000166180 - Applying a filter using a date field on a map image layer does not work when the source map service is published by reference from an enterprise geodatabase.
• BUG-000164465 - The Cloud Raster Format (CRF) build pyramids process often fails for scale levels 8 and above when using Microsoft Azure Blob Storage or Amazon Simple Storage Service (S3) as a raster store.
• BUG-000158284 - Hosted tables fail to synchronize in distributed collaborations between ArcGIS Enterprise and ArcGIS Online.
• BUG-000156453 - The arcpy.management.ChangeVersion() tool does not work when executed from a python toolbox but runs fine from ArcGIS Notebooks and the Python window in ArcGIS Pro.
• BUG-000153113 - The output of the Pivot Table tool does not include all values of the input value field.

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.

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

Step 3: Double-click ArcGIS-113-S-UNDM-Patch1.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.

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

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