Latest Contributions by JonathanIrwin

I have had this same request from a number of users/customers and agree that being able to search multiple groups would be a useful enhancement to this widget. ... View more

Hi all We are not seeing the moving bundle error but I thought I'd check if any of you are seeing the Invalid XML registry error, as there appears to be a lot of commonality with the issues and David noted in one of his earlier posts that esri did reproduce at version 10.2.1. So for reference purposes: -  we have a 10.2.1 clustered environment (windows 2012)  we have just moved in the last 6 months from 10.1. - we use Shared storage (UNC) - We do cache in production and not to a staging environment. - We publish service and then cache post service creation, so we are updating an empty cache or recreating tiles in existing. - We need to update the cache nightly, which will be scripted in python. So the load on the service should be low. - Unfortunately it looks like we will have to include within our script an AGS Service restart for each machine in the cluster before updating the cache. Thanks all Jonathan ... View more

Hi all I have been watching this thread closely over the last few weeks.  We have a 10.2.1 multi clustered and server site using shared storage with UNC paths.  We have regularly been seeing the "index was either too large or too small"  and  "field is not editable" errors when caching our services.  We get these errors when updating caches and creating from fresh. I was wondering if anyone has seen these following errors in the Caching Tools logs? -  Error executing tool.: TilesWorker: Output failure, error string = Unable to construct the map service instance. Failed to execute (Manage Map Cache Tiles Worker). -  Unable to instantiate class for xml schema type: CIMDEGeographicFeatureLayer -  Invalid xml registry file: e:\program files\arcgis\server\bin\XmlSupport.dat We first noticed these errors referencing the XMLsupport.dat file when publishing services.  It would happen randomly, then more frequent up until we couldn't publish at all.  An AGS service restart appears to resolve the issue at that point in time but eventually it comes back again. I only recently noticed the same error when caching.  My caching came to a standstill, however as soon as I restarted the AGS service all was good again - cache updates no problem. I am really wondering what causes the XML.dat file to become an issue\corrupt.  Esri support have recommended replacing this file with the same from a server install at the same build - but this wont prevent further corruption! So really just wondering if you are all seeing the same errors relating to XMLsupport.dat? Thanks Jonathan ... View more

Hey Sebastian I am experiencing exactly the same error message with version 10 also but with Inspire Extension sp2. Just wondering if you were able to find a fix? Thanks Jonathan ... View more