ArcGIS Datastore Service Issues

Question

Hello esri community,

Just about everyday I get a phone call from the Application user/product builder that they are unable to publish new products and cannot validate the Datastore.

I log into the Database server and run the describedatastore.bat tool and receive this error:

Error encountered: No valid connection to ArcGIS Data Store configuration store established.
Caused by: Connection to localhost:9876 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.

The only workaround has been to manually stop and start the ArcGIS Datastore service or reboot the entire server. Has anyone encountered this? Any luck with a permanent solution?

Things I have done:

1. Verified the service account running the ArcGIS Datastore server has full rights to

C:\arcgisdatastore
      C:\Program Files\ArcGIS\DataStore
2. Verified Host Based Security System/firewall is not blocking a connection

RClaveroM · Answer

Hello @RichardValera,

Not so long ago someone posted this same error message and some suggestions were provided. Checking them I see they are pretty similar from @RyanUthoff's ones. Still, I decided to "link" to that post since someone might benefit from it.

ryanuthoff · Answer

That sounds like an issue with the underlying PostgreSQL DB that the ArcGIS Data Store runs off of. I've received that message immediately after restarting the ArcGIS Data Store, when all the underlying services are still starting up. But it goes away after a couple minutes once everything is fully online.

There are a couple logs you can check to see if there is any useful information.

C:\arcgisdatastore\logs\machine name\server - These are log files specific to Esri's ArcGIS Data Store service.

C:\arcgisdatastore\logs\machine name\database - These are log files specific to the underlying PostgreSQL DB.

I think searching through those logs is a good first step. If you know a specific time when users start experiencing that error, that would be a good timeframe to check in the logs. You might need to start there and work your way back to when you last knew it was working.