Cannot create a table using any FileGDB created by ArcGIS Pro 2.3.2
If we use a File GDB which was created by ArcGIS Pro 2.3.2. an exception "The row contains a bad value" occur when calling Geodatabase::CreateTable. All our Unittests failed with the File GDBs created by ArcGIS Pro 2.3.2. Is there any known incompatibility?
I'm not aware of any issues with File Geodatabases created with ArcGIS Pro 2.3.2. I'll take a look.
We have started seeing the same or similar issues with using ArcGIS Pro 2.3 and now Pro 2.4 created File Geodatabases.
- Can not delete a feature class/table if the GDB file is locked. We have noted that the ArcGIS Pro SDK GeoProcessing tool (delete_management) can
** Start ArcGIS Pro,
** From the Catalog pane, Add Database, select an existing GDB file
** Display a feature class on the map. There is a .lock file in the .GDB directory
** If we attempt to delete another feature class in the same GDB file via the FileGDB SDK function GeoDatabase.
Delete (String^ path, String^ datasetType), it will throw “Cannot acquire lock” exception. The same operation will work if we call “delete_managment: GP tool - Could not write to GeoDatabase created by ArcGIS Pro
** Start ArcGIS Pro
** From the Catalog pane, New File GeoDatabase
** If we attempt to create a feature class in the newly created GDB file using the FileGDB SDK function GeoDatabase.
CreateTable (), it will throw an exception. Again GP tool works - FileGDB SDK crashed if CreateTable fails ** If CreateTable fails, FileGDB SDK threw “Cannot access a disposed object” exception and then crash
Any ideas if this is going be fixed? Since then has been no updates since the OP in May?
Any progress on this issue? We are currently staying with the version 1.4 and we are creating our own FileGDB in ArcGIS Pro.
We are experiencing the same problem with FileGDB API and File Geodatabases created in ArcGIS Pro 2.3 and above. File Geodatabases created in ArcGIS Desktop work fine. Is there any progress on the issue?
I finally reproduced the issue. I'll enter a bug and see when we can get it on the schedule.
Any news about this issue?
Any news about this issue?
I'm still getting this issue using ET GeoWizards 12 in ArcGIS Pro 2.8.3. Do we have a timeline for getting this fixed? Or a BUG# to monitor?