Skip to main content
Solved

Can't create FileGeodatabase with FME Desktop over network

T
Forum|alt.badge.img

I have a workbench that Inputs a fileGDB that has a feature class with just a few points. The output location is generated based on the input with a timestamp added. Savings as a new file gdb (Regular API and the open API) ones both work when saving to local C drive but not anywhere on the network and gives the following error:

"Unable to connect to the File Geodatabase at 'H:\\Temp\\CAD_Test.gdb'. Make sure the correct filename was specified, and that the geodatabase wasn't saved with a newer version of ArcGIS than the one installed locally. The error number from ArcObjects is: '-2147024894'. The error message from ArcObjects is: {}"

Using UNC paths is same result

If I change the file type to .csv I can export over the network no problem, but filegdb fails and don't know why, have the drop table setting set to yes

 

Any ideas?

Best answer by tforward

After much trial and error and tweaking, I was able to get it working:

  • Feature Writer (FGB Open API Only works)
  • Set table handling to "Drop and Create"
  • Set the Template File Geodatabase to "fme_dataset" (This is the input fileGDB)
  • For any attributes you need to use the attribute exposer to bring them over (Don't bring over objectID, it will get created automatically) [I'm trying to figure how to do this dynamically but not sure at moment]
  • Works with UNC paths
  • FME will report that 0 features are written but if you go look at the data it's there.

Do not use the FGB ESRI API it does not work

View original
Did this help you find an answer to your question?

7 replies

redgeographics
Celebrity
Forum|alt.badge.img+48

Are you overwriting an existing FGDB on the network? I have the same issue and usually work around it by deleting the original before running the workspace but it'd be nice if there's a more stable solution.

T
Forum|alt.badge.img
  • tforward
  • Author
  • August 20, 2019
redgeographics wrote:

Are you overwriting an existing FGDB on the network? I have the same issue and usually work around it by deleting the original before running the workspace but it'd be nice if there's a more stable solution.

No, newly created file geodatabase.

mygis
Contributor
Forum|alt.badge.img+12
  • mygisContributor
  • Contributor
  • August 20, 2019

1. Do you have full access on that drive?

 

2. Are ArcGIS and FME compatible? Please check out this article: https://knowledge.safe.com/articles/1517/notes-on-fme-and-esri-versions-and-compatibility.html

 

3. Does the same error occur on that drive when the format is "Geodatabase API"?
T
Forum|alt.badge.img
  • tforward
  • Author
  • August 20, 2019
mygis wrote:

1. Do you have full access on that drive?

 

2. Are ArcGIS and FME compatible? Please check out this article: https://knowledge.safe.com/articles/1517/notes-on-fme-and-esri-versions-and-compatibility.html

 

3. Does the same error occur on that drive when the format is "Geodatabase API"?

I'm not sure I understand. When you say driver to you mean drive? If so, than yes I do have write access to that drive (also tested with exporting new .csv and that works). However, If I save a new file geodatabase to local C drive it works, over the network it does. Yes, is compatible and again it works when exporting to C drive so confirms it. Yes both the regular Api and the open api for filegeodatabase have the same error. My current hacky workaround is to write to the C drive then move it to the correct location after it is created...

mygis
Contributor
Forum|alt.badge.img+12
  • mygisContributor
  • Contributor
  • August 20, 2019
tforward wrote:

I'm not sure I understand. When you say driver to you mean drive? If so, than yes I do have write access to that drive (also tested with exporting new .csv and that works). However, If I save a new file geodatabase to local C drive it works, over the network it does. Yes, is compatible and again it works when exporting to C drive so confirms it. Yes both the regular Api and the open api for filegeodatabase have the same error. My current hacky workaround is to write to the C drive then move it to the correct location after it is created...

is anyone else opening the geodatabase?

Can you drop the tables before writing?

Other possibility, I have read before, is there an antivirus on both machines? Can you disable them and test?

These threads are worth checking out as well.

https://knowledge.safe.com/questions/84633/file-geodatabase-output-in-network-location-issue.html

 

 

there is a similar thread here. https://knowledge.safe.com/questions/46141/overwriting-existing-file-geodatabase.html

 

Can you please share your workspace?

 

 

p.s. thanks for pointing out the typo, it has been corrected.
T
Forum|alt.badge.img
  • tforward
  • Author
  • Best Answer
  • August 20, 2019

After much trial and error and tweaking, I was able to get it working:

  • Feature Writer (FGB Open API Only works)
  • Set table handling to "Drop and Create"
  • Set the Template File Geodatabase to "fme_dataset" (This is the input fileGDB)
  • For any attributes you need to use the attribute exposer to bring them over (Don't bring over objectID, it will get created automatically) [I'm trying to figure how to do this dynamically but not sure at moment]
  • Works with UNC paths
  • FME will report that 0 features are written but if you go look at the data it's there.

Do not use the FGB ESRI API it does not work

T
Forum|alt.badge.img
  • tforward
  • Author
  • August 20, 2019
mygis wrote:

is anyone else opening the geodatabase?

Can you drop the tables before writing?

Other possibility, I have read before, is there an antivirus on both machines? Can you disable them and test?

These threads are worth checking out as well.

https://knowledge.safe.com/questions/84633/file-geodatabase-output-in-network-location-issue.html

 

 

there is a similar thread here. https://knowledge.safe.com/questions/46141/overwriting-existing-file-geodatabase.html

 

Can you please share your workspace?

 

 

p.s. thanks for pointing out the typo, it has been corrected.

I got it working see above

Reply


Helpful Members This Week

Community Stats

30,921
Posts
117,181
Replies
38,725
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.