Skip to main content
Solved

GDB writer works once, then keeps failing


Forum|alt.badge.img
I'm doing a fairly straightforward IFC conversion. It runs once correctly and then every time I try it again, it errors out with the below messages. When I create a new writer it works, but also only once. What's up with that?
  • Dataset template source `<Unused>' for writer GEODATABASE_FILE_1 could not be located
  • Dataset template source `<Unused>' for writer GEODATABASE_FILE_1 could not be located
  • f_72(CreationFactory): Dataset template source `<Unused>' for writer GEODATABASE_FILE_1 could not be located
  • Dataset template source `<Unused>' for writer GEODATABASE_FILE_1 could not be located

Best answer by debbiatsafe

Hi @clickingbuttons

I'm sorry you ran into this issue. Could you try clearing any values for the Template Geodatabase parameter under the Geodatabase writer parameters in the navigator pane? That has resolved the error in the past.

I suspect the behaviour you are seeing is related to a bug that should have been fixed in FME 2018. Which version of FME are you using?

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

2 replies

debbiatsafe
Safer
Forum|alt.badge.img+20
  • Safer
  • Best Answer
  • May 18, 2018

Hi @clickingbuttons

I'm sorry you ran into this issue. Could you try clearing any values for the Template Geodatabase parameter under the Geodatabase writer parameters in the navigator pane? That has resolved the error in the past.

I suspect the behaviour you are seeing is related to a bug that should have been fixed in FME 2018. Which version of FME are you using?


Forum|alt.badge.img
debbiatsafe wrote:

Hi @clickingbuttons

I'm sorry you ran into this issue. Could you try clearing any values for the Template Geodatabase parameter under the Geodatabase writer parameters in the navigator pane? That has resolved the error in the past.

I suspect the behaviour you are seeing is related to a bug that should have been fixed in FME 2018. Which version of FME are you using?

It somehow fixed itself over a weekend. Version was whatever comes with ArcGIS Pro 1.8(?).

 


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