Latest Contributions by RoyceSimpson

‎09-28-2012

What is the "max instances" value for your cachingtools service? If it's 16... and you set your cache to process with 16... and you are only getting one cpu to process... yeah, that is odd.

‎09-28-2012

Ok, I'm up and running at full caching capacity. You need to make sure your CachingTools services is pointed at the correct cluster. I had mine pointed at my wrong one, which only has one machine in it. I pointed it over to my "caching cluster" and now my map service, which is hosted on the first single machine cluster, is caching at full multi-machine cpu capacity. Pretty cool. Really cool actually. -r

‎09-28-2012

I am using 10.1. How can I easily tell how long a cache runs? In 9.3.1, when the cache completed, the message box would indicate how long it ran. Also, I am using a 16 core machine dedicated to caching only. I set the max instances to 17 but it only ever uses 1. Why?? I'm having similar issues. I've got multiple machines and a couple "clusters". One cluster has only one machine in it and the other cluster has a bunch. I'm trying to use that second cluster for caching. When I setup a map service and tell it to live in the second cluster, then run the map cache... it doesn't use any of those cpus (even though the map service is reporting the correct number of "max instances") and uses only cpu's from the machine in the first cluster. Very odd. I've checked and re-checked that the service is setup properly and is being hosted by the second cluster. The "instances running" counts in both the web manager and ArcCatalog are very confusing as well and they state conflicting and erroneous map service instance counts when the cache is running. Good luck on this. I've posted a similar thread on this forum as well. -r

‎09-28-2012

There are several threads in this forum regarding map service performance issues. Have a look through those as well. -r

‎09-27-2012

My experience with 10.1 caching is similar to other posts. The new tools are unstable and unreliable, with poor error reporting. Typical first release... It is frustrating that a relatively simple task in 10.0, which worked fine, has become a convoluted web of trial and error to get a basic cache built. I find I can build levels 1-5 when publishing the map service. When I try to build levels 6,7 and 8, this is where the witchcraft of figuring out what approach doesn't break it and leave me wondering what is going on. I found one dramatic approach that seems to help, and that is to stop all the other map services and only run the one you want to cache. NOT very efficient. Build the initial levels, and then add one at a time, and pray to the voodoo gods that it doesn't just mysteriously stop on its own. It shouldn't be this way! I have better use of my time than debugging pre-release state release software. Come on ESRI get this fixed with SP1!!!! I've experienced this as well. Very frustrating caching building experience in 10.1. If I only cache one scale at a time, it works fine. If I cache many scale levels, only a few get done. The only way to guarantee a full cache creation is to run each scale individually... which of course isn't really an option.

‎09-27-2012

In my case the slow performance was Windows Server 2008 related. I upgraded it to "R2" and performance is great now.

‎09-27-2012

I've upgraded the server from Windows Server 2008 to Windows Server 2008 R2 and that seems to have fixed the problem. Will do some further confirmation by moving the config-store and other directories to the network share.

‎09-24-2012

It looks like your REST directory is even taking a long time to load. I have cached all our image services in 10.1 and they have been drawing very fast. I have had an issue with having multiple servers on a site. It caused Manager and ArcCatalog to load all the service information really slowly. I gave up on it before viewing the performance of the map services. It looks like the issue has to do with sharing the config-store on a network share. You may want to try removing the other servers from the site and changing the config-store path to a local path. Thanks for that info. I'll fire up another server with all local directories today to test that out. If that's the problem, that'd be a bummer and show stopper for a multi-server site.

‎08-02-2012

Ok, so I updated the existing server's "arcgissystem" folder to be in the shared space along with all the others and now the new ags install can "join site". I hope that was the right call. Not sure why that "arcgissystem" folder was create locally on the existing server when all the others were specified to go to the shared space. Anyway, things seem to be fixed. -r

‎08-02-2012

