BUG-000184815: Raster store failures in ArcGIS Enterprise 12.0 on Kubernetes due to incorrect Azure endpoint key configuration

Description

In ArcGIS Enterprise 12.0 on Kubernetes, a bug in ArcGIS Enterprise Manager causes Azure-based raster stores to be registered with an incorrect storage account endpoint key. 

This issue affects all Azure Blob Storage raster stores registered in ArcGIS Enterprise 12.0 on Kubernetes, regardless of authentication type. Raster stores registered in 11.5 or earlier are not affected. 

As a result, users may experience: 

• Raster analytics jobs failing
• Image service publishing failures
• Storage authentication inconsistencies 

Cause

Due to a bug in ArcGIS Enterprise Manager, the Azure storage account endpoint is using an incorrect key: 

"accountEndpointUrl" 

instead of the required key: 

"accountEndpoint" 

Since ArcGIS Enterprise components expect accountEndpoint, this mismatch leads to failures during raster processing and publishing workflows. 

Workaround

Users can either upgrade to ArcGIS Enterprise 12.1 or apply the latest patch (Update 4) and re-register the raster store using ArcGIS Enterprise Manager with the correct configuration. 

Step 1: Apply Update 4 

Follow the Apply updates documentation to install ArcGIS Enterprise 12.0 Update 4. 

Note:
Re-registering the raster store without applying the update will result in the issue recurring. 

Step 2: Identify impacted raster stores 

1. Sign in to ArcGIS Enterprise Manager.
2. Navigate to Data Stores > Raster Stores.
3. Review raster stores configured with Cloud service - Azure Blob.

All raster stores registered in ArcGIS Enterprise 12.0 on Kubernetes should be considered impacted, especially if: 

• They were newly registered in 12.0
• Raster analytics job failures or publishing failures are observed 

Step 3: Unregister the existing raster store 

Ensure the following items before proceeding: 

• No raster analytics jobs are running
• No active imagery layer publishing operations are in progress
• Note the raster store name, it will be needed when re-registering in the next step.
• If a folder (optional) property was used during registration, note the folder name, it will be required when re-registering. You can verify the folder name before unregistering: 
• Follow the Update raster store properties documentation until step 3.
• Locate the Folder (optional) property.

Follow the Unregister a raster store documentation to unregister the impacted raster store.

Step 4: Re-register the raster store 

Follow the Add a raster store documentation to re-register the raster store using the same configuration as before.

Important:
Use the exact same raster store name and folder (optional) noted in Step 3. This ensures existing published services continue to function and references to the raster store are not broken.

Verification 

After re-registering: 

• Run a raster analytics job successfully
• Publish an image service successfully