ArcGIS Server Reconcile and Post Consistency Patch

Esri announces the ArcGIS Server Reconcile and Post Consistency Patch. This patch addresses a defect related to reconcile and post. A status tracking defect allowed a user to Post a version to default, after a Reconcile operation but after an additional operation (Validate Network Topology) has been run, resulting in incorrect data being posted to default. After installing this patch, run Disable Network Topology and Enable Network Topology to ensure a consistent state. Esri recommends that customers using ArcGIS Enterprise 11.5, 11.3 and 11.1 for reconcile and post operations apply this patch. 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-000183319 - Post must get the can_post property from the write lock.

To avoid conflicts the 11.5 version also addresses:

• 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-000179322 - Evaluate calls differences on unmodified classes.
• BUG-000178964 - Remove "hasContingentValuesDefinition": true property on layer resource for references 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-000177471 - Optimize generation of the default replica name in the createReplica operation.
• 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-000176825 - Evaluate operation is adding objectids to the selection set one at a time.
• 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-000169677 - In the ArcGIS REST Services Directory interface, a query on a query layer with SDO_Geometry fails when using an object IDs filter.

To avoid conflicts the 11.3 version also addresses:

• 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-000179884 - There is a security vulnerability in ArcGIS Server Feature Services.
• BUG-000179851 - The Update Subnetwork operation fails and returns the 'subnetwork is not dirty' message when there is an active dirty controller and a 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-000179206 - Performance degradation in Trace with subnetworks containing large cardinalities of connectivity associations with nonspatial objects.
• BUG-000178701 - The full extent validation checks if the objects are dirty before exiting early.
• 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-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-000176927 - Inefficient branch versioning queries with log files and predicate filters are impacting performance and scalability.
• BUG-000176902 - Optimize the population of the logfile table by utilizing an array insert instead of single-row writes.
• 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-000176744 - Avoid branch versioning reconcile serialization lock errors.
• 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-000174795 - The conflicts operation in the REST endpoint retrieves the default representation of a feature using an incorrect moment.
• 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-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-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-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-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-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-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-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-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-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 validate network topology.
• BUG-000166688 - Running Migrate ObjectID to 64 bit can recreate branch versioned class indexes incorrectly.
• 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-000166025 - Improve the Enable and Validate network topology by selecting the required fields.
• 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-000164368 - Remove the binding used for pagination queries offset and next values.
• BUG-000163812 - Downstream tracing is forcing the user to choose Allow Indeterminate Flow when it shouldn't be necessary
• BUG-000160615 - The ArcGIS Utility Network topology for validation in the ArcGIS REST APIs requires validateArea to be input, which overrides all specified objects in validationSet.
• 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.
• BUG-000141682 - Unexpected association conflicts occur in named versions after reconciling and posting with DEFAULT following topology validation, and the conflicts appear in the UN_<>_ASSOCIATIONS table and the Conflict Manager.
• BUG-000137206 - The Aggregate Geometry trace results are not honoring the mid-span end when using a filter function barrier.

To avoid conflicts the 11.1 version also addresses:

