Patches and updates

ArcGIS GeoEvent Server 10.9.1 Patch 4 (Windows | Linux)

Published: April 13, 2023


ArcGIS GeoEvent Server 10.9.1 Patch 4 is a general maintenance patch that addresses several issues, including persistent session log-in prompts on the site tab, the inability to export data from the spatiotemporal data store to Amazon S3, data retention where clauses not being honored, a condition where multiple GeoTagger processors causes gateway failure, and several resource and logging adjustments to the WebSocket transport. Esri recommends that all customers using ArcGIS GeoEvent Server 10.9.1 apply this patch. 

This cumulative patch incorporates all previously released ArcGIS GeoEvent Server 10.9.1 Patches and Hot Fixes. See the Enhancements and Issues Addressed section below for a complete list of updates.

  • ArcGIS GeoEvent Server 10.9.1 must be installed before you can install this patch.
  • You must clear the browser cache after this patch is installed to properly load the updated GeoEvent Manager User Interface.
  • It is recommended to create a backup of your GeoEvent Server configuration prior to installation of the patch.
  • ArcGIS GeoEvent Server Patches cannot be uninstalled. To roll back a patch requires a fresh install of GeoEvent Server.

Enhancements and Issues addressed with this patch

  • BUG-000153272 - After updating to ArcGIS Server 10.9.1 Security 2022 Update 2 Patch, the ArcGIS GeoEvent Server Manager Site tab log-in session persistently expires.
  • BUG-000154054 - Spatiotemporal data store export to Amazon S3 Bucket fails with Amazon Service Exception.
  • BUG-000145527 - ArcGIS GeoEvent Server exposes a used WebServer name/version on an invalid request.
  • BUG-000142170 - Configuring multiple GeoTagger Processors on a single GeoEvent Service input breaks the gateway service.
  • BUG-000133766 - When an ArcGIS GeoEvent Server input in a client disconnects and reconnects due to WebSocket inactivity, the GeoEvent Server process leaks thread resources and RAM.
  • BUG-000133872 - When an external server’s WebSocket disconnects, the ArcGIS GeoEvent Server input logs an error but the visual indicates the input is still running.
  • BUG-000154271 - Enter evaluations appearing twice on first observed event record using the GeoTagger processor.
  • BUG-000154399 - Stream service geofence synchronization fails with 1=1 WHERE clause.
  • BUG-000154397 - Stream service WHERE clause not honored for geofence synchronization.
  • BUG-000154405 - Geofence synchronization WHERE clause is ignored when start and end time extent properties are set.
  • BUG-000154406 - The Choice element does not honor enter/exit spatial conditions.

To avoid conflicts with previous releases and patches, the following issues are also addressed with this patch:

  • BUG-000150552: ArcGIS GeoEvent Server does not honor the 'Maximum Feature Age' parameter in a stream service's store latest capability referencing a non-hosted feature service.
  • BUG-000148632: When rebooting a Windows Server machine with ArcGIS GeoEvent Server installed, there is a chance of ArcGIS GeoEvent Manager becoming inaccessible.
  • BUG-000145347: Update log4j to address security vulnerabilities.
  • BUG-000129110: Enterprise server connections without credentials revert to an unusable state when GeoEvent Server is restarted.
  • BUG-000144488: Following a reboot GeoEvent Gateway will periodically fail to restart in an operational state.
  • BUG-000145348: Update GeoEvent Server to replace unpatched Log4j libraries.
  • BUG-000145938: Expressions with attribute names including special metacharacters are no longer supported in the 10.9 / 10.9.1 Field Mapper.
  • BUG-000145944: Event records with one or more null values are no longer supported by the 10.9 / 10.9.1 stream service output.
  • BUG-000146495: Lack of query parameter throws null pointer exception.
  • BUG-000146611: Field Enricher query fails for integer type values in where clause. 
  • BUG-000146645: GeoEvent Server loses connection with the GeoEvent Gateway causing GeoEvent Services and Outputs to stop functioning correctly.
  • BUG-000147023: GeoEvent restart stability with custom components.

Installing this patch on Windows

Note: Any changes made to the configuration or property files in GeoEvent/etc or GeoEvent/gateway/etc will need to be reapplied to the new files after the patch is installed. The patch will overwrite the files in these locations.

Step 1: Login with an Administrator Windows account.

Step 2: Download the patch to a location other than your ArcGIS installation location.

            Patch File: GeoEvent_10_9_1_Patch4.msp

            Checksum (SHA256): 4561b69ea19f84bc3912c996174aad723153933f095c22b3238f2d0479a99649                 

Step 3: Double-click GeoEvent_10_9_1_Patch4.msp to start the install.

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>\GeoEvent_10_9_1_Patch4.msp

Step 4: Open the GeoEvent Manager to ensure your inputs, outputs, and GeoEvent Services have been started. If they are not, restart them in the GeoEvent Manager.

Installing this patch on Linux

Note: Any changes made to the configuration or property files in GeoEvent/etc or GeoEvent/gateway/etc will need to be reapplied to the new files after the patch is installed. The patch will overwrite the files in these locations.

Step 1: Log in as the user that installed ArcGIS Server. 

      Note: For the Amazon AMI this is the user arcgis.

Step 2: Download the patch to a location other than your ArcGIS installation location.

                Patch File: GeoEvent-10.9.1-Patch4.tar.gz

                Checksum (SHA256): 093c29d80c8353dc8daf4880d442a599efc1a829a621f633527e0a80dd80fd20

Step 3: Extract the package:     % tar -xzvf GeoEvent-10.9.1-Patch4.tar.gz

Step 4: Stop the GeoEvent daemon services.

Step 5: Start the installation and wait for it to complete:     % ./GeoEvent/

Step 6: Delete the contents of the GeoEvent Server data folder.     % rm -rf /GeoEvent/data/*

Step 7: After the setup is complete, restart the GeoEvent daemon services.

Step 8: Open the GeoEvent Manager to ensure your inputs, outputs, and GeoEvent Services have been started. If they have not started, restart them in the GeoEvent Manager.

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 products, hot fixes, and patches installed on your local machine.

To determine which version of ArcGIS GeoEvent Server is installed append /version.txt to the GeoEvent Manager URL. For example:

  • https://localhost:6143/geoevent/manager/version.txt

Download ID: 8100

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options