Deployment

Hi, thereDoes FME Desktop 2022.2.2 and FME Server 2022.2.2 use any of the below listed .NET components?Microsoft .NET 6.0.29 - Windows Server Hosting Microsoft .NET Runtime - 6.0.29 (x64) Microsoft .NET Runtime - 6.0.29 (x86) Microsoft ASP.NET Core 6.0.29 - Shared Framework (x64) Microsoft ASP.NET Core 6.0.29 - Shared Framework (x86)If yes, will the upgrade of these components to .NET 8 will cause issues?

FME(R) 2023.1.1.0 (20230928 - Build 23631 - WIN64)I have a simple scripted parameter script in workbench to return the value of a deployment parameter and I’m wondering if there’s a bug in the interface. When I drag a user parameter onto the script canvas the code generated contains FME_MacroValues, eg.FME_MacroValues['SomeUserParam']If  I drag a deployment parameter, dpTest, onto the script canvas the code generated looks like$(dpTest)Here’s the script. The commented code fails; if I manually correct $(dpTest) to FME_MacroValues['dpTest'], it runs: # Get the archive folder from deployment paramimport fme#arch = $(dpTest)#return archreturn FME_MacroValues['dpTest'] Is this a bug? Thanks.

Planning to upgrade the OS After that, How to setup the FME server and configure it ?How to Migrate the Existing FME server to New machine?How to move forward with new machine?   

Hello Community,As clear from the title I want to know dimensions, although file sizes are mentioned but that is not helpful at all. I don't wanna trial and error the sizes to find a perfect one.Maybe I am missing something, please let me know.Also when I add logo it shows up in center I want to be able to adjust its position. Thank for your answer and patience.

Hello, We are setting up a fault tolerant FME flow setup where in we have decided to use AWS RDS as FME Flow database component. First if all, is it right thing to use RDS or do we need to have a separate postgres instance installed on an EC2 machine ?Secondly, if we can use, please let me know the steps or any resource material to setup the fme flow withg RDS postgres as database component. Thanks.  

Hello, Need to know in detail on how FME Flow and ArcGIS Server licensing works. If there are 16 dynamic engines being run with 16 ESRI jobs, then does it mean that fme flow uses 16 ArcGIS server licenses? Thanks,Rajan

We used to need custom python on FME-Server. I’m no system administrator, but I had found out how to install it (Using Python with FME Flow (safe.com)).Now we updated to FMEFlow 2024 and we don’t need custom python anymore, so I didn’t install it. but obviously it is still registered somewhere that we used to need a different python.dll, for I get the warning “The User-specified library ...python37.dll could not be loaded”. How can I reset everything to default-settings? I tried it with this: <FMEFlowDir>Server/fme/fme.exe APPLY_SETTINGS SYSTEM "Python/Use Custom Python 64" falseand restartet the FMEServer-services, but the warning remains in the log.Thanks, Vera Update:I ran this command as well to reset to the standard python.dll:<FMEFlowDir>Server/fme/fme.exe APPLY_SETTINGS SYSTEM "Python/Python Interpreter 64" "C:\Program Files\FMEFlow\Server\fme\fmepython312\python312.dll"Now I get this warning:The PYTHONHOME `...' for the user-specified Python interpreter set through

A Feature Information Window pops up when starting Form 2023.2.3.0. This was an install package from our IT group so there could be something from packaging causing this.

Hi all,In our company we are using FME Flow, it's works great.Except with one workspace we get some errors. On the desktop version is works flawlessly! The error we get is about a plugin (STUF-GEO) that cannot be loaded:144 2024-7-3 21:48:01 | File C:\Program Files\FMEFlow\Server\fme\metafile\STUF-GEO.fmf could not be opened 148 2024-7-3 21:48:01 | Could not load module 'C:\Program Files\FMEFlow\Server\fme\plugins/STUF-GEO.dll' : 'The specified module could not be found' 149 2024-7-3 21:48:01 | Could not load module 'C:\Program Files\FMEFlow\Server\fme\STUF-GEO.dll' : 'The specified module could not be found' 150 2024-7-3 21:48:01 | This FME edition does not recognize the `STUF-GEO' reader. Please ensure that the current platform supports this reader, the reader name is spelled correctly, and that you have installed all required plug-ins 151 2024-7-3 21:48:01 | This FME edition does not recognize the `STUF-GEO' reader. Please ensure that the current platform supports this

Good morning all, I have a working workspace, I run it from FME FLOW and it gets stuck after a while.It doesn’t show any error or warning.I suppose that the problem could be due to a CSV WRITER, it seems that the process got stuck seding the result of a filter to the CSV WRITER. Then I found the solution, altough the workspace was run from the admin user and the user is the owner of data folder, I provided the authorization to data folder to admin group.The task ended with no errors.

We have recently installed FME Flow and FME form 2024, while trying to publish fme workspace, connection get established but after closing and opening FME Form again it failed to connect to FME Flow. Is there restriction from license side or some hanging connection issue which is not closed after first connection, I tried restarting application and even serve but it didn’t help . I have attached screenshot.

Good morning,I amplanning to upgrade FME 2018 server to FME 2023 , I have 200-250 ETL in 2018. Usually how many ETLs in 2018 will be impacted on the average when upgrading to FME 2023.  On the average, how long it takes to upgrade from FME 2028 to FME 2023, the whole process. I know it depends on the organization setup but just in general how long it takes to upgrade. Thanks

