ArcGIS Enterprise on Red Hat Linux: Publishing issues when referencing data from enterprise geodatabase
Hello Enterprise community,
We are facing some publishing issues on one of our environments. In fact, this is our staging environment and we must get everything working before we deploy the production environment. We have a multi-machine base deployment architecture as shown below:
We have two machines in this environment and we installed all 4 components (portal, server, datastore, and web adaptors for portal and server) on each. We installed and created sites on the first machine, and we joined the portal and server components to existing sites from the first machine. The server and portal are federated and everything seems to work perfectly. We also updated our WebContext URL appropriately. However, we are having issues whenever we attempt to publish data from Enterprise Geodatabase. The database we are using is Oracle. We have also attempted to register a Microsoft SQL Server database, and still experienced the same issue.
We want to publish a Utility Network dataset, and we want to reference the enterprise geodatabase. We've tested several workflows to troubleshoot the publishing settings as follows:
| # | Workflow | Result |
| 1 | Upload CSV, and Shapefile and published as hosted feature layer | PASSED |
| 2 | Share as web map/web layer from File Geodatabase (Copy all feature) | PASSED |
| 3 | Share as web map/web layer from Oracle Enterprise Geodatabase (Copy all feature) | PASSED |
| 4 | Share as web map/web layer from Oracle Enterprise Geodatabase (Reference registered data) | FAILED |
| 5 | Share single layer as web layer from Oracle Enterprise Geodatabase (Reference registered data) | FAILED |
| 6 | Save Service definition file from Oracle Enterprise Geodatabase to publish on Server Manager (Reference registered data) | FAILED/INCONCLUSIVE |
For the failed sharing from Enterprise Geodatabase, the publishing job gets stuck on "Uploading service definition" for longer than usual before failing as shown below:
The log below was also generated from each failed attempt:
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:41 Status: InProgress StatusMessage: Successfully wrote sharing info file
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:41 Status: InProgress StatusMessage: Successfully wrote sharing connection file (Number of SDE Connections: 1)
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:41 Status: InProgress StatusMessage: Loading manifest
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:41 Status: InProgress StatusMessage: Creating thumbnail from map
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:41 Status: Pending StatusMessage: Sharing process started
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:42 Status: InProgress StatusMessage: Sharing process started
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:42 Status: InProgress StatusMessage: Loading manifest
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:42 Status: InProgress StatusMessage: Reading thumbnail from file
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:43 Status: InProgress StatusMessage: Publishing process started
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:43 Status: InProgress StatusMessage: Preparing data references and staging web layer
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:35:43 Status: InProgress StatusMessage: Loaded SDE Workspaces
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:06 Status: InProgress StatusMessage: Using ArcGIS Version 13.1 for staging (Source for version: GP Staging Parameters)
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:06 Status: InProgress StatusMessage: Stage Tool initialized
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:06 Status: InProgress StatusMessage: Preparing maps and layers for processing
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:09 Status: InProgress StatusMessage: Retrieving and processing fonts
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:10 Status: InProgress StatusMessage: Executing...
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:10 Status: InProgress StatusMessage: Start Time: Tuesday, December 12, 2023 9:36:09 AM
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:10 Status: InProgress StatusMessage: Succeeded at Tuesday, December 12, 2023 9:36:09 AM (Elapsed Time: 0.03 seconds)
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:13 Status: InProgress StatusMessage: Consolidate data
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:13 Status: InProgress StatusMessage: Staging map service
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:35 Status: InProgress StatusMessage: Compressing package into SD file
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:37 Status: InProgress StatusMessage: Staging successful
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:37 Status: InProgress StatusMessage: Uploading service definition
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:38 Status: InProgress StatusMessage: Publishing tool initialized
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 09:36:38 Status: InProgress StatusMessage: Publishing web layer (AGS)
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 10:07:41 Status: InProgress StatusMessage: Upload failed
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 10:07:43 Status: InProgress StatusMessage: Publishing tool execution failed
Map1 8 WebMapImageLayer ArcGIS Enterprise https://webserver.hostname.tld/server portaladmin 2023-12-12 10:07:45 Status: Failed ErrorMessage: Failed to publish web layer
I used FAILED/INCONCLUSIVE for the 6th test, because the service definition upload on Server Manager keeps uploading for hours with no fail/success result.
At this point we're stuck as to what next we need to check. Calling on everyone here to give us suggestions on what we can apply to be able to publish our Utility Network Data referencing registered data from enterprise geodatabase. Thanks you in anticipation.
Hi @MarceloMarques , thanks for your imput. We already configured the Oracle client, and we were able to register the Oracle database with the server and it validates successfully in both ArcGIS Pro and Server Manager. This is also one of the things ArcGIS Pro checks when you click Analyze and it will not even allow sharing until the data source is registered with the server.
So, like I said, we were able to click Share, and as seen in the logs, the publishing tool completed some steps while it failed to upload service definition and publish the layer. In the status pane, we can only see that it tool forever to upload service definition before eventually failing, and the logs is all we've got which is not providing enough information for diagnostics.
