Latest Contributions by NathanHeick

This is my best answer.  I am not an expert, but I try to answer someone's question when someone else helps me. I would try to first use desc = arcpy.Describe(rasterLayer) to describe each raster layer in the map document.  See below: http://resources.arcgis.com/en/help/main/10.1/index.html#/Describe/018v00000066000000/ Then, I would try to use the desc.dataElement property of the layer describe object to get the raster dataset describe object.  See here: http://resources.arcgis.com/en/help/main/10.1/index.html#/Layer_properties/018v00000063000000/ Lastly, I think you could use desc.dataElement.CatalogPath to get the source of the raster.  See here: http://resources.arcgis.com/en/help/main/10.1/index.html#/Describe_object_properties/018v00000013000000/ Then, you could use it directly as an argument to RasterDomain without setting the workspace.  It sounds like you have various source folders for the raster datasets and you care specifically about the rasters in an MXD.  I don't know how you were planning on listing the layers, but I am assuming you would have to use the arcpy.mapping module instead of arcpy.ListRasters(). Hope this helps. ... View more

This might work, although I don't know if there is a better or more appropriate way to do it.  It looks like the key is to make a layer file first and then add it with arcpy.mapping.  It looks like you could make a layer file using the Make Feature Layer tool and the Save Layer to File tool.  Then, you can probably use the AddLayer function like in the 10.0 sample code I found below: import arcpy mxd = arcpy.mapping.MapDocument(r"C:\Project\Project.mxd") df = arcpy.mapping.ListDataFrames(mxd, "New Data Frame")[0] addLayer = arcpy.mapping.Layer(r"C:\Project\Data\Orthophoto.lyr") arcpy.mapping.AddLayer(df, addLayer, "BOTTOM") mxd.saveACopy(r"C:\Project\Project2.mxd") del mxd, addLayer ... View more

The only solution I see is learning ArcObjects or waiting for Esri to fix the bug.  Out of the 180, I have 19 relationship classes that use GUIDs that I have to create manually on a regular basis.  It also keeps our ETL process from being fully automated. ... View more

I can confirm that as well.  It still does not work. ... View more

I ran our ETL again on our new ArcGIS 10.1 Test Server.  The problem appeared immediately 10 minutes into the ETL.  I disabled Behavior Monitoring in Microsoft Forefront and the problem went away when I reran the tool. ... View more

One behavior we did identify is that the problem seems to only occur when the file geodatabase is open in ArcCatalog.  Previously, this was never a problem.  I could watch the feature classes being deleted one at a time and ArcCatalog would refresh.  It seems the combination of Microsoft Forefront and a shared lock being opened in ArcCatalog while accessing the file geodatabase locks the database from the same user who took out the shared lock, but not necessarily on every geoprocessing tool call, but some of them.  Uninstalling Microsoft Forefront while doing this testing solved the problem.  Reinstalling it did not recreate the problem immediately, but the problems only occur when the antivirus software is installed and Enable Behavior Monitoring is checked under Runtime Protection.  Technical Support created a bug for this: Bug #NIM085826  Microsoft Forefornt/System Center2012 Endpoint conflicts with file geodatabase operations. Hope this helps someone searching. ... View more

I'm still not 100% sure what is causing the problem, but it seems to only occur after repetitive calls to geoprocessing tools.  Also, whenever it has appeared and I have tried disabling the antivirus software, that fixed the problem.  I cannot consistently cause the problem by turning on the antivirus software, but turning it off does seem to fix the problem when it is there.  Usually, the Delete tool appears to delete some of the feature class from the geodatabase metadata, but leaves the table files themselves and the feature classes appear as a tables in the root of the file geodatabase. ... View more

After another day of troubleshooting and planning what to do, I at least learned that under the settings for Real-Time Protection, unchecking Enable Behavior Monitoring resolves my problem, but I cannot modify the system policy for all machines in the City.  I'm wondering if Microsoft Forefront sees certain ArcGIS 10.1 behaviors as suspicious or interferes with the geoprocessing operations with its scanning processes.  I don't see why this would start up at 10.1 versus 10.0.  I'm guessing there might be a definitions update required from Microsoft.  Technical Support is working on the issue, but I thought this was an important subject, so I wanted to leave an update for those who might benefit.  I'm trying to avoid adding exclusions.  I think Esri needs to identify why one version has trouble and not the other, and I think the solution should lie with the vendors on this one, not us changing our policies. ... View more

After two days of failure, I think I have diagnosed the problem with our ETL after migrating to ArcGIS 10.1.  It seems that Microsoft Forefront is interacting with the files in the file geodatabase while our model and scripts are running, producing highly variable errors and corruption of the file geodatabase.  I am calling Feature Class to Feature Class and Delete from these tools.  The feature classes become read-only and locked and the errors are inconsistent.  This was based on my own investigation. I decided to research the issue more and I found your Forum post.  Thank you for validation.  I wanted to add my issues to it and see if anyone had anything else to say about it.  We have Microsoft Forefront on both our servers and workstations, so I have been able to reproduce the issue on both Windows 7 and Windows Server 2008 R2.  I uninstalled Microsoft Forefront on my desktop and the issue was resolved.  Any solutions that are workable with Microsoft Forefront?  I will see if there are any settings I can adjust and post them here if they are successful. Thanks, Nathan ... View more

I just wanted to state that you don't need two clients to run ArcGIS Server 10.1.  You need two clients if you want to install ArcGIS Desktop and ArcGIS Server on the same machine.  Desktop still requires a 32-bit client and Server requires a 64-bit client.  You can use the instant client if you want to save space. ... View more

I believe you set the executable under Geoprocessing -> Geoprocessing Options --> Script Tool Editor / Debugger. ... View more

I followed up with Esri Technical Support on this issue.  They reported it as a bug and said that it won't be corrected until a later release of ArcGIS 10.1. ... View more

So far, what I have found using arcpy.ListToolboxes() is that my own toolbox is no longer listed after the first script tool call.  If I add it back in, the second script tool call works.  This would explain all the behavior I have seen, but I don't see why I would have to import it twice. ... View more

Please let me know if any of you find a clear explanation for this.  I have spent many hours the last two weeks with a similar problem.  The difference I have is that it occurs after I call the second script tool from my main script tool.  No matter how I comment out the code, the second tool call fails with AttributeErrors.  I thought I had fixed this on our development server, but when I moved our ETL toolbox to our test server, it came back more consistently than ever.  Now, I get the issue when calling models from the script tool, not just script tools from the script tool.  I had concluded it has something to do with arpcy and the ImportToolbox function.  If I find something today, I will let you know.  First, I want to test Mark's workaround and understand it.  I will be so happy when this problem gets resolved.  It's ruining my weekend automation. ... View more