Following an upgrade of our HA Enterprise environment from version 11.1 to 11.2 in mid-November, we have encountered significant operational challenges, primarily centered around our hosting server. This critical component appears to be experiencing persistent connectivity problems with our Portal machines, leading to disruptions across multiple services.
The immediate impact has been the complete breakdown of Workflow Manager functionality. Furthermore, hosted services within Portal are now throwing repeated 405 errors whenever attempts are made to load feature layers. Our investigation into the Portal logs has revealed error messages 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”
Interestingly, while the logs indicate a failure to start, manual checks on the server itself show the service in a ‘STARTED’ state. Restarting the service through admin tokens also yields no resolution to the underlying issue.
Another error message observed in the logs is:
“Using defaults for some properties of the self resource (ex: supportsSceneServices). The hosting server may not be reachable.”
This further suggests a fundamental problem with the hosting server’s ability to communicate effectively within the ArcGIS Enterprise environment.
Despite these errors, we have verified that all necessary ports remain open on the ArcGIS Server machine. Prior to the 11.2 upgrade, the system was functioning without any network-related issues. We also confirmed that the known defective Portal patch from 11.1 was not applied to our Portal machines before the upgrade, eliminating it as a potential cause. This issue seems isolated specifically to the hosting server site, as our older federated server sites continue to operate without any comparable problems.
In an attempt to rectify the situation, we deployed a brand new ArcGIS Server 11.2 instance with the intention of adding it to the existing hosting server site and retiring the potentially problematic older server. However, this attempt was blocked by an unexpected “license does not match error”. This error is particularly perplexing as the new server was licensed using the exact same 11.2 license files that were used to license the original server. This licensing discrepancy is currently our strongest lead, suggesting a possible authorization problem on the backend of the original hosting server.
We have exhausted numerous troubleshooting steps suggested by ESRI support, but the core issue persists. We are seeking further insights or suggestions from the community to resolve these persistent connectivity issues with our hosting server and restore full functionality to our ArcGIS Enterprise deployment.
