ArcGIS Server Branch Versioning Licensing Patch

Esri announces the ArcGIS Server Branch Versioning Licensing Patch.  This patch updates the licensing for creating, editing, and managing a branch version.  After installing this patch users will be able to create, delete, alter, and edit within a branch version without the need for the Advanced Editing User Type Extension (UTE) when working with simple data.  The Advanced Editing UTE will still be required when working with more advanced data and capabilities in branch versions such as utility networks, trace networks, parcel fabrics, geodatabase topologies, dimensions, and batch attribute rules. This patch also resolves BUG-000178964, a defect that impacts editing with feature services and contingent values on web clients, apps and maps SDK clients (this defect is not related to licensing). Esri recommends that customers utilizing branch versioning with ArcGIS Server 11.3 and 11.5 apply this patch.  This patch deals specifically with the issues listed below under Issues addressed with this patch.

For additional information on licensing. refer to the ArcGIS Enterprise Functionality Matrix document.

Note about the Web Editor application: Even after installing this patch, the Web Editor application will still require the Advanced Editing User Type Extension (UTE) when working with simple data. An additional patch, for Portal for ArcGIS, is forthcoming to remove this licensing check from the Web Editor application.

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-000178964 - Remove "hasContingentValuesDefinition": true property on layer resource for references feature services. (11.5 only)
• 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.

To avoid conflicts the 11.3 version also includes:

• BUG-000176107 - Network Dataset enters in a state of failure after performing an edit.
• 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-000158284 - Hosted tables fail to synchronize in distributed collaborations between ArcGIS Enterprise and ArcGIS Online.

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