Hello Laurence
I am experiencing the same FATAL error but after Federation and i can ressolve it. However i have some "under the bonnet" questions i am hoping someone at Esri could asisst with?
I have ArcGIS Server ( one site joined to two virtual machines joined, active\active high availability) and the site has one registered relational (managed) data store, residing on a third virtual machine. In addition, the ArcGIS Server is federated to Portal. Data Store, ArcGIS Server and Portal have the same CA root certificate and intermediate certificate assigned as trusted. One domain service account with full control permissions has been setup across all virtual machines and Portal and GIS Server rest end points are reachable from within each of these machines.
I unfederated ArcGIS Server from Portal and validated the data stores in AGS Manager and the data stores validated fine (green tick box, no fatal log errors). When i federate ArcGIS Server to Portal again and then re-validate the data stores in AGS Manager, i get a similar fatal error as Joel
Type=warning, code =”110787” source “Data Store” process = “21232” thread = “1” methodName = “” machine “<machine name>.<domain>” user= “” elapse = “” requestID = “” > Failed to create index on ‘{0}’ org.postgres.util.PSQLException: FATAL : no pg_hba.config entry for host “XXX.X.X.1”, user “hsu_XaXaX”, database “db_AbAbA”, SSL off </msge>
I can run the allowconnection.bat and the fatal error no longer is logged and the data stores are validated ( green tick box) in AGS Manager and the data store log files are all ok.
I repeate the above again. The second time, the fatal error had a different host, user and database parameters
I would like to understand
a) when does the connection to the managed\relational database get set? I thougth it was at the initial data store configuration? Do we have to manually set data connections to an existing data store after Federation?
b) By what script\mechanism\process is the different IPs, users and database parameters being created?
c) can these IPs, users and database parameters be static\never change?
d) is this accepted\designed behaviour by Enterprise?
Any help and insight is greatly appreciated
Thanks Ed