Hosting Server Connectivity Issues Following ArcGIS Enterprise 11.2 Upgrade

We are encountering significant functionality problems with our Hosting Server after upgrading our HA Enterprise environment from version 11.1 to 11.2 in mid-November. These issues appear to stem from connectivity errors between the hosting server and our Portal machines. This disruption has severely impacted our operations, specifically causing Workflow Manager to become completely inoperable and hosted services within Portal to consistently return 405 errors when attempting to load feature layers.

Portal logs are registering errors such as:

- Failed to start the Offline Packaging service in the hosting server with URL 'https://*exampleservername.domain.com*:6443/arcgis/admin/services/Utilities/OfflinePackaging.GPServer'. {1} The server at 'https://*exampleservername.domain.com*:6443/arcgis/admin/services/Utilities/OfflinePackaging.GPServer/start' returned an error. Service failed to start

Despite the error message, upon inspecting the service status directly on the hosting server, the Offline Packaging service is shown as ‘STARTED’. We have attempted to resolve this by stopping and restarting the service multiple times, even accessing the service page with administrative tokens, but the problem persists.

Another error message appearing in the logs is:

- Using defaults for some properties of the self resource (ex: supportsSceneServices). The hosting server may not be reachable.

We have verified that all necessary ports are open and correctly configured on the ArcGIS Server machine. Before the 11.2 upgrade, this setup was fully functional, indicating that the issue was introduced during or after the upgrade process. Furthermore, we confirmed that the problematic Portal patch present in version 11.1 was not installed on our Portal machines prior to the upgrade, ruling out this patch as a potential cause. Our environment includes several older federated server sites that are running smoothly without similar issues, suggesting the problem is isolated to the hosting server site.

In an attempt to rectify the situation, we deployed a new ArcGIS server, also version 11.2, intending to add it to the existing hosting server site and potentially replace the original, malfunctioning server. However, we encountered an unexpected “license does not match error”. This occurred even though we used the identical 11.2 license files that were originally used to license the existing server. This licensing discrepancy is currently our strongest lead in understanding the root cause of these hosting server problems, suggesting a potential backend authorization issue on the original server. We have exhausted numerous troubleshooting steps suggested by ESRI support agents, making this license error a critical point of investigation.

We are continuing to investigate this licensing issue and its potential connection to the hosting server connectivity problems. Any insights or suggestions from the community would be greatly appreciated as we strive to restore full functionality to our ArcGIS Enterprise environment.