Patches and updates

ArcGIS Server 10.8.1 Utility Network Patch 8

Published: October 25, 2022


This patch addresses several functional issues with the 10.8.1 utility network release. In addition to the issues listed below, the patch addresses issues focused around reconcile, validate, update subnetwork and performance of utility networks.


EsriĀ® announces the ArcGIS Server 10.8.1 Utility Network Patch 8. This patch focuses on quality and performance particularly in the areas of validate, update subnetwork and reconcile, and is recommended for all utility network customers using ArcGIS Enterprise 10.8.1. This patch deals specifically with the issues listed below under Issues Addressed with this patch.

Note: SQLServer clients are required to upgrade using this patch to leverage all of the fixes made available. Please see the Upgrade a geodatabase section for upgrade instructions.


Issues Addressed with this patch


  • BUG-000152495 - Export subnetwork files must have the correct server prefix to allow the server to delete files.
  • BUG-000152378 - Remove singleton queries from validate when accessing the eidmappings table.
  • BUG-000152239 - Heuristic to improve the Validate Consistency performance.
  • BUG-000152209 - Validate returns the discovered subnetworks in the response payload.
  • BUG-000152047 - Optimize Oracle branch version spatial query to use DBMS 'rowid' instead of 'gdb_archive_oid' when joining to the analytic subquery.
  • BUG-000152042 - The branch versioning reconcile and post require an application lock to ensure only one SOC per session can perform the operations.
  • BUG-000152041 - Reconciling a version fails with the following error, "Null geometries are not allowed."
  • BUG-000151865 - Poor performance when running ValidatingSubnetworkTraceResult during the Update Subnetwork operation.
  • BUG-000151822 - Slow performance when viewing associations in Oracle.
  • BUG-000151804 - The sde_purge_process_information procedure and delete statement can become blocked by uncommitted transactions on sys.objects.
  • BUG-000151789 - Feature.AssociationStatus is out of sync after creating associations via an attribute rule.
  • BUG-000151626 - Remove the singleton query from midspan connectivity processing.
  • BUG-000151624 - Add MAXDOP 1 to all branch versioned queries that do not have a spatial or attribute-provided query filter.
  • BUG-000151544 - The sde_branch_tables_modified primary cluster key must be branch_id, edit_moment, and registration_id.
  • BUG-000151543 - Remove NOT EXISTS statements and replace them with where 'rn > 1' for branch versioning procedures.
  • BUG-000151537 - Add the forceseek index hint to the delete statement in the SDE_Branch_modified_def_delete_procedure.
  • BUG-000151487 - The Validate command does not remove dirty areas for features when error features are created.
  • BUG-000151443 - The Validate Network Topology tool with a Utility Network Version 3 deletes dirty areas when error features are present.
  • BUG-000151400 - Creating multipart dirty area results in a SE_SHAPE with CAD properties.
  • BUG-000151399 - Remove singleton query during the build to cache containment and attachment association records.
  • BUG-000151397 - Silver dirty area features are not being removed by validate.
  • BUG-000151335 - The validate process generates invalid errors for line terminals due to clipping.
  • BUG-000151324 - Address duplicate vertex errors caused by conflicting XY and Z tolerances.
  • BUG-000151323 - The validate network topology operation is fetching the entire subnetworks table.
  • BUG-000151321 - The validate network topology operation on a UN3 release is incorrectly fetching all error features.
  • BUG-000151315 - Validate is fetching the entire dirty area class.
  • BUG-000151314 - Enable or validate using the wrong error code for vertices within the spatial reference tolerance, which must be error code 5.
  • BUG-000151237 - Reconciling a branch version returns an error, "The index passed was not within the valid range".
  • BUG-000151073 - Random poor performance and response times are encountered when editing, validating or reconciling versions.
  • BUG-000151002- Updating subnetworks using the NOT IN clause can cause an impact on performance.
  • BUG-000150652 - Utility Network Version 3 produces duplicate records for the same type of dirty area for the same modified feature.
  • BUG-000150504 - When editing vertices to relocate an electric junction and change the subnetwork connected to the service line, mark the new subnetwork as dirty while the original subnetwork is never flagged as dirty preventing the Update Subnetwork tool from being performed.
  • BUG-000149876- RestoreRow fails when an origin row is restored and participates in two relationship classes.
  • BUG-000149496 - Improve the validation performance for queries to the EIDMapping table.
  • BUG-000149297 - Aggregated trace results with a function barrier on the shape length are returning the entire line.
  • BUG-000148965 - The validation service operation checks the entire data workspace instead of only validating the layers included in the service.
  • BUG-000148539- Reconciling a utility network's named version returns the error message, "The subnetwork controller name already exists in the specified tier. []."
  • BUG-000148331- The IsDirty property is not set to 'True' after editing an embedded tier in the utility network. Subsequently, the Subnetwork Name for lower tiers is not updated, even after running Update Subnetwork.
  • BUG-000147713 - Validating topology on specific dirty areas in a customer utility network fails with a generic error.
  • BUG-000147190 - Asynchronous Database cursors can cause performance impacts on SQL Server keyset cursors.
  • BUG-000146650 - The contingent values are not ported over when switching from the default version to a child version using the Contents pane.
  • BUG-000145428 - Optimization to reconcile by avoiding expensive sublineage queries by removing the 'not in' clause.
  • BUG-000145334- A dirty area returns "Status 9" after validation when the errors are created (expect '8').
  • BUG-000144260 - Slow performance when reconciling a branch version in PostgreSQL using the default work_mem settings.

