Latest Contributions by SuryaSawant

Thank you Jonathan. I switched from using ArcGIS Enterprise Builder to individual component installation.  If time permits I will try your suggestion and update.   ... View more

Hello Noah, Thank you for your suggestions. We have resolved the issue.  It turned out that even after disabling the antivirus on Spatiotemporal Big Datastore Server machine the IP and port of ArcGIS Server and GeoAnalytics server was blocked. Removing antivirus and allowing ports through Windows firewall resolved the Q2 (i.e. Unable to insert data into SpatioTemporal big data store). Thanks and Regards, Suryakant Sawant ... View more

Dear Noah, Thank you for your reply. The first question (i.e. Q 1. Error in executing jobs on GeoAnalytics Server) is solved for ArcGIS managed GeoDatabase. GeoAnalytics server is able to store results in managed GeoDatabase. The server was restarted and then it stared working. The exact reason for this behaviour is not identified.  The second question still persists. Following are the server logs, ArcGIS Server log   Message: Unable to connect to the manged egdb, Source: Hosted/<feature>.FeatureServer GeoAnalytics Server log Message: Error executing tool. CreateBuffers Job ID: j3609b8641b644fada0bfa157c956cecd : {"messageCode":"BD_101030","message":"Failed to execute CreateBuffers. Please contact your administrator with job ID 'j3609b8641b644fada0bfa157c956cecd'.","params":{"toolName":"CreateBuffers","jobID":"j3609b8641b644fada0bfa157c956cecd"}} Failed to execute (CreateBuffers). Message: Job 'j3609b8641b644fada0bfa157c956cecd' for tool 'CreateBuffers' failed: Connect to <machine fully qualified name>:9220 [<machine fully qualified name>/<IP Address>] failed: Connection timed out: connect. Connection timed out: connect. SpatioTemporal Big datastore validate response { "datastore.name": "bds_2wq79s3h", "clusterStatus": "YELLOW", "datastore.overallhealth": "Healthy", "isHealthy": true, "numOfNodes": 1, "numOfPendingTasks": 0, "activeShards": 1, "activePrimaryShards": 1, "relocatingShards": 0, "initializingShards": 0, "unassigned_shards": 1, "validationFailures": [], "nodes": [{ "name": "<IP Address>", "heapSize": "7.6gb" }] } Following is the Elasticsearch configuration  # ---------------------------------- Cluster ----------------------------------- cluster.name: <Cluster Name> # ------------------------------------ Node ------------------------------------ node.name: <fully qualified server name> # node.rack: r1 # ----------------------------------- Paths ------------------------------------ path.data: C:/arcgisdatastore/elasticdata path.logs: C:/arcgisdatastore/logs/<fully qualified server name>/elasticlog # ----------------------------------- Memory ----------------------------------- # bootstrap.mlockall: true # ---------------------------------- Network ----------------------------------- network.host: _site_,<fully qualified server name>,_local_ transport.tcp.port: 9320 # --------------------------------- Discovery ---------------------------------- discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["<fully qualified server name>:9320"] Do we need to change discovery.zen.ping.unicast.hosts? As it is allocated to <fully qualified server name> and above response shows the server IP address. What is the reason for connection timed out (to Spatio Temporal Datastore)? The firewall on all servers / machines is turned off. Please suggest regarding the same. ... View more