Skip to main content
Question

Issue Writing to ArcSDE with Geodatabase Writer in FME Flow 2024.2


andrewj74
Supporter
Forum|alt.badge.img+6

We’ve recently upgraded to FME Flow 2024.2 and have started encountering an issue where some of our processes fail to write to ArcSDE using the Geodatabase writer. The error message appears, but I can’t determine the root cause.

Some processes are able to write to the SDE consistently, while few others mostly fail—though they have occasionally succeeded. I’ve tried re-uploading with various ArcGIS default settings, but it doesn’t seem to make a difference.

We’re currently using ArcGIS Desktop 2022.

Any insight would be appreciated.

 

2025-7-7 09:44:12 | Unable to perform any licensing related tasks. Please check your Esri ArcGIS Compatibility workspace parameter, found in Navigator -> Workspace Parameters -> Translation. This 64-bit version of FME requires ArcGIS Desktop along with 64-bit Background Geoprocessing; ArcGIS Pro; or ArcGIS Enterprise. Refer to this this article http://fme.ly/qua for more details

 

 

4 replies

crutledge
Influencer
Forum|alt.badge.img+33
  • Influencer
  • July 7, 2025

Hi ​@andrewj74 That error indicates that the ESRI license FME has is basic and is not at the level required to write data to an ESRI Enterprise GDB. When you say “We’re currently using ArcGIS Desktop 2022.” do you mean FME Form 2022? If so be sure to upgrade to the same version as Flow, upgrade your workbenches and re-publish your workbenches. Form and Flow should be the same version.

Hope that helps.


andrewj74
Supporter
Forum|alt.badge.img+6
  • Author
  • Supporter
  • July 7, 2025

@crutledge  thanks for the reply. Sorry by desktop i mean “Form”. 

 

I always thought the FME flow was backwards compatible so it was ok if flow was ahead of form in terms of versions. We are planning to upgrade form but this is still a few month off. 

The strange thing is that it works for some processes all the time (so far) but there are a hand fall that mostly cause this error, so i would think the licence is fine. 


nielsgerrits
VIP
Forum|alt.badge.img+54

andrewj74
Supporter
Forum|alt.badge.img+6
  • Author
  • Supporter
  • July 8, 2025

Thanks all - Sorry it was the Esri compatibility setting, i was changing the default Arc setting and not the setting  in the translations…. However i am still confused that it did not always fail for the same workbenches.


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