Latest Contributions by ArtUllman

‎11-06-2013

I figured out my problem. The SQL Server database was set to a case-sensitive collation sequence. Once, I changed the database to case-insensitive collation, I was able to create and load feature classes using a direct database connection without enabling the database as a geodatabase. Thank you for your assistance.

‎11-06-2013

I created a "database Connection" using Direct connect. The SQL Server is enterprise.

‎11-05-2013

With 10.1, I have been able to Import Feature Classes to brand new layers in SQL Server 2008 R2 without enabling enterprise Geodatabase. All I had to do was create a database, and then create a database connection in ArcCatalog. Once I had a connection, I could use the Import Feature Class to import FGDB layers to the database. I did not use inter-operability extensions, but I did have ArcInfo Advanced. There were no SDE tables in the database. Is this something you can try on your system?

‎11-05-2013

I have a brand new empty SQL Server 2008 R2 database. I am trying to either load data from an FGDB or create a new Feature Class using ArcCatalog. Every time I try to perform either function, I get an error: Wrong Column Type and 00210 error. When I run the SQL Profiler, I can see that the following SQL executes correctly in SQL, but then I see a DROP TABLE immediately after this step: CREATE TABLE GISMART_TST.dbo.aaaaa ( OBJECTID INTEGER NOT NULL IDENTITY , SHAPE geometry NULL, PRIMARY KEY ( OBJECTID) ) I am running Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64) and ArcCatalog 10.1 with SP1. I have done this plenty of times at other installations without problems. My license is Desktop Standard. In the past, I have had ArcGIS Advanced License. I don't think this should make a difference.

‎06-25-2013

I'm going to wake this thread up. Anybody know what the VM setting to change is? We had a similar problem. We originally started out with only 4GB of RAM on a VM, which was not enough. We requested more memory. Well, they allocated more virtual memory to the VM, but kept the same physical memory settings (without tell us this). As a result, the OS thinks it has more memory, but there is a balloon driver in VM that actually steals all of the fake memory so the applications do not get to use any of the memory (which doesn't exist anyway). We kept seeing memory utilization go up every time we requested more memory, because the balloon driver kept consuming the additional virtual memory. We thought it was ArcGIS, but was really the VM Settings. You can see the "private" balloon memory using a tool from sysinternals called RAMMAP.

‎01-24-2013

It turned out that the memory issues we were running into were related to the Virtual Machine (VMWare) configuraton. The VM really only had 4GB of phyisical memory, even though the OS was showing 24GB. VMWare uses something called a balloon driver to trick the OS into thinking it has more memory than it really has if you do not allocate the physical memory to the VM. The balloon driver grabs all of the 'fake memory' so it looks like you have very high memory utilization on the server. In reality, the balloon driver has grabbed all of the fake memory you see in task manager. Once the VMWare configuration was corrected, all of our memory problems were solved. Memory utilization is now on par with our expectations - less than 8GB for 35 services.

‎01-07-2013

Thanks. That makes sense. I will try that.

‎01-03-2013

I am trying to write a script for creating new services using the ADMIN API: http://resources.arcgis.com/en/help/server-admin-api/ I do not see any way to specify a folder name for the service.

‎11-02-2012

Thanks! The geodesic functions sure are great! Art Ullman

‎10-05-2012

I am getting the following error whenever I run the geodesic.area method on any feature that has hole (i.e. donuts). I get: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index This is with Silverlight API version 3.0.0.288 running under Silverlight 5.1. By the way, the geodesic functions are great.

‎08-30-2012

Thanks. I was hoping to get some sort of idea as to how memory is allocated in 10.1. In 10.0 on IIS, I was able to monitor memory utilization as additional SOC processes spawned. In 10.1, it looks like it allocating about 80% of 16GB of the memory for only about 12 concurrent SOCs. I am wondering if it is pre-allocating memory based on availability in the system. If this is true, then I need some sort of metric or perfmon stat I could use to determine memory requirements. I don't want to wait until I start paging to determine it is time to add memory.

‎08-24-2012

