We are experiencing brand new caching issues at 10.2.2. I am unable to either DELETE_TILES or RECREATE_ALL_TILES from an existing cache. The error we keep receiving is:Line 30Output failure, error string = Error moving bundle Failed to cache extent: -9223211.962860 3087885.815688 -9079003.170544 3271103.291998 at scale 577790.55428899999.The error occures when running RECREATE_ALL_TILES or DELETE_TILES operations of the Manage Map Cache Tiles (run as a tool or script) when run from a dedicated server gp cluster machine. Our clustered setup consists of a network file server storing our config, security and data-stores, as well as all server and system directories. Two servers serve as a mapCluster for map and image services, a single server in a gpCluster for caching and user-defined gp services, and a virtualized web server for the WebAdaptor. This has occurred as of lastweek whether reading from the GIS SDE database OR from a data-store file gdb. All permissions for directory shares and folder and file security have been accounted for.When the error occurs, the entire cache becomes corrupt, making any other caching operations in-operable (delete cache, delete tiles, etc). During the recreate, the bundlx file is being removed but the bundle file is not, thus not allowing the tool to overwrite thebundle from the admin-defined /arcgistemp folder(s) on the GP server.Thus far, the only solution has been to kill the service, stop the site, and then remove the entire cache directory, restart the site, recreate both the service and the cache.Has anyone encountered this?Thanks-David
Greetings all, Did anyone find out about this issue at UC?
A small update: The Recreate_All_Tiles option worked again last week (repeatedly using my python IDLE) on our stand-alone development server, but continues to fail with the same frequency and 'error moving bundle file' error in our distributed three-machine, 2 cluster production environment where our shares, directories and stores are stored on our 1Gig Lan connected file server. It would be really, really great if ESRI could comment.
David
Sorry to re-start this thread, but are there any updates on this?
I'm having near-identical issues to the OP with a very similar set up.
A 1st cache of a service works. Any subsequent caching, whether it be the full extent of the service or a number of smaller AOI's within the service leaves behind some blank spaces and some areas where a cache only exists at some scales.
I will raise a ticket with ESRI today, but was wondering if anybody had received a response/workaround/fix to this as I'm aware that a number of you had tickets in with ESRI.
Many thanks
Dan
I have a ticket with ESRI Sweden, they have been able to reproduce this error but have no solution yet.
Meanwhile I've been testing to use the EXPLODED Storage Format to get rid of the bundle-files and see if some of all the png-images gets locked as well, so far they have not.I only have a couple of cached services that are updated regularly, I will publish them with EXPLODED storage format until I hear of another solution/workaround for the COMPACT storage format.
Thanks Matt, interesing result regarding the Exploded v Compact.
I too am working with Jon out of Redlands to get this solved. We ran some I/O tests yesterday using IOzone and thus far have determined that throughput does not seem to be the culprit. We will be running a ProcMon test later today and I will post the results
I do not have a solution only a sad comment about this issue.
When developing a web adf application 3 years ago, I tried to use the compact cache option for my cached services, but found many missing tiles, which of course would be confusing to the enduser and therefore unacceptable. The only solution after a few months of testing and an ESRI support ticket was to use exploded caches, which are still in use today. Hopefully, ESRI will come up with a solution at this time, but it sounds like an exploded cache might be your best option at this point in time based on my past experience.
Is this problem occurring in all version of ArcGIS Server v10 (10.0, 10.1, and 10.2)? I ask because I might be looking to use weekly updated cached mapservices in my current production environment (v10.0) if dynamic mapservices fail to perform well.
Hi Michael, no. The bundle move error (which from what I see is really is a *.bundlex file not being moved from an arcgistemp folder on a gp machine in a cluster environment to a shared cahe directory) bundleissue is brand new at 10.2.2 (to us anyway). I've never encountered an bundlex move error prior to this release since the bundles have been in existence.....
Mattias,
We are experiencing the same problem that you did when you posted this. We are at 10.2.2 and get this error sometimes and sometimes we do not. Did you get this fixed? If so, what workflow helped to resolve your problem?
You can install a patch to address this issue
found at
Patches and Service Pack - Esri Support
You'll need to log in to download the patch.
There also is a bug with ArcGIS Server v10.2.2 where bundle errors do not get deleted from a temporary directory on the ArcGIS Server server. You might want to periodically check this location so it does not fill up storage on the server which could eventually impact the performance of AGS. These issues have been fixed at v10.3.x if you can upgrade your software.
John,
I just want to confirm that the patch Michael referring to fixed the issue for us.
Michael and Mattias,
Thank you for your feedback! I have installed the ArcGIS 10.2.2 for Server Map Cache Consumption Patch on both ArcGIS Servers that participate in the site some time ago. Yet we are still experiencing caching errors.
The most recent error was received after trying to update the cache using a feature class as the AOI when applying the DELETE_TILES option to the ManageMapServerCacheTiles tool. See below:
ERROR: Failed to cache extent: -10798905.658617 3874446.062724 -10762339.554976 3891581.043078 at scale 4513.9887049999998 The index was either too large or too small.
Failed to execute (ManageMapServerCacheTiles).
I am not familiar with the bundle errors nor the temporary directory where they are stored. How can I find this location to determine if it is contributing to the problem?
Unfortunately I cannot upgrade to 10.3.x at this time because we are required to support a legacy ArcIMS application until we migrate it to ArcGIS server.
Thanks again!
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.