Limit on number of feature classes in mxd when caching?

[WhitehorseCity_Council]

Hi all,

I am trying to generate a cached map service for a .mxd containing 150 feature classes.

ArcGIS Server creates the service, but then fails to generate the map cache. (The log files tell me that the Caching GeoProcessing Service has crashed and the anlayze map tool shows nothing prohibitive in the mxd prior to publishing.)

I have tested creating caches for map services with fewer feature classes, say <20 and it works fine.

I am wondering, is there a limit on the number of feature classes that can be in an .mxd when you are attempting to create a cache?

I have been unable to locate any ESRI documentation on the matter.

thanks,

[RandallWilliams]

There's not a documented limit on the number of feature classes that can be in a map document when caching a service. I'd set your ArcGIS Server logs to 'debug' and attempt to reproduce the issue and forward the logs to Esri support services. What's the source of the underlying data? If you're using enterprise GDB, I'd consider copying those feature classes to a file geodatabase that lives locally on the GIS Server, repath your cache document, and cache from that. This will help reduce or eliminate issues related to network latency and database performance.

[WhitehorseCity_Council]

All of our data is being read from an enterprise GDB (SDE-SQL 2008) so, unfortunately, copying data to our GIS Server as File Geodatabases is an unsustainable solution for us.

Do you know if changing the pooling settings on the Cache GeoProcessing Service from default (3) would help? We usually set our dynamic map services to 15. Again, I've found a couple of forum posts about this but nothing solid in terms of ESRI documentation.

thanks,