Cannot invoke "com.esri.standardsql.query.Selection.getExpression()" because "<local6>.y" is null

[NoahFrazzini]

Following an upgrade from 11.1 to 11.3, our hosting server started throwing these errors.

Type: Severe

Message: "feature server..." Cannot invoke "com.esri.standardsql.query.Selection.getExpression()" because "<local6>.y" is null

Target: Rest

Machine: Hosting Server

Code: 9000 (Cannot access Admin API)

-- I am pulling these errors from the Admin API

Process: 11868. 

I am unsure as to why this has started so any advice or insight would be greatly appreciated. All enterprise datastores are healthy and validated. This specifically started happening following the upgrade and have not seen any other documentation on the matter. Due to privacy concerns I cannot provide screenshots.

[JakeNeedle]

Any solution for this?  It is still happening in 11.4.

[alexanderzitzmann]

same problem here by updating from 11.2 to 11.4:

/configuredatastore.sh https://********:6443/arcgis siteadmin ******* /gisdata/arcgisdatastore/ --stores spatiotemporal
Configuring data store(s). Initial configuration may take a few minutes. When configuring an upgraded data store, this process may take several hours depending on the size of your data. Please wait...

Performing upgrade prerequisite checks on data stores...

Error encountered: Cannot invoke "com.esri.arcgis.discovery.json.JSONArray.length()" because "<local3>" is null

i will open a case by esri tommorow

[JakeNeedle]

Any luck with Tech Support?

[alexanderzitzmann]

Unfortunately not, but I was able to solve the problem myself. In the OpenSearch configuration, localhost was set as the hostname.
I corrected this in the following files:
-spatiotemporal-config.json
-opensearch.yml
I also had to create a server certificate for OpenSearch itself and replace the node.pem and node-key.pem files (opensearch doesn't like wildcard certs and the cert must be the same like the hostname).
(Instructions:
https://gist.github.com/cecilemuller/9492b848eb8fe46d462abeb26656c4f8 )
Import the cross-certificate on the Geoevent server, and then everything worked.