Houston,
We have a problem with the File Geodatabase writer that requires ArcGIS (not the API version). It performs differently in different virtual environments (Citrix) with different FME versions, on the same File Geodatabase. We suspect that the differences in the virtual environments are the cause of this, because the desired functionality is offered in all FME versions. We'd like to know which parts of the ArcGIS Desktop installation are used by FME, when writing to a File Geodatabase, in order to get to the bottom of the issue.
The details of the situation are as follows. As mentioned, we have two different virtual environments:
- A production environment with FME 2019 32-bits served in a "bubble". This is combined with ArcGIS Desktop 10.6.1, in a direct install (no bubble).
- A testing environment with FME 2019 64-bits and ArcGIS Desktop deployed the same way as the production environment
In the production environment, the File Geodatabase writer does not work* when the desired feature class (fc)does not exist and Table Handling is set to "Create if Needed". (This is what we'd like to achieve.)
Neither does it work* when the fc does exist and Table Handling is se to "Drop and create".
It only works when the fc exists and Table Handling is set to either "Truncate" or "Use existing".
In the testing environment, all works fine.
There is no reason to think that the 64-bit version should make the difference, since the functionality is offered in both. So we fear that deploying 64-bit FME in production will not solve the problem. Before we try that, we'd like to besure it does.
Rather we suspect that some permission is missing that allows for creation of new feature classes in a File Geodatabase, in the production enviroment. Or there could be a different cause altogether.
Where do we look?
Any suggestions are welcome.
(Mind you: I'm not asking for a workaround.)
Kind regards,
Ferdinand.
*What happens is FME.exe keeps running endlessly without progressing beyond the opening of the File Geodatabase for writing. Here's the last part of the log that is produced before I stop the workbench:
----
Creating writer for format: Esri Geodatabase (File Geodb)
Trying to find a DYNAMIC plugin for writer named `GEODATABASE_FILE'
FME API version of module 'GEODATABASE_FILE' matches current internal version (3.8 20190820)
FME Configuration: No destination coordinate system set
FME API version of module 'GEODATABASE_FILE' matches current internal version (3.8 20190820)
Writer `GEODATABASE_FILE_1' of type `GEODATABASE_FILE' using group definition keyword `GEODATABASE_FILE_1_DEF'
FME API version of module 'GEODATABASE_FILE' matches current internal version (3.8 20190820)
An ArcGIS license is already checked out. The product checked out is 'Standard'
Installed ArcGIS version is '10.6'
Connected to the File Geodatabase at 'LANDMETEN_OPLEVERING.gdb'
File Geodatabase release: '10.0'
Fast deletes enabled
The 'HAS_Z_VALUES' keyword is set to 'AUTO_DETECT'. With the exception of MultiPatch feature classes, the dimensionality of new feature classes will be based on the first feature written to the feature class. (Features with no geometry are considered 2D)
A default z-value of '0' will be used for all 3D features where z-values are not provided
Geodatabase Writer: Not simplifying geometries being written to the Geodatabase
----
