Skip to main content

I have just installed FME Form 2024.0. Previously, I have added the option of sharing my connections by setting up the neccessary registry enties.
When I open the Database Connections in FME Options I get this message:

Which means I have no available Database connections. When I “upgraded” my FME Form installation from 2022.x to 2023.x, this was not an issue.
I also see that my Web Connections have the same issue. Is this expected behaviour from FME Form 2024, have I missed some important steps when upgrading/installing 2024 or is this an error in 2024? My 2024 install is in parallell to my existing 2022.2.8, 2023.2.1 and 2023.2.2 installations.We have customers running different versions of FME, so I need FME Form installations in parallell.

Hi @mgrimnes.  I’m sorry that you’ve encountered an issue with your connections when upgrading to FME 2024.  This is likely related to the improved encryption algorithms introduced in FME 2024.  I’ll do my best to help.  Could you please open up a support case and provide the registry settings (.reg file) from:

  1. Open the Registry Editor and navigate to Computer\HKEY_CURRENT_USER\Software\Safe Software Inc.\Feature Manipulation Engine
  2. Right click on the Feature Manipulation Engine folder
  3. Select Export
  4. this will bring up a dialog that will allow you to save the .reg file

 

 


Support case created with attachments.


Any response to your issue.  I’m having issues with Web connections in v2024.1.2.1.  I’ve had to recreate my AGOL connection (https://support.safe.com/hc/en-us/articles/25407474895629-How-to-Create-an-ArcGIS-Online-Web-Connection-OAuth-2-0), update ArcPro to v3.3.2.  This then allows me to connect to AGOL and view my feature services.  The documentation seems to indicate that the new connection db file created should be good to go but that does not appear to be the case.  


I opened this year’s release for the first time today and I might have run into the similar issue.

We are missing many shared database & web connections with 2024.1.3.  I would appreciate it if anyone can share any work-around or eta of the fix. 


Reply