Hi all,
Posting here as multiple ESRI agents have been stumped by this issue we're having in our environment. In mid-Nov we proceeded with an upgrade of our HA Enterprise environment from 11.1 to 11.2, and have since seen major functionality problems, specifically with our Hosting server. It seems to be having connectivity errors with our Portal machines. Due to this, Workflow Manager has become completely broken, and hosted services in Portal come up with repeated 405 errors when trying to load feature layers. Errors seen in the Portal logs include:
- 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
^When checking the service status on the server, the service is already in the 'STARTED' state, and we have stopped and restarted it multiple times. Even loading the page through an admin token we are still able to perform these actions.
- Using defaults for some properties of the self resource (ex: supportsSceneServices). The hosting server may not be reachable.
All necessary ports are open on the ArcGIS Server machine, which was perfectly functional before the upgrade to 11.2. In addition, the defective Portal patch in 11.1 was not installed on the Portal machines prior to the upgrade, so they shouldn't be an issue (hopefully) since we have multiple older federated server sites that have been running without any problems. It seems to be isolated to the hosting server site itself. Interestingly we stood up a brand new 11.2 ArcGIS server to add to the existing hosting server site in the hopes of removing the old server that wasn't working, only to be met with a "license does not match error". The new server site was licensed with the EXACT same 11.2 license files that were used to license the original server, so it seems like something may not be authorized properly on the backend of the old server. This is the only lead we've had so far as to a potential cause for this, since we've exhausted pretty much every other suggested troubleshooting step from ESRI. Thanks in advance