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!
Hmmm....I was going to respond with the oath and found a "recovered" comment (from who knows when) that I obviously never sent. I'll just send this as is.....with the added note that the AppData folder will be hidden on many machines by default, but it you type the path in (after you get to the user folder) you should be able to find it.
Interesting thread. And although my error "the index was either too large or too small" is coming from a different process, my guess is it related to all the above.
In this case, I'm testing 10.3 pre-release because I wanted to compare the 10.2.x bundle with the new 10.3 bundle, to see if it really was smaller. So, although I've come at it several ways, what I'm really wanting to do is to use the "Upgrade Map Server Cache Storage Format" in the Server Tools->Caching toolbox. The other tool I tested to see if this would word was an attempt to export/convert it back to an exploded cache to see if I would get it to work from that format. I get the error from both.
For me, I think the issue is I'm running out of temp space on my C drive. Even though it never gets to zero, it seems that the more space I have available when I start one of these commands, the longer it will go before it crashes. I know from previous experiences (when caching caches with 10.0) that there are many temp files that are created in
c:\users\<AGS service account>\AppData\Local\Temp that never get cleaned out properly. I also notice, many files are created here that are never cleaned out when the command crashes (although I am deleting between running my processes). My test 10.2.2 bundled cache I am trying to convert is ~ 9GB. I have about 13 GB free on C.
by the way... the <AGS service account> it the account that the actual windows service for ArcGIS Server is running under, not what you necessarily use to log into manager.