Deployment

We are converting a number of GIS-focused Automations in FME Flow 2024.0 to use the new SDE Database Connections instead of the old PATH resource.  FME Flow is returning an error when attempting to read the new database connection properties: ‘An error occurred while attempting to retrieve the connection parameters from the connection file’ For each of the FME Flow Database Connections, we used an FME Resource, ‘SDE_GISD’, for the path reference for the connection file.  We found if we use a UNC path instead of the FME Flow resource it works as expected.  Is this a limitation or are we doing something wrong?Connection works as expected on local host, local server host, and with UNC path for the database connection within FME Flow.  Just not with using a Resource path in the connection.Error:315 2024-7-31 11:51:25 | Opening the Esri Geodatabase reader 316 2024-7-31 11:51:25 | An ArcGIS license is

We migrated from FME Server 2022 to FME Flow 2024 (FME Flow 2024.2.3Build 24825 - win64) and we have imported the 2022 backup successfully. When I now want to create a new project and I want to add a Resource path to the Project, the list of Resources to chose from is empty.I’ve looked at the request and the response contains the list of resource paths at the highest level but this list is not displayed in the UI. Is there a known issue with this release or a config setting that we missed?Request URL:https://<fmeserver>/fmeapiv4/resources/connections?limit=100&offset=0&suppressBroadcastError=false&cb=1744107685909Request Method:GETStatus Code:200 OKResponse : {    "items": [        {            "name": "FME_SHAREDRESOURCE_BACKUP",            "owner": "admin",            "ownerID": "fb2dd313-e5c

Morning all,I’m trying to create a workspace that works both on FME Flow & Form. I’m using the FME_JOB_ID to determine what the workflow is running on.If its FME Form I’m setting the filepath to a shared drive. For Flow I’m trying to set it to the FME_SHAREDRESOURCE_TEMP folder to produce a data download.If I hard code the parameter in the writer to $(FME_SHAREDRESOURCE_TEMP)@Value(_FILEPATH) its fine, but I can’t do this as the file will not then post to a shared drive.If I try and set the FME_SHAREDRESOURCE_TEMP in the workspace to push that to my parameter and add it to the created filepath FME no longer produces the downloaded zip file.I’m setting the FME_SHAREDRESOURCE_TEMP to the url defined on Flow - which in this case is something likehttps://-myserverlocation-/fmeserver/resources/browse?path=FME_SHAREDRESOURCE_TEMP&name=TempIs this correct, or should I be using a shorter, relative path? EDIT: Sorry just

Hello,I recently received a new fme flow 2024 from my IT department and something keeps failing when i run a large workspace(1096704 kB), i get no error but the workspace fails.This same workspace runs in fme flow 2023 without any problem.Here are my system details,FME FLOW 2023System Status: 43.39 GB of disk space available in the FME temporary folder (C:\Users\Username\AppData\Local\Temp\fmeengines\{enginename}_Engine1)System Status: 30.00 GB of physical memory availableSystem Status: 126.00 GB of virtual memory availableFME FLOW 2024System Status: 65.31 GB of disk space available in the FME temporary folder (C:\Windows\TEMP\fmeengines\{enginename}_Engine2)System Status: 30.00 GB of physical memory availableSystem Status: 126.00 GB of virtual memory availableI have been reading around but i have not been able to pint out where the problem actually lies. How

A simple workspace created in Workbench 2024.1.1 with three FME Flow deployment parameters - a web connection using Esri ArcGIS Portal (Template), a DB connection to PostgreSQL and a Text deployment parameter - works perfectly in Workbench as well as a manual or scheduled job once published to Flow.An FME Flow app created from that workspace fails trying to access the Web and DB deployment parameters. The Text parameter works fine. The app fails whether or not authentication is required to run the app. The Web and DB connections and the associated deployment parameters have been shared with fmeuser and fmeguest roles with Read access to try to fix the problem - but that did not help.Web connection error: 2025-3-20 14:46:38 | FME Flow error: `FME Flow error: `Unauthorized request by user due to lack of proper permissions for connection: WEB_ARCGIS_PORTAL. Please see: http://fme.ly/zn8''2025-3-20 14:29:41 | ArcGIS Portal Feature Ser

