First zoom to feature wrong location

Permanently deleted user

31 Juli 2018 18:55

When I select a feature (currently from instant search) the first attempt at zooming to the feature takes me to the wrong location.  The second time it works.

 

 Any Ideas?

0

• 

  Permanently deleted user

  07 November 2018 23:39

  Hi Craig,

   

  When this happens, is anything else happening in the viewer interface (the shell)?

   

  We have many old (and fixed) bug reports from issues zooming to the wrong location when the zoom command was sent to the viewer while the map extent was changing (many from the Silverlight days, when the zoom was animated and there was more chance of repositioning it while it was still in motion)

   

  If there is some additional action happening, please report your viewer version, or even just open a support ticket to report the bug.

   

  Regards,

   

  -Malcolm

  0
• 

  Kristin Judy

  28 December 2018 20:02

  I'm having the same issue in one of my sites, and have had the issue crop up before on the dev version of the same site.  It's only on the map service that have Instant Search enabled.  The correct feature is selected and highlighted at the initial extent of the viewer, when I “click to view feature details” the viewer appears to take me to the center of initial extent, and then when I “click to view feature details” a second time, it takes me to the correct feature/location in the view.  All subsequent searches take me to the correct feature/extent when I “click to view feature details”. 

   

  Sometimes scanning the service again fixes the issue, but that's not the case in the site where I'm currently experiencing the issue.  I’ve also tried to delete the index for the service, and re-scan it, but that hasn’t worked.  I do have the Scanner Manager scheduled to scan the service daily in the role.config, from D:\GeoCortex_Application_Services\Geocortex Core\NSRoot\Geocortex\Core\Roles\InstantSearch\ScannerManager\3.xxxx, which appears to be working.  If I review the InstantSearch.Scanner.log it appears to have successfully started and finished scanning the service.  However, I do some earlier entries that have the following error: “Exception Occurred: 'There was an error while trying to refresh a message.' details: MessageQueueElasticException: Failed to execute the update request in elasticsearch.. Error Details: Response Code - 409, Error Type version_conflict_engine_exception, Error - Type: version_conflict_engine_exception Reason: "[ScanRequest-103_202_71_208:http_arcgis_rest_services_planning_lupermits_planning_lupermits_referencedata_mapserver-Medium][AWf1OqAOLioeD3NKJCT-]: version conflict, current [3], provided [2]"  at Geocortex.Platform.Infrastructure.MessageQueue.MessageQueueExtensions.AssertResponse(IResponse response, String message, Int32[] validCodes) at Geocortex.Platform.Infrastructure.MessageQueue.MessageQueue.<>c__DisplayClass39_1`1.<<LockMessage>b__0>d.MoveNext()”

   

   

  Planning to upgrade this instance next week to Essentials 4.10.3, but that’s what my dev instance is presently at and it hasn’t resolved the issue.

   

  Essentials 4.10.0

   

  GVH 2.11.0

   

  Thanks,

   

  Kristin

  0

Du måste logga in om du vill lämna en kommentar.