We recently upgraded our standalone ArcGIS Server from 11.3 to 11.5 (along with PostgreSQL 15.5 to 16.8) and noted a failure in one of our publishing workflows. We've isolated the issue to an in-map join between a feature class sourced to a PostgreSQL Enterprise Geodatabase and a table sourced to an Oracle Enterprise Geodatabase and attempting to publish as a map service.
We were able to duplicate this issue in a separate server running ArcGIS Server 11.5 and were able to also confirm that functionality existed in 11.3. We can successfully publish map services with data from either registered data store and we are able to publish map services with joins, so long as both sources are from the same data store. We've attempted the following:
- Created a new .aprx with just the relevant layers.
- Dropped and recreated both .sde connection files and registered data stores.
- Utilized connections to the adjacent Postgres database as 'localhost' or as an FQDN.
- Dropped and recreated Server's dsconnections.lst configurations.
- Created a new Postgres EGDB.
- Attempted the workflow while running ArcGIS Pro as an administrator.
The specific Server error logs read:
SwizzleService failed.
DoAfterSDExtraction failed.
CreateServiceWrapper failed.
Failed to create the service. Updating the server connection string for layer xyz_xyz failed. Attempted connection string was SERVER=localhost;INSTANCE="DSID=###-####-###-###";DBCLIENT=postgresql;DB_CONNECTION_PROPERTIES=localhost;DATABASE=postgres_database;VERSION=sde.DEFAULT;AUTHENTICATION_MODE=DBMS. Table name is postgres_database.user.TABLENAME_FC. Please verify the data exists on the server.
Error executing tool. PublishServiceDefinition Job ID: ###### : ERROR 001487: Failed to update the published service with the server-side data location. Please see the server's log for more details. ERROR 001369: Failed to create the service. Failed to execute (Publish Service Definition).
The machines tested run Windows Server 2019 & 2022 Datacenter, IIS Web Adaptor, and are alongside a PostgreSQL 16.8 EGDB. We are working in Oracle 19c EGDBs in an on-prem Oracle RAC. All network traffic within a WAN. All machines are using ArcGIS Pro 3.5.6. These instances of Server are not federated with any Portal. All relevant patches have been installed.