While running a job on FME Flow 2024 Server, the following error occurred:"Unable to connect to the File Geodatabase located at '\vmbltstweu001\FS\TestFME\TestCheckout_ERW.gdb'. Please verify that the correct file path is specified and that the Geodatabase is not saved in a newer version of ArcGIS than the one installed on the server. The error code from ArcObjects is '-2147024891'."Could anyone please help me on that 

I made a flow gallery app with some banners en footbanners. But i did not like them. So i tried removing them. But when i remove them end click OK. They are not removed and come back in the site and in the costumizer.But when i add an item like a logo it saves it oke. But then when i want to remove that also, it won’t.

I’m trying to publish a new app on FME Flow, but there are no services listed to create the app.  If I try open an existing app, it says “You do not have access to the "fmedatastreaming" service.” I’m logged as a admin with all possible rights.  If I go to services settings, all seems normal.  So Im not able to create any app and practically run any workspace. What could have gone wrong?EDIT:After updating to FME 2024.2.3 the problem stays exactly the same.

Hi! I could use a hand. I'm running an FME workspace that downloads data from ArcGIS Online using 4 HTTPCallers and a Web Connection. The workflow works fine in FME Form 2024, but when I publish and run it in FME Flow 2024.1, it fails.Setup:Using a Web Connection to authenticate (ArcGIS Online). The Web Connection exists in FME Server and is assigned to my user. The Web Connection is correctly assigned in FME Server.Does anyone have experience with this issue? Could it be related to permissions, token handling, or FME Server settings?Any suggestions would be greatly appreciated!

Hi, We are following this instruction Upgrading In Place, On the Same Machine and failing in the last step. what could be wrong? We are upgrading from FME flow 2023.1 to 2024.2  So what about that file: Migration) File "/temp/tomcat/fde0b0779317417da467e76dec4c9027/restServerRestore.fsconfig" does not exist for shared resource "FME_SHAREDRESOURCE_SYSTEM". 

FME server 2020.2 failing with - "Unable to perform any licensing related tasks. This 64-bit version of FME requires 64-bit Background Geoprocessing, ArcGIS Pro or ArcGIS Server". There is already ArcGIS pro installed on same machine and the version of ArcGIS Pro is 2.6. Is ArcGIS server required for this?

Hello you all and perhaps especially ​@LizAtSafe Gone through this tutorial here:Using the Geometry Parameter – FME Support CenterAnd this is of great help, just have one question that I cant figure out the answer to and that is if the selection map can be set as “Inline” by default instead of “Pop up”, as in that the users have the little imbedded selection map by default when accessing the tool?With regards,

We are currently running FME Server 2022.2. on prem (not cloud hosted).  We had been planning on upgrading to the latest, but now even more so with the privilege escalation issue, and there apparently not being a fix for our version….except to upgrade.Looking over the “in place upgrade” portion of the documentation, it seems we can simply backup the configuration files (we’re not using version control yet), do an uninstall of 2022.2, do a fresh install of the latest 2024, and then restore the configuration backup.Are there any known issues with doing this from 2022 to 2024?  I know the product was rebranded in 2023, but the differences I could see between 2022 and 2023 seemed mostly cosmetic for the rebrand.  However, I know 2024 seems to be different.I just really want to dot all my i’s and cross all my t’s, and keep any down time to a minimum.  And know if there are any “gotchas” that can be avoided.Thank you.

Where can we find the download for FME Flow and Form version 2024.2.3?I only see versions 2024.2.2 and 2025.0 in the list of available downloads. Thank you