Hey peeps, I'm currently trying to import a project to FME Flow. The problem is that when I only try to select the relevant items for that environment, it still imports and overwrites the other categories. For database connections I don't experience any problems. There is an option to choose whether to overwrite the existing ones or not on the third page. But for all the other items it seems to be all or nothing. Any advice that doesn't tell me to exclude the items from the project, would be welcome.

My co-worker doesn’t see the popup 'Register Service' whenever they publish a workspace to FME server. I generally see one and the service ‘Job Submitter’ is ticked. Does my co-worker need this to run their workspace on the server? 

In the 2024.x versions of FME Flow, will the URL continue to contain ‘fmeserver’ or will it be changed to ‘fmeflow’? Example: https://mydomain/fmeserver vs. https://mydomain/fmeflow If, by default, the URL will continue to have ‘fmeserver’ in it, can we change that in a configuration file?Asking as we may need to run both FME Server 2022.x and FME Flow 2024 in parallel while migrating some legacy 32-bit Esri solutions. Thanks,Mark

A few co-workers have left the company and have forgotten to share their workspaces on the FME server with myself and others. Is there a way for the FME admin to share those workspaces that are being used in automation and schedules with us?

Hello,  I’m building a workflow to process multiple input files. When running from FME Flow some of the files are read correctly from this location:  /data/fmeflow/resources/system/temp/upload// but for some of them I’m getting this error: File does not exist: $(FME_DATA_REPOSITORY)/When running from FME Form I’m getting the same error: File does not exist: $(FME_MF_DIR)For some reason this this happens only when more than 21 files are processed (does not matter the size of the file). Do you have any idea how to fix it?  Thank you.  

We have FME Flow 2023.2.1 installed, we have chosen PostgreSQL running in AWS RDS as our database. This has been setup and configured at installation using the silent Windows installation method.We are seeing vulnerabilities on the server FME Flow is installed on relating to Microsoft OLE DB Driver. This seems to have been installed as part of FME Flow. Is the Microsoft OLE DB Driver a required driver if we’re not using SQL Server?If so, can this be removed or do we now need to manage patching of this driver?

Hello,I am submitting job through my FME api and not keeping job id in application, Though I want to check status of my job through Published parameer which is always unique.I know we can get all jobs and then we can do filtering but it will bit costly operation hence I dont want to do that.How to track Submitted job status with Published parameter? (Eg: I am supplying  “batchId” as published parameter and want to track job status based on my that batchid only)  

I have set up a project in our test environment containing two workspaces in a repository, a workspace app and an automation. Workspaces use a resource\data subfolder. The automation writes data to a database through a database connection. All this is set up with my admin account.When I try to export the project to move to our production environment I get the error: “Exporting the project is not permitted. This project contains items that don't exist or are inaccessible by you.”In the project I have added the automation, connection, repository, resource path and workspace app, 5 items in total. I have verified that the resource\data path is migrateable as per the first note here: https://docs.safe.com/fme/html/FME-Flow/WebUI/Exporting-Importing-Projects.htmAny tips on why I am not allowed to export? The items defined in the project all exists and as an admin I have access to all items...

Out of curiosity, does anyone know if there is a limit to the number of jobs which can be queued on FME Server/Flow?

Hi,We cannot get FME to work behind an AWS loadbalancer.Using fme-flow-2024.0.2.1-b24217-linux-x64~ubuntu.22.04.runDeploying FME behind an AWS Application load balancer with a HTTPs listener, works for signing in and browsing https://.../fmeserver/. However, when testing the installation using the following instructions, this error is returned “400 - Bad Request The plain HTTP request was sent to HTTPS port”https://docs.safe.com/fme/html/FME-Flow/AdminGuide/Test-Installation-Linux.htmThe FME server has a security group that only allows HTTP and SSH connections and so connections to port 443 are not possible. The Browser issues two requestshttps://.../fmeapiv4/workspaces/Samples/austinApartments.fmw/encodeparametervalues-> 200https://.../fmeserver/run/form/fmedatadownload/Samples/austinApartments.fmw-> 400 The AWS Application Loadbalancer terminates the HTTPs connection and forwards to FME on HTTP port 80. Nginx receives these requests on HTTPNginx10.xxx.1.144 - - [21/May/2024:09:

We are updating from FME 2022 to 2024. On our Staging-Server FME 2024 has already been installed.I tried to run some of our Workspaces there, but they failed as the connection to the database could not be established.I finally found out, that the problem was, that we are using embedded connection parameters and not database connections, if I use database connections, it works.As we never used database connections, none of our workspaces will run on FME Flow 2024, unless we change to database connections. This means, we have to edit every workspace with a connection to a database, that’s a lot of work…!Do we really have to do this and if so, is there an efficient way to do it?

Does the fanout expression is available on FME FLOW 2023 ? My FME Workbench works well on FME Server 2020, but on FME Flow, I got an error that mention that I don’t have the permission to write in the specific folder, but I have that permission.  For example, the Destination Fanout is $(FME_SHAREDRESOURCE_DATA)/temp and the Fanout Expression is /gpkg/test_@Value(attribut).gpkg.zip. I got this error message:MULTI_WRITER: Failed to create folder '/gpkg/test_hello.gpkg.zip'. Please ensure you have sufficient permissions to create this folderIt seems like Destination Fanout is not taken into account.

According to the GE Documentation Smallworld 5.3.3. has been officially tested/validated with FME 2023 version 2023.1.2.We would like to upgrade our current FME Server and FME Desktop 2021.2.x 32 bit.To consider FME 2023.2.3, I would like to know if there are any modification to Smallworld Translators between the versions, 2023.1.2 & 2023.2.3?