使用ArcObjects地理处理器执行Union工具时遇AutomatedException错误求助

Hey there, I’ve dealt with this exact AutomatedException when running Union via ArcObjects before—super frustrating, but there are a handful of common fixes that usually get it sorted out. Since you didn’t include your code snippet, I’ll walk through the most likely culprits and solutions below:

• Validate & Repair Your Input Geometry
  ArcGIS tools are notoriously picky about invalid geometry. First, run the Check Geometry tool on all your input feature classes—look for issues like self-intersections, null geometries, or broken topological relationships. If you find problems, use Repair Geometry to fix them before attempting the Union operation. This is the #1 cause of this error in my experience.

• Double-Check Geoprocessor Environment Settings
  Missing or incorrect environment settings often trigger this exception:

  • Workspaces: Make sure you’ve set a valid scratch workspace and current workspace using gp.SetEnvironmentValue("scratchWorkspace", yourScratchPath) and gp.SetEnvironmentValue("workspace", yourWorkspacePath). The Union tool creates temp files during processing, and without a valid scratch space, it’ll fail.
  • Overwrite Output: Don’t forget to set gp.OverwriteOutput = true—if your target output feature class already exists, the tool will throw an error instead of overwriting it by default.
  • Coordinate Systems: If your inputs use different coordinate systems, explicitly set an output coordinate system in the environment settings to avoid projection conflicts.

• Verify Licensing & Geoprocessor Initialization
  Ensure you’re properly initializing the ArcObjects license and geoprocessor object before running the tool. A missing or incorrect license can cause silent failures that bubble up as AutomatedException. Here’s a quick example in C#:

  AoInitialize aoInit = new AoInitializeClass();
  aoInit.Initialize(esriLicenseProductCode.esriLicenseProductCodeAdvanced); // Match your license level
  
  Geoprocessor gp = new Geoprocessor();
  gp.OverwriteOutput = true;
  

  Also, make sure you’re releasing COM objects properly after processing (this prevents memory leaks that can lead to odd exceptions in long-running workflows).

• Check for Locked Datasets
  If your input or output files are open in ArcMap/ArcGIS Pro, or being used by another process, the geoprocessor can’t access them. Close any applications holding locks on the data, or make a copy of the inputs to use for processing.

• Run the Tool Manually First
  Test the Union tool directly in ArcGIS Desktop/Pro with the exact same inputs. If it fails there, the issue is with your data or tool parameters—not your code. If it works manually, the problem is in how you’re passing parameters to the geoprocessor (e.g., incorrect file paths, missing required parameters, or passing object references instead of string paths).

• Catch & Inspect Full Error Details
  The generic AutomatedException rarely tells you what’s actually wrong. Wrap your geoprocessor call in a try-catch block to pull detailed error messages from the geoprocessor itself:

  try
  {
      Union unionTool = new Union();
      unionTool.in_features = @"C:\Data\InputFC1;C:\Data\InputFC2";
      unionTool.out_feature_class = @"C:\Data\OutputUnionFC";
      gp.Execute(unionTool, null);
  }
  catch (AutomatedException ex)
  {
      // Pull all error messages from the geoprocessor
      string errorDetails = string.Join("\n", gp.GetMessages(2));
      Console.WriteLine($"Full error info:\n{errorDetails}\nInner exception: {ex.InnerException?.Message}");
  }
  

  The gp.GetMessages(2) call returns all error-level messages from the tool execution—this will almost always tell you exactly what went wrong (e.g., "Invalid geometry in feature 123" or "Output workspace is read-only").

If you share your specific code snippet, I can help pinpoint the exact issue, but these steps should cover most common scenarios that trigger this error with the Union tool.

内容的提问来源于stack exchange，提问作者David