Build info:FME Flow 2024.2.3Build 24825 - linux-x64running in Ubuntu 24.04.1 LTS AWS KubernetesI have trouble installing oracle client correctly. We are using FME Flow in AWS Kubernetes with helm. I used this dockerfile to install oracle client to the engine pod (this worked in fmeserver 2021): FROM safesoftware/fmeflow-engine:2024.2.3USER rootRUN apt-get update && apt-get install -y \ unzip \ libaio1t64 \ sqlite3 \ software-properties-common && \ apt-get clean && \ rm -rf /var/lib/apt/lists/*RUN mkdir -p /opt/oracle/instantclient_19_26COPY instantclient-basic-linux.x64-19.26.0.0.0dbru.zip /opt/oracle/WORKDIR /opt/oracleRUN unzip instantclient-basic-linux.x64-19.26.0.0.0dbru.zipENV LD_LIBRARY_PATH=/opt/oracle/instantclient_19_26:$LD_LIBRARY_PATHRUN rm instantclient-basic-

We make use of parallel processing within FME Flow 2023.1. However we are struggling to de-bug issues that intermittently occur in the worker processes. I can see that, whilst running, each worker process has a log file, stored under the parent job log. However, this is deleted when the worker process closes, even if it fails. This makes it very difficult retrospectively diagnose any issues.In our FME Server 2021 instance, the worker logs are surfaced in the main job log once complete, which is fine, but I can’t identify any setting to control and replicate this behaviour.Does any one know of a config change that I can make, in FME Flow 2023, to retain these worker logs somehow?

FME Flow 2024.1Workspace set up on FME Form with a web connection configured as a user parameter and only allowing one type of supported service. This works on FME Form as expected. Once the workspace is uploaded to FME Flow, any web connection present within Flow can be selected irrespective of what service this is for. Is this expected behaviour?

We are currently running FME Server 2022.2. on prem (not cloud hosted).  We had been planning on upgrading to the latest, but now even more so with the privilege escalation issue, and there apparently not being a fix for our version….except to upgrade.Looking over the “in place upgrade” portion of the documentation, it seems we can simply backup the configuration files (we’re not using version control yet), do an uninstall of 2022.2, do a fresh install of the latest 2024, and then restore the configuration backup.Are there any known issues with doing this from 2022 to 2024?  I know the product was rebranded in 2023, but the differences I could see between 2022 and 2023 seemed mostly cosmetic for the rebrand.  However, I know 2024 seems to be different.I just really want to dot all my i’s and cross all my t’s, and keep any down time to a minimum.  And know if there are any “gotchas” that can be avoided.Thank you.

 I updated the pfx cetificate file according to this :Configuring for HTTPSBasically updating these lines i server.xml: keystoreFile="<file>"keystorePass="<password>"Now apps complains about REST API? Why? - what to do?What is the realtion between the SSL certificate and the FME flow Rest API? Where to find information about this? 

I updated the pfx cetificate file according to this :Configuring for HTTPSBasically updating these lines i server.xml: keystoreFile="<file>"keystorePass="<password>"Now apps complains about REST API? Why? - what to do?  

Is there any way to cancel a system restore, it appears to be hung at  Unzipping migration package stage for 1.5 hours now.  I think the file system/network glitched during the process.  There is no cancel in the UI, no jobs running.  

We just upgraded our on-prem Flow (from 2023.2 to 2024.2.2) and are now are dead in the water --all scheduled workbenches will not run, but seem to be valid --after restoring from the backup (I even tried reinstalling the successfull backup again, but it failed on the second try).  I then tried re-uploading the workbenches to the new Flow version from the Form workbenches (both old and new versions) but can not access the repositories to save them there to re-schedule them in the new Flow.  Yikes. Help. Please.

This question came up at my office today.   Can I have two FME Flow engines at different versions installed on the same Windows Server?  I’m guessing that the answer is no but I wanted to get official verification on that.

HTML Pages created with FME use an external stylesheet:<html> <head> <title>Report</title> <meta charset="UTF-8"> <link href="https://cdn.jsdelivr.net/npm/bootstrap@4.5.3/dist/css/bootstrap.min.css" rel="stylesheet"> </head> <body> ...... </body></html>This is somewhat of a problem when FME Flow has no access to this location, as HTML pages displayed from FME Flow Apps in that case will show without this stylesheet, thus maiming the layout.Are there alternatives for using this external stylesheet, like placing a copy of it somewhere on the FME Flow machine? Then the <head> of the HTML page could point to this local stylesheet.The stylesheet contains

Hello and happy 2025!Was speculating on feature types selection possibilities when reading as a single merged feature type with a wildcard on flow.My scenario being that a user will drag and drop a DWG to a Flow tool and then that said tool would read it in and then display all the feature types (layers) that said DWG consists of  in a list. Where the user could then check a box in front of each and every layer they need and afterwards select “Run” to start the main tool (which is a conversion into another file format).Thus the tool not converting all features/layers within a file but only a selected few which are selected like one does for example with the “Feature types to read” option in the FeatureReader.Anyone here done this before that wishes to share?