graeme

CopyFeatures from in_memory throws General Function Failure on Virtual Server

Discussion created by graeme on Mar 14, 2012
Latest reply on Mar 14, 2012 by graeme
The Python code below looks pretty straightforward.

import arcpy

if arcpy.Exists("D:/temp/test.gdb"):
    arcpy.Delete_management("D:/temp/test.gdb")

if arcpy.Exists("in_memory"):
    arcpy.Delete_management("in_memory")

arcpy.CreateFileGDB_management("D:/temp","test","CURRENT")

arcpy.CreateFishnet_management("D:/temp/test.gdb/test","0 0","0 1","1","1","1","1","#","NO_LABELS","#","POLYGON")

arcpy.CopyFeatures_management("D:/temp/test.gdb/test","in_memory/test2","#","0","0","0")

arcpy.CopyFeatures_management("in_memory/test2","D:/temp/test.gdb/test3","#","0","0","0")


and when I run it on a PC (ArcGIS 10.0 SP2; Windows XP SP3; 32bit) it completes in 4-5 seconds when run from IDLE or as a Python script tool in ArcMap (where I added it with no parameters).

However, when I move it to a virtual server (ArcGIS 10.0 SP3; Windows Server 2008 R2 Standard; 64bit) it still runs fine from IDLE but when run as a Python script tool in ArcMap it just sits at:

Executing: test
Start Time: Thu Mar 15 10:31:50 2012
Running script test...

When I move the tool I find a small Error dialog with a white "i" in a blue filled circled.

To dismiss that dialog I click the OK button and/or the "x" at its top right.

When it goes a second Error dialog appears - this time with the text "General function failure [test3]"

The code provided above has been stripped out from a much larger tool that I need to publish as a Geoprocessing Service which in turn requires that I save it as a tool layer within a map at 10.0 (10.1 won't be an option for quite a while).

The culprit seems to be the CopyFeatures from the in_memory workspace which will take some working around.  If I need to eliminate in_memory from this polygon overlay intensive application then its performance is going to take a big hit.


Would someone be able to run the same test as I describe above on a virtual server (it may also manifest on a physical server but I don't have one to test on) running ArcGIS 10.0 and Windows Server to see if they can reproduce what I am seeing, please?

Outcomes