• 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-000179851 - The Update Subnetwork operation fails and returns the 'subnetwork is not dirty' message when there is an active dirty controller and a 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-000179749 - The Update Subnetwork tool fails and returns Error 999999.
• BUG-000179573 - LRS dataset takes several days to complete the ExportNetwork query from the ArcGIS Server REST endpoint.
• 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-000179206 - Performance degradation in Trace with subnetworks containing large cardinalities of connectivity associations with nonspatial objects.
• BUG-000178701 - The full extent validation checks if the objects are dirty before exiting early.
• 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-000177759 - Perform association expansion on a selected object in validate by selection set.
• BUG-000176927 - Inefficient branch versioning queries with log files and predicate filters are impacting performance and scalability.
• BUG-000176902 - Optimize the population of the logfile table by utilizing an array insert instead of single-row writes.
• 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-000176712 - Propagation of Phase Energized attribute is incorrect when 3 phase lines merge in ArcGIS Pro.
• BUG-000176032 - Editing an attribute value fails with the error "Features that are utility network subnetwork controllers do not support edits to asset group or asset type attributes".
• BUG-000175933 - Performance issues in APR tools when editing in a geodatabase with multiple feature datasets.
• BUG-000175663 - ArcSOC memory footprints are getting too large.
• BUG-000175217 - queryAttachments: Gives incorrect response after applyEdits async=true on branch versioned data
• BUG-000175099 - Utility Network users are experiencing large SOC memory footprint, causing resource contention.
• BUG-000174354 - Reconciling by attribute with a branch versioned feature service does not detect conflicts even when conflicting features exist.
• BUG-000174085 - Experiencing a large number of "Association Status" UN errors when running errors only topology
• 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-000173853 - Running the Apply Event Behaviors tool on the linear referencing system (LRS) service with time enabled and symbology added in ArcGIS Pro causes the process to fail.
• BUG-000173446 - Failure to query an unregistered table when the objectIDField values are not set.
• BUG-000173394 - Unable to reconcile/post branch versioned data that contains a topology after upgrading enterprise geodatabase in PostgreSQL
• BUG-000173367 - Rebind the pipe_name variable on each execution when returning rowids to its appropriate pipe
• 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-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-000171261 - After using the Reverse tool, the Reassign tool returns the following error message, "The input measure will result in a non-monotonic route."
• BUG-000171206 - The Realign tool fails and returns the error message, "There was an error while processing the edits on the server."
• 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-000170566 - When running the Apply Event Behaviors tool with the Event Realign rule set to Cover, the FromDates appear to be incorrectly set to the date of the realignment.
• 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-000169178 - Export Subnetwork and Trace JSON output do not properly serialize polygon curves.
• 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-000168781 - Fix memory leak when executing SQL using OCI.
• 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-000168091 - Realign Route fails in APR-UN configuration when centerline isn't split at realign location in advance
• BUG-000168090 - Event Replacement: Non-Spanning Line Events are not Retiring and Replacing on a Line Network if the replacement is not the full length of the line
• BUG-000168089 - LRS routes in a GCS are not automatically densified if centerline is in 2D
• BUG-000168080 - Subnetworks are not being concatenated when a feature's terminal path is set to None.
• BUG-000168079 - Multiple terminal devices which have multiple subnetworks fail to get a concatenated subnetwork name.
• BUG-000167975 - The Validate Network Topology tool fails with a General Function Failure and returns an "Invalid network element id" error.
• BUG-000167887 - The GetFeature operation on a WFS service referencing data from a SQL Server Enterprise Geodatabase fails to return any results unless the count parameter is included in the request after installing the ArcGIS Server Branch Versioning Data Consistency Patch.
• BUG-000167572 - Dirty areas with empty geometries are generated after validating a network topology.
• BUG-000166934 - SDESPATIALINDEXHINT is no longer working for paginated queries
• BUG-000166704 - Serialize StopEditing REST Request to ensure a single writer.
• BUG-000166701 - Upgrading a geodatabase should resolve branch versioning metadata and data inconsistencies.
• BUG-000166688 - Running Migrate ObjectID to 64 bit can recreate branch versioned class indexes incorrectly.
• BUG-000166613 - The Export Map operation fails at the ArcGIS Server rest API when listing a sublayer before a group layer in the dynamic layers parameter.
• BUG-000166025 - Improve the Enable and Validate network topology by selecting the required fields.
• BUG-000165693 - The subnetwork does not get marked as dirty when opening or closing a medium voltage switch.
• BUG-000165688 - Enabling topology for UN data coming from the SAP HANA database causes ArcGIS Pro to crash.
• BUG-000165684 - Check for IDatasetImpl in FeatureServer.
• BUG-000165556 - Concurrent update subnetwork processing deadlocks return the error message "Session Application lock in progress - operation not allowed".
• BUG-000165151 - Feature services accessing SAP HANA datastores allow multiple applyEdit operation calls on the same version in parallel.
• BUG-000164817 - Publishing a referenced map service containing data from two different database connections fails and returns the error, "Failed to create the service.: Updating the server connection string for layer failed."
• BUG-000164497 - The map service layer REST resource reports False for the supportsPagination flag for BigQuery datasets.
• BUG-000164368 - Remove the binding used for pagination queries offset and next values.
• BUG-000164231 - Low performance with utility network maps in all JavaScript 4.x applications.
• BUG-000163812 - Downstream tracing is forcing the user to choose Allow Indeterminate Flow when it shouldn't be necessary
• BUG-000163235 - Slow performance when running ArcGIS Utility Network 'Upstream trace'.
• BUG-000163163 - When a calibration point is added to the end of the route with the same measure and a different date, the calibrate event behaviors do not time slice the impacted point events.
• BUG-000163037 - The Generate Intersections tool takes an exceptionally long time to run on two routes.
• BUG-000163003 - Using specific queryAttributeSet queries from ArcGIS REST API on route IDs with multipart geometries causes the linear referencing service to crash or the returned events to be incorrect based on the query.
• BUG-000162973 - Remove the option recompile from branch versioned query statements.
• BUG-000162691 - The workflow creates empty geometries without dirty areas.
• BUG-000162567 - Creating routes causes ArcGIS Pro to crash.
• BUG-000162360 - Performing an isolation trace with a directional device near the isolated section returns incorrect trace results.
• BUG-000162289 - Branch versioning query performance.
• BUG-000162011 - Running a trace network trace in ArcGIS Pro with the result type set to Aggregate Geometry does not return partial features when a barrier is not placed in the same line segment as the starting point.
• BUG-000161976 - When using the Split Into COGO Lines tool on a feature service containing a parcel fabric, the Created By Record field of new parcel features is not populated.
• BUG-000161847 - The measureToGeometry endpoint returns incorrect geometry for certain branched and gapped routes in a postmile network.
• BUG-000161846 - The measureToGeometry endpoint crashes when encountering a branched postmile route.
• BUG-000161813 - Honor directional devices when calculating flow direction in loops.
• BUG-000161112 - Reduce the memory footprint of ArcSOC by not cloning class definition.
• BUG-000161000 - Incorrect line numbers are reported for invalid Arcade expressions.
• BUG-000160615 - The ArcGIS Utility Network topology for validation in the ArcGIS REST APIs requires validateArea to be input, which overrides all specified objects in validationSet.
• BUG-000160150 - Allow applyEdits with UseObjectIDsForAdds to accept adds without object ids.
• BUG-000160111 - Updates to fields being referenced in a layer definition query for a sync replica lead to two inserts of the same OBJECTID in the delta geodatabase and an error message, "UNIQUE constraint failed: T_6_Updates.OBJECTID" is returned during sync download.
• BUG-000160068 - The batch calculation evaluation does not reset Validation Status to validationRequired.
• BUG-000160032 - The applyEdits operation with branch versioning updates inserted rows impacting the performance and throughput of the request.
• 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-000158886 - In UN Branch Versioning, the branch versions appear under the user's name. The versions are neither created by the user nor assigned to them knowingly by any other user, and appear as 'private' rather than 'public'.
• BUG-000158867 - Allow extracting a subset of a full model utility network for tracing in the field.
• BUG-000158727 - Function barriers are leading to unexpected trace results when applied to junction objects with terminals and Use Local Values = False
• BUG-000158635 - ArcGIS Arcade error, unexpected null value when editing feature classes consisting of calculation attribute rules with the intersects function in ArcGIS Pro 3.1.x.
• BUG-000158628 - A downstream trace runs indefinitely in an infinite loop when specifying a target tier in some scenarios.
• BUG-000158523 - The Append Routes tool results in a logged error, "Partially matched centerlines found." when the centerline and route appear to have a complete match.
• BUG-000158474 - Feature service with utility network and stand-alone topology fails to reconcile, and the following error message is returned, "ERROR: code: 500, Error in handling operation reconcile, Internal server error".
• BUG-000157992 - Phase propagation loses phase in certain 'loop' situations.
• 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-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-000157087 - Saving a versioned edit session should update all previously saved edits to the new version moment.
• BUG-000156886 - Non-LRS edits to the calibration point features generates records in the LRS Edit Log.
• BUG-000156763 - Post must obtain the current list of modified tables for a version prior to the posting operation.
• BUG-000156756 - The Apply Event Behaviors tool produces incorrect results on point event layers.
• BUG-000156421 - Provide a more informative error message when failures are encountered with a large number of starting points when running the Trace tool.
• BUG-000156349 - The reconcile process may timeout while an operation is being completed on Default.
• BUG-000156042 - Passing privileges on a feature class in SAP HANA through database roles does not work in ArcGIS Pro.
• BUG-000155836 - Support LRS operations for GCS data with vertices that are too sparsely spaced
• BUG-000155422 - Running the Generate Routes tool using the Postmile network changes the Odometer values in a linear referencing system (LRS) Dataset (published and branch versioned).
• 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-000155261 - The Conflict Manager fails to display conflicts when a subtype group layer is published as a referenced feature service.
• BUG-000155010 - STArea() value is showing different results based on viewing representation (for example, all records view versus show selected records view).
• 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-000152165 - Allow service-based writing/updating of associations in a utility network database, without the utility network rule-validation of these association updates.
• BUG-000152139 - ArcGIS Enterprise Data Store's update password process breaks layers that are referencing a geodatabase.
• 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-000148398 - Poor asynchronous validate performance at the full extent in the Default version.
• BUG-000148077 - The downstream trace across tiers does not reach the target tier in some cases. (#8927) /
• BUG-000147333 - Unable to export the data for the hosted feature layer view in Portal for ArcGIS 10.9.1 when some fields are hidden.
• BUG-000141682 - Unexpected association conflicts occur in named versions after reconciling and posting with DEFAULT following topology validation, and the conflicts appear in the UN_<>_ASSOCIATIONS table and the Conflict Manager.
• BUG-000137206 - The Aggregate Geometry trace results are not honoring the mid-span end when using a filter function barrier.

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-<Version>-S-RPC-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:

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