To avoid conflicts on 10.8.1 this patch also addresses:

  • BUG-000151587 - In ArcGIS Server 10.8.1, using the createReplica operation in the REST endpoint creates a corrupt geodatabase when the referenced feature class has an index with 11 or more columns.
  • BUG-000151237 - Reconciling a branch version returns an error, "The index passed was not within the valid range".
  • BUG-000151073 - Users are encountering random poor performance and response times when editing, validating or reconciling versions.
  • BUG-000149876 - RestoreRow fails when an origin row is restored and participates in two relationship classes.
  • BUG-000148070 - Elements missing geometry in output JSON after running the Export Subnetwork
  • BUG-000147993 - Overwriting the hosted feature service in Portal 10.9.1 created from a CSV utilizing Military Grid Reference System (MGRS) addresses is unsuccessful and crashes the service.
  • BUG-000147861 - Creating an association through an attribute rule fails with "unknown error" in Enterprise. Server incorrectly reports that the association already exists.
  • BUG-000147765 - Certification of ODBC 18 for SQL Server connections
  • BUG-000147630 - Multiple executions of ApplyEdits with the same edit payload following a timeout can result in a DBMS deadlock error.
  • BUG-000146998 - Restoring the row via Conflict Manager does not properly maintain the dirty area.
  • BUG-000146889 - FGDB fails on import associations when reaching commit threshold
  • BUG-000146789 - Export Subnetwork fails with the error message "Operation is only allowed by the owner of the version" when Default is 'Protected'
  • BUG-000146762 - Set-based implementation of UN::UpdateSubnetworkStatusByName()
  • BUG-000146752 - Relating a branch versioned point to a related table record in a child version does not display in the Version Changes window when the relationship class is attributed.
  • BUG-000146572 - Update or Trace subnetworks fail for specific subnetwork with Error 999999, Error: Unexpected Operation
  • BUG-000146391 - Performing move of single feature with LKE data taking over 4 minutes.
  • BUG-000146342 - The Utility Network service fails to start with the error message, "The dataset name is invalid" returned.
  • BUG-000145596 - The Antialiasing mode configured in ArcGIS Pro or in the Manager site is not honored in the ArcGIS Server REST endpoint.
  • BUG-000145357 - Propagation not working correctly for lines connected to the same terminal on a device with multiple terminals
  • BUG-000145322 - Update Subnetwork fails with 999999 "Arithmetic overflow error converting float to data type numeric."
  • BUG-000145060 - Provide a way to disable post processing in validate (marking subnetwork controllers as dirty)

    For more information regarding this issue please see Technical Article: Bug: Add an option to disable post build processing after validate

  • BUG-000145058 - Map service response does not have updated ETag after a layer's resources are updated, causing the GET requests to receive a cached response unless the browser cache is cleared.
  • BUG-000144988 - Editing a centerline that is a curve that is not associated with a route throws a 3D error
  • BUG-000144761 - Update subnetworks needs to densify line segments in order not to store CAD properties on the subnetline feature
  • BUG-000144700 - The error, 'insufficient permissions', can occur on reconcile if the service was published by a database user which does not have permissions to a Utility Network present in the same database by another database user schema.
  • BUG-000144666 - Long running Save Edits operation in branch version results in ArcGIS Pro error "Save Edits Failed".
  • BUG-000144593 - V3 Utility Networks regenerate Association Dirty Areas in incorrect locations
  • BUG-000144420 - Reconcile fails with collation conflict error when database collation is different than instance collation.
  • BUG-000144404 - Updates to M-values should not create DA
  • BUG-000144240 - Export Subnetwork taking a long time on specific utility network
  • BUG-000143940 - Validate Network Topology (async) does not include Success flag to statusUrl when "Success = true"
  • BUG-000143892 - Reconcile failed on v3 with (an expected field not found)
  • BUG-000143529 - Error occurs when running "service area analysis" tool: Error DBMS table not found Invalid object name 'sde.sessions_137833_5'
  • BUG-000143165 - Validate topology does not clean dirty areas created for errors features.
  • BUG-000142062 - Reconcile and Post should not be creating dirty areas for changes in the DEFAULT version
  • BUG-000141879 - Optimize the VersionManagementServer VersionResource for the default versions locking information
  • BUG-000141813 - AddTerminalConfiguration is sorting valid paths (Build algorithm bug)
  • BUG-000141793 - Branch version change owner (alter version) can cause cached versions to have incorrect information for new owners.
  • BUG-000141670 - Common Table Expressions (CTE) query not using the ancestor moment timestamp for branch requests, returning incorrect results.
  • BUG-000141477 - Do not acquire a shared lock on gdb_items during asynchronous validate topology and update subnetwork
  • BUG-000141458 - Add index hints to branch versioned queries which delete by gdb_branch_id
  • BUG-000141457 - Add index hints to the branch versioned statements used by the trim operation
  • BUG-000141456 - Connection not caching spatial index properties resulting in repetitive queries being executed
  • BUG-000141455 - Add index hints to branch versioned insert statements to ensure the appropriate access path for obtaining the active row
  • BUG-000141454 - Add index hints to the update statements executed by reconcile and post operation
  • BUG-000141365 - Map service export operation takes longer when the service has annotation layers
  • BUG-000141095 - Pro branch versioning editing workflows can lead to server side crashes when split is called on the feature service
  • BUG-000140825 - There is a performance decrease when the map services contain annotations in servers with newer versions than ArcGIS Server 10.3.1.
  • BUG-000140704 - REST - measureToGeometry doesn't return the intermediate route when the from and to routeID have the same routeID in Postmile
  • BUG-000140539 - STIntersects() queries do not use the spatial index
  • BUG-000140525 - Implement the Validate optimization, when tracing to dirty subnetworks. When a tier contains no subnetworks do not trace the tier, because nothing could be marked as dirty.
  • BUG-000140449 - Connections blocked by exclusive table lock on sde_process_information.
  • BUG-000140443 - Validate of content feature generates updates for all associations of the container feature
  • BUG-000140314 - Realigning an existing centerline fails with Error: Underlying DBMS error 'Conversion failed when converting from a character string to uniqueidentifier" due to routeID field type being a GUID.
  • BUG-000140214 - Post holding shared table lock on gdb_itemtypes for the duration of the post operation
  • BUG-000140107 - Feature services in specific scenario fail to render completely when publishing from PostgreSQL PostGIS and Oracle SDO_Geometry data.
  • BUG-000140030 - Improve performance for branch query with UUID log file table join.
  • BUG-000140013 - Dead lock can be encountered when multiple connections hold exclusive locks on the sde_process_information and sde_table_locks tables.
  • BUG-000139968 - Upgrade can create incorrect conditional index on GDB_Locks table.
  • BUG-000139833 - Deadlocking may on SDE_branches & SDE_branch_tables_modified tables during simultaneous reconcile and post operations.
  • BUG-000139379 - Conflict propagation incorrectly occurs in a specific scenario with Attributed Relationships and Branch Versioning.
  • BUG-000139299 - Editing Performance on Enabled Network Topo
  • BUG-000138999 - Extend object class cache to support controller datasets within the workspace
  • BUG-000138365 - Adding multiple associations should update the source/target features to trigger attribute rules (filegdb bug)
  • BUG-000138212 - Validate Topology fails for dirty areas with Subnetwork Errors, "Edit operation failed: ERROR".
  • BUG-000137729 - A hosted feature layer shared from ArcGIS Pro using ArcGIS Pro default datum transformation displays a shift in Portal Map Viewer when using Esri Basemaps as a background map.
  • BUG-000137359 - Reconciling changes in a branch version causes ArcGIS Pro to stop responding.
  • BUG-000137346 - Crash occurs when reconcile is executed while the intermediate table is not registered as versioned.
  • BUG-000137303 - Review error reporting via JSONResponse when an HR is returned in the VersionManagementServer
  • BUG-000137260 - Optimize reconcile when the majority of features have been edited
  • BUG-000137139 - Optimize UpdateAssociationInfo function by splitting the query to discover from/toglobalid associations
  • BUG-000136979 - Validate Network Topology incorrectly allocating large amounts of memory impacting server soc mem usage
  • BUG-000136930 - In a branch versioned service, sourcing from a PostgreSQL database, any interruption to the connection results into underlying DBMS error until service is restarted.
  • BUG-000136892 - When a -1 is returned to ArcGIS Pro the conflict resolution dialog is unable to properly present the conflicts
  • BUG-000136889 - After upgrading Enterprise Geodatabase 10.7.1 to 10.8.1 and running the query to get Next_RowID, the following error message is returned: Msg 8144, Level 16, State 2, Procedure DBO.i13_get_ids, Line 0 [Batch Start Line 0] Procedure or function i13_get_ids has too many arguments specified.
  • BUG-000136296 - Long running reconciles may block users from editing Default or reconciling other versions with Branch Versioning.
  • BUG-000136284 - Editing data which are registered as multibranch causes lock escalation and blocking scenarios in the geodatabases in the SQL Server.
  • BUG-000136107 - The Update Subnetwork tool fails and returns the error message, "ERROR 001400: The server took too long to answer. The client has timed out. (status code 28). Failed to execute (UpdateSubnetwork)."
  • BUG-000135328 - Reconcile fails on a branch version and returns the error message, "A row with this OID already exists."
  • BUG-000135117 - Updating the subnetwork on a geographic coordinate system (GCS) spatial reference utility network fails the second time for short lines.
  • BUG-000134954 - Reconciling multiple versions in the utility network using the Reconcile Versions tool crashes the ArcSOC.exe instance.
  • BUG-000134950 - Crash occurs when reconcile is executed while a related destination table was not registered as versioned
  • BUG-000134496 - Using the 'Reconcile Versions' tool and leaving the 'Abort if conflicts detected' parameter unchecked, the session is still aborting the reconcile.
  • BUG-000133978 - Unable to execute the 'Export Report to PDF' ArcPy function outside of the ArcGIS Pro environment.
  • BUG-000133698 - Enabling the topology with the 'Only generate errors' option does not clean the dirty areas of the error.
  • BUG-000133185 - The 'Validate Network Topology' tool fails, and returns the following error message, "Edit operation failed. ERROR:"
  • BUG-000132887 - The electric subnet lines and electric lines do not overlap when the UN is in a GCS of 'GDA2020'.
  • BUG-000132610 - Updating/overwriting a csv fails if the first 150 records are removed.
  • BUG-000130888 - The Register with Geodatabase tool fails when registering an empty feature class
  • BUG-000115504 - The ArcGIS Pro Append tool is very slow if the target feature class participates in a relationship class with messaging enabled.

