Skip to main content
Question

FeatureWriter - Esri Geodatabase (File Geodb Open API) Random Failures

  • November 25, 2025
  • 1 reply
  • 26 views

pgammie
Contributor
Forum|alt.badge.img+7

I’ve been struggling with the File Geodatabase Open API FeatureWriter in FME. When I create a new file geodatabase from scratch, everything runs successfully. However, when I switch the FeatureWriter to Drop and Create, I encounter random failures with the error:

Geodatabase Error (-2147467259): General function failure

Here’s my setup:

  • The workbench consists of a series of Oracle SQLExecutors that read each table, followed by a FeatureWriter to convert the data into feature classes in the file geodatabase.
  • I originally used a dynamic workspace, but after seeing this error (and reading advice to limit the number of features processed dynamically), I changed the design so each table is processed in series.
  • The failures occur at different FeatureWriters each time, so it’s not tied to a specific table.
  • I tried using Truncate instead of Drop and Create (since truncating is better for avoiding file locks), but it was very slow, so I abandoned that approach.
  • As a workaround, I check for lock files at the start of the run and send an email alert if one exists.

Has anyone else experienced this issue with Drop and Create? Any suggestions for improving stability?Unfortunately it is not a possibility to license our FME Server for ESRI at this time. I could break the workbench up and do a workspace runner workbench if it is still a case of the writer just not being able to handle the number of features though I had thought that should have been resolved by running it in series. Appreciate any advice. 

1 reply

desiree_at_safe
Safer
Forum|alt.badge.img+16

Hi ​@pgammie!

Just to narrow down things a bit I do have a few questions.

  1. What version and build of FME are you using and what’s your environment/OS?
  2. Is this something that looks isolated to just the FeatureWriters? I understand the FeatureWriter allows more control over when you write data, but I’m curious if it’s an issue with the writer format itself.
  3. How often does the error happen? 

Would you be willing to share a sample workspace and log file with log debug enabled? 

If you haven't already, it might be helpful to open a support case as well, especially if you aren’t comfortable sharing that log file here! Here’s where you can submit a ticket so that our team can look into this further