Latest Contributions by deleted-user-zpcJw1u0IXiO

I have a script I'm developing to automate changing the data source from parcels_1 to the original feature class parcels from which I had manually changed source several weeks ago. It was a most tedious task to do manually, and was done for several layers in multiple MXDs, hence my desire to automate it. The MXD I am using for testing has two layers that have the same feature class for data source, but each has a different definition query to show just the relevant subtypes: Layer Parcels has definition query "SUBTYPE" <2 OR "SUBTYPE" = 8 Layer RoadROW has definition query "SUBTYPE" BETWEEN 2 AND 5 Both layers are drawn with Unique Value symbology, and in the output MXD, everything draws correctly symbolized on the map from the successfully updated data source. Trouble is in Layer Properties, only RoadROW has a Symbology tab that shows what it did before. The Symbology tab for Parcels has just Single Symbol, and actually entirely lacks Categories as an option to choose. I do not understand why the two layers behave so differently. Perhaps it's because Parcels has two joins and one relate, while RoadROW has neither? The joins come through properly, but the relate does not. For RoadROW, lyr.symbology.valueField was bcwa.GIS_ADMIN.parcels_1.SUBTYPE before being changed For Parcels, lyr.symbology.valueField was SUBTYPE already before being changed. I don't know why the difference between the two layers in that regard. As a work around, in my script I have tried  if "parcels_1" in lyr.symbology.valueField:     lyr.symbology.valueField = 'SUBTYPE' but when running it I get ValueError: SUBTYPE Maybe it doesn't matter because lyr.symbology.valueField is already SUBTYPE? I hesitate to leave the Parcels layer in the state it is in, but ought I even be worried? Thanks, Justin ... View more

I have an image service I've successfully cached previously. It had four empty scales 1:50, 1:100, 1:250, and 1:500 I created in order that the Geocortex viewer would permit zooming closer than the cached levels. I have found need to populate the cache at 1:500, and was able to get perhaps a third of the service extent to do so. The table below shows the Cache Status where it is stuck, despite that Level 17 is currently underway for the dozenth or so attempt.  Level Scale Size Expected Tiles Completed Tiles Percent In Progress 0 1,000,000 0.18 MB 6 6 100 1 500,000 0.61 MB 18 18 100 2 250,000 2 MB 55 55 100 3 125,000 4.36 MB 210 180 85.71 4 100,000 6.76 MB 312 275 88.14 5 64,000 9.87 MB 760 624 82.11 6 50,000 13.92 MB 1,200 960 80 7 32,000 27.75 MB 2,886 2,356 81.64 8 25,000 39.45 MB 4,653 3,744 80.46 9 16,000 65.76 MB 11,242 9,150 81.39 10 10,000 162.53 MB 28,405 23,183 81.62 11 8,000 228.27 MB 44,352 36,058 81.3 12 5,000 471.78 MB 113,390 91,868 81.02 13 4,000 742.54 MB 177,408 143,395 80.83 14 2,500 1.91 GB 453,560 366,520 80.81 15 2,000 2.79 GB 708,400 572,390 80.8 16 1,000 11.01 GB 2,832,450 2,285,258 80.68 17 500 4.47 GB 11,327,500 2,583,061 22.8 18 250 0 MB 45,310,000 0 0 19 100 0 MB 283,126,752 0 0 20 50 0 MB 1,132,434,765 0 0 The trouble is the tile count never changes, despite my running Manage Map Server Cache Tiles with each attempt using an Update Extent shapefile covering a progressively smaller fraction of the area needed. So after three hours on an extent of just 30 sq. miles, the job details URL reports 0% completion on each line, with a different Estimated Time Remaining that grows larger and larger before dropping back to begin growing larger again. The Logs in AGS Manager report what I suspect may be the reason for no tile creation: SEVERE Aug 15, 2016, 1:21:23 PM Error exporting image Wait time of the request to the service 'public/swoop2015_mosaic.ImageServer' has expired. Rest SEVERE Aug 15, 2016, 1:21:23 PM Unable to process request. No instances for 'public/swoop2015_mosaic.ImageServer' were available for 60.006 seconds. Wait timeout exceeded. public/swoop2015_mosaic.ImageServer SEVERE Aug 15, 2016, 1:20:41 PM Error exporting image Error handling service request :Processing request took longer than the usage timeout for service 'public/swoop2015_mosaic.ImageServer'. Rest SEVERE Aug 15, 2016, 1:20:38 PM Processing request took longer than the usage timeout for service 'public/swoop2015_mosaic.ImageServer'. Server request timed out. Check that the usage timeout is appropriately configured for such requests. public/swoop2015_mosaic.ImageServer I don't know what to try next. I have already restarted the image service with no change in behaviour. Short of contacting Esri tech support, what should I try to correct this issue? Thanks, Justin ... View more