Installing this patch on Windows


Installation Steps:


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.

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

    ArcGIS 10.8.1  
         ArcGIS Server ArcGIS-1081-S-UN8-Patch.msp
  2. Make sure you have write access to your ArcGIS installation location.
  3. Double-click ArcGIS-1081-S-UN8-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:

    msiexec.exe /p [location of Patch]\ArcGIS-1081-S-UN8-Patch.msp


Installing this patch on Linux


Installation Steps:


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.

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

    ArcGIS 10.8.1  
         ArcGIS Server ArcGIS-1081-S-UN8-Patch-linux.tar

  2. Make sure you have write access to your ArcGIS installation location, and that no one is using ArcGIS.
  3. Extract the specified tar file by typing:

    % tar -xvf ArcGIS-1081-S-UN8-Patch-linux.tar
  4. Start the installation by typing:

    % ./applypatch

    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.

Upgrade a geodatabase


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


import arcpy
arcpy.UpgradeGDB_management(Connection_File_Name_full_path, "PREREQUISITE_CHECK", "UPGRADE")


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:

"C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\scripts\propy.bat" C:\temp\
"C:\Program Files\ArcGIS\Server\framework\runtime\ArcGIS\bin\Python\envs\arcgispro-py3\python.exe" C:\temp\


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

source /<arcgis_server_installation_directory>/arcgis/server/framework/etc/arcenv


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


Uninstalling this patch on Windows


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.


Uninstalling this patch on Linux


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:


The script allows you to uninstall previously installed patches or hot fixes. Use the -s status flag to get the list of installed patches or hot fixes ordered by date. Use the -q flag to remove patches or hot fixes in reverse chronological order by date they were installed. Type removepatch -h for usage help.

Restart your ArcGIS services.


Patch Updates

Check the Patches and Service Packs page periodically for the availability of additional patches. New information about this patch will be posted here.


How to identify which ArcGIS products are installed

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.

Download ID:8072

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options