Skip to main content
Question

Error - 2147219115 when writing to the File Geodb Open API

  • February 14, 2023
  • 7 replies
  • 362 views

ruthvd
Contributor
Forum|alt.badge.img+1

Writing to an Esri Geodatabase (File Geodb Open API) fails with this error: ‘Geodatabase Error (-2147219115): The row contains a bad value. 

There's an empty table created instead of a point layer.

The error suggests that something's wrong with the schema, but I can't find the cause. The issue stays even with only one feature and limited number of attributes.

Writing the result to a shapefile or to SQL works fine.

 

FME version is 2022.1 

 

Anybody had similar issues with the Esri Geodatabase (File Geodb Open API) writer and knows how to solve this?

 

Thanks,

 

Ruth

 

 

7 replies

Forum|alt.badge.img+2
  • February 14, 2023

@ruthvd​  If you can include a small sample of the dataset and your workspace that might help track down the cause of the issue. You might have a reserved word in your schema


ruthvd
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • February 15, 2023

Thanks for the suggestion Mark!

 

In the meantime I did some more tests. It turns out that the issue is not related to the schema but to the File Geodatabase.

 

Writing to a File Geodatabase created with ArcCatalog (pre-ArcGIS Pro) works.

Writing to a File Geodatabase created with FME works.

Writing to a File Geodatabase created with ArcGIS Pro generates the error.

 

The hypothesis now is that the open API feature writer is not compatible with File Geodatabases created in ArcGIS Pro. Is that possible?

 

 

 

 


Forum|alt.badge.img+2
  • February 15, 2023
ruthvd wrote:

Thanks for the suggestion Mark!

 

In the meantime I did some more tests. It turns out that the issue is not related to the schema but to the File Geodatabase.

 

Writing to a File Geodatabase created with ArcCatalog (pre-ArcGIS Pro) works.

Writing to a File Geodatabase created with FME works.

Writing to a File Geodatabase created with ArcGIS Pro generates the error.

 

The hypothesis now is that the open API feature writer is not compatible with File Geodatabases created in ArcGIS Pro. Is that possible?

 

 

 

 

@ruthvd​ Yes - it is probably dependent on the version of FME you are using whether the ArcPro File Geodb is compatible with the FME File Geodb File API writer


ruthvd
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • February 17, 2023

It makes sense that older FME versions are not compatible with newer ArcGIS Pro versions.

In this case however, I created the filegeodatabase in ArcGIS Pro 2.8.8 and the FME version is 2022.1


egge
Contributor
Forum|alt.badge.img+14
  • Contributor
  • February 17, 2023

The cool thing about the Esri Geodatabase (File Geodb Open API) Reader/Writer is, that it is based on the File Geodatabase API. So, No additional software is required to use this format :-) , but less functionality is available than with some other Esri Geodatabase formats. :-( You say that the File Geodatabase you are writing to has been created with ArcGIS Pro. So, I guess that somewhere under the hood this fgdb is using functionality not supported by the open API...

But hey, If you have ArcGIS Pro running on your FME machine you might just use the Esri Geodatabase (File Geodb) Writer instead.

HTH,

Egge-Jan


Forum|alt.badge.img+2
  • February 17, 2023

@ruthvd​ It is an issue with the API used for the FME File Geodb API format. At this point it is not compatible with File Geodatabses that have been created using ArcGIS Pro 3.x


ruthvd
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • February 20, 2023
markatsafe wrote:

@ruthvd​ It is an issue with the API used for the FME File Geodb API format. At this point it is not compatible with File Geodatabses that have been created using ArcGIS Pro 3.x

@Mark Stoakes​ That's what the compatibility table says. But this case indicates the writer also not to be compatible with lower ArcGIS versions , like version 2.8.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