I am trying to understand how memory is allocated with 10.1 running in a Windows 2008 environment. I installed 10.1 on a Virtual Machine with 4GB of RAM. We were using 90% of available memory and I started having issues with services crashing. I bumped memory to 16GB of RAM and have not had any issues with services crashing, but I am at 90% memory utilization again. I am using default heap settings. We are currently running a single instance/machine (no clusters). We have not worked out our load balancing configure yet. I have the following questions: 1. Will ArcGIS Server try to allocate X% of the memory on the system? If so, what percent is normal? 2. How much memory should I expect to consume for each service/process? I am running low isolation with minimum instance of 1 and max of 4. 3. What are the recommendations for setting the HEAP allocations? 4. Alot of our services use Query Layers. Does that change anything in regard to tuning or memory allocation? I am planning on doing to load testing, but would like a better understanding of memory utilization for 10.1. We are trying to plan and design a stack for our production environment and are trying to understand memory utilization with the new ArcGIS Server. Thanks, Art Ullman

‎08-01-2012

This is �??as Designed�?�. AOI envelope generates the cache tiles for the extents that cover the minimum bounding rectangle of the AOI instead of the supertiles that intersect the polygon. Would you be willing to share your data with us for testing? Thank you, Andrew Thanks Andrew. I was expecting the caching process should use the MBR, but it appeared to be rebuilding well tiles outside the MBR of the feature class. I was able to figure out the problem. I originally created a Feature Class, and then modified features several times before using it as the envelope for rebuilding the cache tiles. After modifying the Feature Class, I did not go back into ArcCatalog and "recalculate" the extent for the feature class. As a result, I had one small feature in the FC, but the feature class had a very large extent based on features that no longer existed. Recalculating the Extent should fix the problem. Thank you for your assistance.

‎07-31-2012

Thanks. You were correct. There was nothing wrong with the scale dependancies or exportOptions parameter. It turns out that there was another layer that was being drawn which looked identical to the layer that I thought I had scale dependancy issue. I did not expect this layer to be drawn because of the filters I set in the Query Definition. However, my Java Script added a new filter using a layer definition. It looks like the LayerDefinition overrode the query definition in the MXD. I thought it would just append to it. Anyway, my problem had nothing to do with scale dependancies or exportOptions. My problem was that I did not understand how layerDefinition interacted with Query Definition in the MXD. I am not sure why it worked correctly in the Java Script interface, but did not work in the Print Task. It doesn't matter though, since I was able to fix my code by appending the original query definition in my layer definition. Once I did this, I got consistent results. Thank you for your assistance.

‎07-31-2012

We are seeing similar inconsistencies. We are generating caches for national scale mosaic dataset of 1m imagery. We ended up with holes. When we tried to fix the holes by supplying an AOI Polygon, it did not always work. We switched over to using AOI Envelope. We had better results with envelope, but it seemed to generate tiles for areas that were much larger than the envelope we supplied. This is problematic for national scale imagery. We kicked off a very small envelope yesterday, and it is still running.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by ArtUllman

Re: "Wrong Column Type" trying to create a Feature class in non-SDE SQL Server with 1

Re: "Wrong Column Type" trying to create a Feature class in non-SDE SQL Server with 1

Re: "Wrong Column Type" trying to create a Feature class in non-SDE SQL Server with 1

"Wrong Column Type" trying to create a Feature class in non-SDE SQL Server with 10.1

Re: 10.1 Memory Issues

Re: memory utilization with ArcGIS Server 10.1 - request for recommendations

Re: How do you specify the folder name when creating a new servier using the ADMIN AP

How do you specify the folder name when creating a new servier using the ADMIN API

Re: geodesic area method getting error for features with holes (donuts)

geodesic area method getting error for features with holes (donuts)

Re: memory utilization with ArcGIS Server 10.1 - request for recommendations

memory utilization with ArcGIS Server 10.1 - request for recommendations

Re: Caching in 10.1 produce inconsistent results

Re: PrintDigit not setting exportOptions in req. - problem with scale dependencies

Re: Caching in 10.1 produce inconsistent results