Instant Search fails with HTTP Error - Error performing query operation

Permanently deleted user

October 21, 2015 18:57

When attempting to run the initial index for instant search, it fails with the error HTTP Error - Error performing query operation. Encounterat at <time> for URL <service URL>. Will retry after <time>

 

I have increased the soc memory heap size substantially based on the guidance in this ESRI support article: http://support.esri.com/em/knowledgebase/techarticles/detail/40890 to no avail. Anyone else ever been stumped by this one and have some pointers for me?

0

• 

  Permanently deleted user

  November 06, 2015 15:30

  I'm still struggling with this, instant search will not pass 1%. I currently have the SOC memory set at 2048MB which seems excessively large to me. 

   

  What I find most interesting is the site having the problem is a production copy of a development version. The sites are identical but sitting on a different server. The dev version's instant search index populated without trouble and is about 11GB. The production version's instant search directory is sitting at 23GB despite only being 1% complete! Is it possible when I copied the site to the production server the indexes came along but are somehow not being recognized? I find it curious it is double the size of the dev version.

   

  Is it possible to simply copy the indexes from the dev to production server?

  0
• 

  Permanently deleted user

  November 20, 2015 00:55

  Hi Piper

   

  I am getting the same problem also on a DEv server but the map service that is pointing at one in the Prod environment.

   

  I have increased the OSC memory limit as per the ESRI article mentioned above with no change.

   

  What would be useful to know is if there are any logs that these errors are recorded to for further analysis.

   

  I did find one file called BootStrapper.console with a match to my error message that showed the full request in question:

   

  http://geo.rdc.govt.nz/arcgis/rest/services/Core/Cadastral_Static/MapServer/26/query?objectIds=1%2c2%2c3%2c4%2c5%2c6%2c7%2c8%2c9%2c10%2c11%2c12%2c13%2c14%2c15%2c16%2c17%2c18%2c19%2c20%2c21%2c22%2c23%2c24%2c25%2c26%2c27%2c28%2c29%2c30%2c31%2c32%2c33%2c34%2c35%2c36%2c37%2c38%2c39%2c40%2c41%2c42%2c43%2c44%2c45%2c46%2c47%2c48%2c49%2c50%2c51%2c52%2c53%2c54%2c55%2c56%2c57%2c58%2c59%2c60%2c61%2c62%2c63%2c64%2c65%2c66%2c67&outFields=*&outSR=4326&returnGeometry=true&f=pjson

   

  In this particular layer in the map service there are only 19 feature and it returns a result correctly if I change the request to:

   

  http://geo.rdc.govt.nz/arcgis/rest/services/Core/Cadastral/MapServer/26/query?where=1%3D1&outFields=*&returnGeometry=true&outSR=4326&f=pjson

   

  Not sure what is going but still frustrating

   

  Regards

   

  Ralph Price

   

   

  0
• 

  Permanently deleted user

  November 30, 2015 14:33

  Hi Ralph,

   

  My problem evenutally resolved. I engaged Latitude staff who narrowed it down to a particular large layer in my service, however before I got around to addressing it the index completed over the weekend. The SOC memory was set at 512MB. The logs we investigated were those located in Geocortex Core/Logs and also the arcgisserver logs (located under arcgisserver/logs/<servername>/server. Sorry I don't have a more definitive answer for you but hopefully this helps.

  0

Please sign in to leave a comment.