Hi Royce, This error occurs because the second machine that you're trying to join to your existing GIS site, can't access either the configuration store or the server directories (or both) of the existing GIS site. You need to ensure that both the configuration store and the server directories of the existing GIS site are located on shared network locations that can be accessed and have read/write permissions by the ArcGIS Server account on the second machine. Joining an existing site help topic Expanding from one GIS server to multiple GIS servers help topic Hope this helps, Thanks Derek, I've made sure that the config-store, directories and logs folders are all on a shared location and have installed both the existing, properly functioning AGS machine as well as this new machine using our arcgis AD account. So, I'm not sure what else can be looked at in that regard. Now, when I go into Manager on the existing machine, then go to the "Site" tab and "directories" option, I see that the "system" folder is set to the local "C:\arcgisserver\directories\arcgissystem" location and not in the shared space. Does that need to be over in the shared space as well? Other than that, I'm stumped. -r

‎08-02-2012

I'm getting the following error when trying to join a newly installed AGS to an existing site (which is up and running just fine). Failed to join the site 'http://firn:6080/arcgis/admin/'. Server machine 'http://firn:6080/arcgis/admin//machines/register' returned an error. 'Failed to register the server machine 'TUNDRA.LC.GOV'. Server machine 'http://tundra:6080/arcgis/admin' returned an error. 'Unable to access the server directory 'C:\arcgisserver\directories\arcgissystem''' See the attached screenshot for the exact error. [ATTACH=CONFIG]16607[/ATTACH] I've uninstalled and reinstalled a couple times with no success. Which "c:\..." folder is trying to be accessed for this? "C:\" on the local server or the server which is trying to be joined to?

‎05-18-2012

Ok, got it solved. The server I've been attempting to get the webadaptor installed/configured on didn't have asp.net registered in 64bit mode. Did that and all is well.

‎05-14-2012

I'm having what seems to be the same issue. I have AGS 10.1 prerelease loaded on two servers as well as IIS (win srv2003). When I install the iis webadaptor, the install goes ok but the resulting web page that comes up is an error 500 page. Same thing happens if I try to install web adaptor on other server as well. I can't seem to get in to configure anything.

‎02-13-2012

Thanks Ivan, Yes, I have all my actual "map layers" in the mxd categorized within group layers. I'll look into your solution ASAP. -r

‎01-30-2012

I've got a map object which has a dynamic map service layer (myLayer) in it that I'm using as to populate a legend. The legend.layers property is being set to that dynamic map service layer (legend.layers = [myLayer]). In this app, the user is restricted to pick and only show one "layer" out of the 30+ "layers" within myLayer. With the legend turned on, the user should see only the legend item for the single "layer" that they have turned on at any given time. This is all working fine except that it seems that the legend component draws each legend item a little lower than the previous one in the myLayer TOC layer list, so if the user turns on the 35th layer in myLayer, the legend draws up with a vertical scroll bar that you have to scroll through a bunch of blank space to finally get to the desired legend item. I've attached two screen shots. noBlankSpace.jpg shows the legend when the user draws only the first "layer" in myLayer. If the user picks, say... the 20th "layer" in myLayer to draw... it looks like what you see in lotsOfBlankSpace.jpg. If the user picks the 30th "layer" in myLayer, they need to scroll down a window of blank space before they see the legend item. There seems to be a direct correlation between how far down the the "layer" is in the published MXD TOC and how much blank space precedes the legend item to be drawn. Not sure how to fix this but it's pretty tough on users to have to scroll through a bunch of dead air to see legend items.

Online Status	Offline
Date Last Visited	‎03-24-2021 06:29 PM

My Ideas

Latest Contributions by RoyceSimpson

Re: Caching time / Not using max number of instances

Re: Caching time / Not using max number of instances

Re: Caching time / Not using max number of instances

Re: Web Application is slooooooow... Any ideas?

Re: Caching in 10.1 produce inconsistent results

Re: Slow performance administering services in ArcCatalog and ArcGIS Server Manager 1

Re: terrible cached map service performance with 10.1

Re: terrible cached map service performance with 10.1

Re: Getting error after installing AGS 10.1 and trying to "join site"

Re: Getting error after installing AGS 10.1 and trying to "join site"

Getting error after installing AGS 10.1 and trying to &quot;join site&quot;

Re: Pre-release 10.1 Web Adapter Install Problem

Re: Pre-release 10.1 Web Adapter Install Problem

Re: Legend component rendering issue

Legend component rendering issue

Options for an Embed Web Map with Time Aware URL P...

ArcGIS Server "image server" error

Re: How do I sum the values in a field in ArcGIS P...

Allow Users to Change and Disable Alerts

Re: WAB Dev Edition deployment... fail.