Introduction
When working with FME, encountering unexpected behaviors or limitations can be frustrating. To help navigate these challenges, this article provides a comprehensive list of known issues affecting all currently supported versions of FME.
Each issue includes details on its impact, available workarounds, and whether a fix has been implemented. Our goal is to ensure transparency and provide solutions wherever possible, so you can keep your workflows running smoothly.
If you encounter an issue not listed in this article or have any questions about a known issue, please contact the Safe Software Support team.
Known Issues in FME 2022.0 to FME 2025.x
For a list of issues for retired versions of FME, see Known Issues in Retired Versions of FME.
| Feature | Product | Description | Workaround | Affects | Status |
|---|---|---|---|---|---|
| Web Connections | FME Form |
When FME Flow is used as the connection storage location in FME Form, users without permission to manage connections can see all web services in Form. |
While visible, the web services remain uneditable without the necessary access. Secrets are masked. If visibility is a concern, please use a personal (default) or shared connection database. |
2025.0 |
Unresolved |
| Database Connections | FME Form |
When FME Flow is used as the connection storage location in FME Form, users without permission to access connections can see database connection details when they have only run access. |
Note that, while visible, the database connection details remain uneditable without the necessary access. Passwords are masked. If visibility is a concern, please use a personal (default) or shared connection database. |
2025.0 |
Unresolved |
| Engine Management | FME Flow |
After upgrading an FME Flow express installation to 2024.0 or later and restoring a backup containing engine assignment rules, jobs go to the queue and won't run. |
Please see Known Issue: Engine Name Change to Localhost Causes Jobs to Queue |
2025.x 2024.x |
Unplanned |
| Transformer Attributes | FME Form | Transformers have attributes missing that are unexposed attributes that were previously exposed. Workspaces should continue to run as expected. However, during authoring, attributes appear to be missing, but they are unexposed. FMEFORM-33479 |
While authoring a workspace with an affected transformer, AttributeExposer can restore the expected schema For existing workspaces, run via command line or with FME Workbench despite the warnings. |
2025.x |
Unresolved |
| Version Control / Upload Workspace | FME Flow | Upon uploading a workspace to FME Flow and committing a version to version control, the user sees the following error: Publish Failed (Not Authorized) - Ensure that credentials are correct, and that user has sufficient privileges. | Grant the user Manage Permissions to Version Control. |
2024.x |
Resolved 2025.0 |
| Web Connections | FME Form |
When FME Flow is used as the connection storage location in FME Form, OAuth 2.0 web connections created from web service templates cannot be used in their respective readers, writers, and transformers. FME Form may also crash when attempting to edit OAuth 2.0 web services. |
If you need to use OAuth 2.0 web connections, please use a personal (default) or shared connection database. |
2025.x |
Unresolved |
| AttributeManager | FME Form | When attempting to change a large number of attributes all at once from the AttributeManager will cause FME to crash |
Upgrade to 2025.0 or see Known Issue |
2024.x 2023.x |
Resolved 2025.0 |
| REST API V3 | FME Flow | FME Flow REST API V3 doesn't return a resultDatasetDownloadUrl when a job is submitted | Jobs must be submitted through the Data Download service to obtain a data download URL. Please see: Known Issue: FME Flow REST API V3 Doesn't Return a resultDatasetDownloadUrl |
2025.x 2024.x 2023.x 2022.x 2021.x 2020.x 2019.x 2018.x 2017.x |
Unplanned |
| GoogleVisionConnector Transformer | FME Form FME Flow |
Transformer fails due to "ImportError: no module found named distutils" at the start of the translation FMEENGINE-84233 |
Upgrade Google AI Services FME package to version 1.6 or newer |
2024.x |
Resolved Upgrade Package |
| GoogleCloudPubSubConnector Transformer | FME Form FME Flow |
Transformer fails due to "ImportError: no module found named distutils" at the start of the translation FMEENGINE-84233 |
Upgrade Google Cloud PubSub FME package to version 2.5 or newer |
2024.x |
Resolved Upgrade Package |
| Encryption | FME Flow | A job with a database connection fails to run on FME Flow. "Encryption Error: AES Decrypt finalization failed" FMEFLOW-21215 |
This is the same root cause as FMEFLOW-23068. Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” |
2023.x |
Resolved 2024.0 |
| Encryption | FME Flow | Changing system encryption settings results in "Error: COM.safe.fmeserver.api.FMEServerException java.lang.illegalArgumentException: Illegal base64 character 3c" FMEFLOW-21215 |
This is the same root cause as FMEFLOW-23068. Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” |
2023.x |
Resolved 2024.0 |
| Projects | FME Flow | Imported projects and project contents need to be shared by an admin if the project was imported by a non-admin user. FMESERVER-17957 |
See Known Issue: Importing a fsproject File Requires an Admin to Grant Permissions to the Project |
2025.x 2024.x 2023.x 2022.x 2021.x 2020.x |
Unresolved |
| Backup and Restore | FME Flow | Restoring a backup from 2020 or 2021 will not restore the Tools repository (which may contain user-created workspaces) and presents no errors in the logs FMEFLOW-21520 |
1. Before backup, publish workspaces to a different repository, then after restoring, create the Tools repository and re-publish workspaces there 2. If access to the source server is lost, open the fsconfig file by renaming it to a .zip extension, find the workspace in the files folder, and re-publish to the new instance (after creating the Tools repository) |
2025.0 2024.x 2023.x 2022.x 2021.x 2020.x |
Workaround |
| Automations | FME Flow | When a dynamic workspace with automatic retries is configured within a split-merge block, multiple actions are taken and are not correctly merged when exiting. I.e. for each retry, a failed message will be logged even if a successful run is reached. FMEFLOW-17795 |
None currently. Regular workspace actions act as expected, as well as dynamic workspaces outside of Split-merge blocks |
2025.x 2024.x 2023.x 2022.x 2021.x |
Unresolved |
| User Parameters | FME Flow | The FILE/URL published parameter with the configuration of Path Selection > Single Path behaves differently on Workbench vs Server, causing some translations to fail. FMESERVER-16829 |
Change Single Path to Existing Path in the parameter manager on FME Desktop. Or change the FILE/URL parameter to a text parameter. |
2025.x 2024.x 2023.x 2022.x 2021.x |
Workaround |
| FME Flow Apps | FME Flow | Jobs do not route to the correct queue if a routing rule based on role is used and the job is submitted via an FME Flow Workspace App with authentication enabled. FMEFLOW-23263 |
This is limited to workspace apps. If feasible, set the rule based on user instead of role. Otherwise, choose a different property to route the job or have authenticated users submit the job via Run Workspace instead. |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| Jobs | FME Flow | Job fails with the error "Source dataset does not exist" if an input file is uploaded as a temporary upload when running a workspace on the Run Workspace page and the same filename, but a different case, is used (for example, file.txt and FILE.txt) FMEFLOW-23965 |
Rename the input file before uploading it |
2024.x 2023.x 2022.x |
Resolved 2025.0 |
| Web Connections | FME Flow | <p data-pm-slice="1 1 []"> If you remove a "parent" web service the "child" web service will also disappear FMEFLOW-19667 |
If child web services are required, they will need to be re-uploaded separately. |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| Data Inspection | FME Form | 3D mode is unavailable when viewing data in Visual Preview or FME Data Inspector when FME is installed on a virtual machine | See Known Issue: 3D mode unavailable when running FME Desktop 2022+ on a virtual machine |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| ArcGIS Online FeatureWriter Transformer | FME Form | ArcGIS Online Feature Writer - older workspaces opened in FME 2022.0 or newer have their parameters reset FMEDESKTOP-13560 |
See Known Issue: ArcGIS Online Feature Writer - older workspaces opened in FME 2022.0 or newer have their parameters reset |
2025.x 2024.x 2023.x 2022.x |
Unplanned |
| Publishing to FME Flow | FME Form FME Flow |
When publishing a workspace to FME Server with a web connection that uses Windows Authentication, only the 'Samples' repository is available for selection, even though the user's permissions grant them access to additional repositories on FME Server. FMEFORM-32432 |
Disable the guest account on FME Server |
2024.x 2023.x 2022.x |
Resolved 2025.0 |
| SSL Configuration | FME Flow | Installing FME Flow on Linux OS and configuring HTTPS using a self-signed certificate topic monitoring will not work. DEVOPS-1618 |
The recommended workaround is to use a valid certificate issued by a recognized certificate authority. Alternatively, you can set up FME Server to bypass the SSL configuration for the WebSocket service (used by topic monitoring) under System Configuration → Network & Email → Topic Monitoring, set the Internal WebSocket URL to ws://localhost:8078/websocket. |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| Webhooks | FME Flow | From the Run Workspace > Workspace Actions > Create Webhook, under the Parameters section of the Create Webhook page, if there is a source file parameter, it is not possible to upload a file. FMESERVER-18223 |
Upload the file on the Run Workspace page before creating a webhook, or upload the file to Resources, then select the file from Resources on the Create Webhook page. |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| File Upload | FME Flow | Files can be uploaded to FME Flow restricted admin folders by any authenticated account. FMEFLOW-18290 |
See Known Issue: Arbitrary file upload with any authenticated FME Flow account |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| SQLite Database Connection | FME Flow | After creating a database connection (e.g. SQLite database connection using a database file in Resources) that uses an uploaded file on FME Flow (Server), trying to run a workspace that uses this database connection results in the following error: `SQLite Reader: Failed to open database '$(FME_ SHARED RESOURCE _TEMP)\ database joiner.sqlite'. SQLite3 Engine error: `unable to open database file` FMEFLOW-20548 |
There are two workarounds available: 1. Upload the file (e.g. SQLite file) to Resources Data. or 2. Using the same database file on FME Form (Desktop), publish to FME Flow using the Embed Connection Parameter option |
2025.x 2024.x 2023.x 2022.2.5 |
Workaround |
| Repositories | FME Flow | Internal Server Error when publishing or deleting a repository with a leading or trailing space. FMEFLOW-17417 |
Delete the repository with trailing space from the server share (i.e. from File Explorer). Then delete from Web UI. |
2025.x 2024.x 2023.x |
Workaround |
| Web Connections | FME Flow | FME Flow web connection in FME Form fails with a 401 error when password begins and ends with a special character (!, &, @, etc.) after initial token expires (approx. 10 days) FMEFLOW-23006 |
Change user password to not include special characters both at the beginning and at the end of the password, such as a special character only at the end, and recreate the web connection |
2025.x 2024.x 2023.x |
Workaround |
| Temporary Uploads | FME Flow | FME Flow workspace translation fails to find uploaded temp datasets when Engines are distributed across different operating systems FMEFLOW-21985 |
Copy file(s) to the system location where FME is expecting to find it, or first upload the file via the REST API and then call Webhook URL |
2025.x 2024.x 2023.x |
Workaround |
| Database Connections | FME Flow | Manually created JDBC enabled database connections not working with message "No MSSQL_JDBC_NONSPATIAL_2 dataset name was specified (couldn't find a value for MSSQL_JDBC_NONSPATIAL_2_1_DATASET' or MSSQL_JDBC_NONSPATIAL_2_DATASET')", via REST V4 API connection details show empty fields as " " rather than "<Unused>" FMEFLOW-22765 |
Publish connections to FME Flow with the workspace from FME Form, or use the REST V4 API PUT endpoint to change the empty field values from " " to "<Unused>" |
2025.x 2024.x 2023.x |
Workaround |
| Webhooks | FME Flow | Cannot create a workspace webhook. The OK button is inactive and fields are missing from the Create Webhook page. FMEFLOW-23291 |
This affects workspaces with no published parameters and an SQLCreator or SQLExecutor. Add a published parameter to your workspace, use a native reader/writer, or use an Automation webhook and trigger it via a POST call. |
2025.x 2024.x 2023.x |
Workaround |
| Schedules | FME Flow | After upgrading FME Flow, my Schedule categories are missing. FMEFLOW-24135 |
Tags are now used instead of categories in FME 2023 and later. Categories will not be migrated to tags, they will need to be recreated after upgrading. See Known Issue: FME Flow Schedule Categories are Not Converted to Tags Upon Migration |
2025.x 2024.x 2023.x |
Unplanned |
| ArcGIS Server Feature Service | FME Form |
ArcGIS Server Feature Service Writer: Unable to create Feature Services Authentication is not as complete/robust as the AGOL/Portal formats. Users may encounter issues when attempting to authenticate Branch Versioning is not supported FMEENGINE-75760 |
None. |
2025.x 2024.x 2023.x |
Unplanned |
| FME Workbench | FME Form | FME 2023.x launches with a toolbar and blank screen (typically on a virtual machine). FMEFORM-29077 |
Downgrade to FME 2022.2 or upgrade VMware Tools to a minimum OpenGL version of 3.3. See Known Issue: FME Workbench 2023 Opens as a Blank Window on a Virtual Machine |
2025.x 2024.x 2023.x |
Workaround |
| System Proxy | FME Flow | After supplying updated credentials for a previously configured system proxy, version control will not detect the updated credentials and continues to make requests using the old credentials. FMEFLOW-18251 |
After updating the credentials under System Configuration >Network & Email > Proxy restart the FME Server Core Service. |
2025.x 2024.x 2023.x |
Workaround |
| REST API V3 | FME Flow | When transitioning from the V3 API to the V4 API, there is a known issue related to the handling of categories in Schedules. In the V4 API (which the FME Flow 23 UI uses), the concept of categories in schedules has been removed, and tags have been introduced as an alternative. The issue arises when creating a schedule using the V4 API. In the V4 API, a default category is implicitly created and represented by a unique identifier. If this schedule is retrieved using the V3 API, the category listed will be this unique identifier. This may cause issues for users who have built a custom interface using the V3 API. FMEFLOW-16486 |
None |
2025.x 2024.x 2023.x |
Unplanned |
| FME Flow Web UI | FME Flow | FME Flow is loading slowly during login in an offline or highly restricted environment. FME Flow is loading the Google Fonts API, which will take around 20 seconds to time out if it cannot be reached. FMEFLOW-21169 |
If possible whitelist fonts.googleapis.com |
2024.0.1 2024.0 2023.x |
Resolved 2024.0.2 |
| Deployment Parameters | FME Flow | Users lacking access permissions for a deployment parameter in FME Flow may encounter the following error: "Undefined macro ‘s3-skytrain-bucket-connection’ dereferenced in file <path to workspace>." | The missing macro is a deployment parameter. Grant the user permission to the deployment parameter. See Getting Started with Deployment Parameters. |
2025.x 2024.x 2023.x |
Workaround |
| Automations | FME Flow | A split merge block object is unable to be deleted from an automation canvas. FMEFLOW-23097 |
Save the automation and refresh the page. Now you can select the Split merge block object and delete it |
2024.x 2023.x |
Resolved 2025.0 |
| REST API V3 | FME Flow | Using the REST API V3 GET/schedules only returns the first 100 schedules in the list FMEFLOW-24185 |
Use the REST API V4 GET/schedules endpoint to retrieve schedules |
2025.x 2024.x 2023.2 |
Workaround |
| Tokens | FME Flow | API Token item permissions do not persist on import. For example, access to a specific resource folder. FMEFLOW-24660 |
After restoring an API Token, from a backup or project, reapply the item-level permissions. |
2025.x 2024.x 2023.2 |
Unresolved |
| Backup and Restore | FME Flow | Error on system restore after uploading backup (fsconfig) file: "The system restore failed for the following reason: The export location provided is invalid." FMEFLOW-24699 |
This occurs when the FME Flow server is behind a proxy or load balancer. Connect to the FME Flow server using the hostname instead. Depending on the network, this may require remotely connecting to the server. |
2024.x 2023.2 |
Unresolved |
| Web Connections | FME Flow | A basic auth FME Flow connection created using the FME Flow web UI, or via the REST v4 API, fails when used in a job with an invalid credentials error. FMEFLOW-24836 |
Publish the connection to FME Flow from FME Form |
2024.x 2023.2 |
Unresolved |
| Dropbox Web Service |
FME Form FME Flow |
Newly authorized Named Connections for the Dropbox Web Service will always expire after four hours. FMEENGINE-82114 |
None currently. Web connections and triggers will expire after 4 hours. There is only a workaround for FME Form, by adding the following line to the Web Service's OAuth 2.0 Authorization URL. token_access_type=offline |
2024.x |
Resolved FME Form 2024.1 Resolved FME Flow 2025.0 |
| FME Flow Apps | FME Flow | In a Workspace App, uploading files twice through the 'Browse Resources' menu causes the 'Run' button to disable. FMEFLOW-23580 |
Upload your files directly into the Workspace App using the Drap & Drop method or clicking 'browse file system'. |
2025.x 2024.x |
Unresolved |
| Logs | FME Flow | The "Download Logs" option in an Automation's menu does not work on some system locales due to differing date formats. List of known system locales to not work: en_CA, fr_CA, fr_FR, fr, de_DE, de This can also occur if log timestamps have been disabled on your instance. FMEFLOW-24588 FMEFLOW-24607 |
Option 1: Change the system locale on the machine hosting FME Flow to 'en_US' Option 2: Follow along the guide How to Combine Logs for One Automation (FME Flow 2023.2 to 2024.2) |
2025.x 2024.x |
Workaround |
| FME Flow | Error validating system email: "Parameter Validation Failed" FMEFLOW-24825 |
There is an error with the email configuration that is not displayed on the web UI. You can use your browser's developer tools to view the error. In FME Flow 2024, the Email From field must only contain an email address. |
2025.x 2024.x |
Unresolved |
|
| Engine Management | FME Flow | Engine Management: a Job Routing Rule where the source name is a Workspace App name or Automation name doesn't work. FMEFLOW-24872 |
Route based on the repository name that contains the workspace used by the Workspace App. For an Automation, place workspaces in the same repository and route based on the repository name. |
2025.0 2024.x |
Unresolved |
| Generic Reader | FME Form | When reading Excel files using a generic reader, the column names are not created as attribute names and data cannot be written downstream. Error: "templateFType" is null FMEENGINE-82535 |
Use a Microsoft Excel reader instead |
2025.x 2024.x |
Workaround |
| Python | FME Form | Cannot use Python 3.10+ Conda environments as custom Python interpreter. FME will fall back to using the shipped Python 3.12 interpreter with the error: "The User-specified library <condaEnv>\python312.dll could not be loaded" FMEENGINE-84685 |
Use Python 3.12 |
2025.x 2024.x |
Unresolved |
| HDFSConnector | FME Form | HDFSConnector fails with the error: "<ModuleNotFoundError>: No module named 'imp'" FMEENGINE-83116 |
Use a custom Python 3.8-3.11 interpreter in Workbench. Note: Python interpreters 3.10+ from Conda environments cannot be used due to FMEENGINE-84685 |
2024.2.2 2024.2.1 2024.2.0 2024.1 2024.0 |
Resolved 2024.2.3 |
| Backup and Restore | FME Flow | After upgrading, no system cleanup tasks are displayed and there is an Internal Server Error message. FMEFLOW-24335 |
This is caused by system cleanup tasks created in earlier versions of FME Flow that are incompatible with FME Flow 2024.2+. For example, a cleanup task targeting a UNC path. Submit a ticket to support and attach your system backup (fsconfig) file or send it via FTP. Reference Known Issue ID FMEFLOW-24335. |
2024.2.2 2024.2.1 2024.2 |
Resolved 2024.2.3 |
| Emailer Transformer | FME Form | Error: "SMTPDataError: Could not complete request. Message: (554, b'Transaction failed: Empty address')" when sending email via the Emailer transformer using AWS as the SMTP host. FMEENGINE-84884 |
This affects workspaces authored in earlier versions of FME using Emailer v0 Upgrade the Emailer transformer to v1 Remove and replace the emailer transformer |
2024.2.1 2024.2.0 2024.1 2024.0 2023.x |
Resolved 2024.2.2 |
| Emailer Transformer | FME Form | "401 Unauthorized" when trying to use the Emailer with the template "Microsoft Mail (safe.emailer)" web service and sample Client ID provided. FMEENGINE-84539 |
The sample Client ID is no longer valid. It is always recommended to use your own Client ID. See How to use Microsoft Modern Authentication with FME |
2024.2.1 2024.2.0 2024.1 2024.0 |
Resolved 2024.2.2 |
| Web Connections | FME Flow | Web connections that use an HTTP Authentication Service web service cannot be edited on Flow. Also, the connection's username and password are missing in FME Flow after it has been uploaded from FME Form. FMEFLOW-24416 |
Use a token or Oauth2.0 web service, if possible, or Embed credentials into the reader/writer/transformer in FME Workbench and then republish to FME Flow |
2024.2.1 2024.2 |
Resolved 2024.2.2 |
| Resources | FME Flow | FME Flow Linux and FME Flow Hosted Only: 502 gateway error trying to download Resource files greater than approximately 2GB. FMEFLOW-24429 |
For large backups, choose to download the fsconfig instead of saving it to Resources/Backups where it currently can’t be downloaded. For other files, SSH to the FME Flow Linux server and copy files from the system share using the Linux terminal (not applicable for FME Flow Hosted) |
2024.2.1 2024.2 |
Resolved 2024.2.2 |
| Autodesk AutoCAD Reader/Writer | FME Form FME Flow |
Jobs with AutoDesk AutoCAD readers/writers using the REALDWG plugin directory fail with the error "Module 'realdwg/REALDWG' is unavailable for use with this FME edition." FOUNDATION-568 FMEENGINE-85174 |
Before attempting this workaround, make a copy of the Flow RealDWG plugin folder (<FMEFlowDir>\Server\fme\plugins\realdwg) so you can undo your changes if necessary. Then, replace the RealDWG plugin folder in FME Flow with the FME Form RealDWG plugin folder (<FMEFormDir>\plugins\realdwg). For workspaces handling DWG files containing only 2D data or where primitive 3D data capabilities are acceptable, use the Autodesk AutoCAD DWG/DXF (ACAD) reader/writer as it does not require RealDWG. FME 2024.2.1 and above uses RealDWG 2025 which is compatible with Windows Server 2019 and above. Upgrade your Windows Server or downgrade FME to 2024.1.4 or below. |
2024.2.0 |
Resolved 2024.2.1 |
| ArcGIS SDE Geodatabase | FME Flow |
ArcGIS SDE Geodatabase error: "Could not open the Enterprise Geodatabase. The error number from ArcObjects is: '-2147216118'. The error message from ArcObjects is: {Bad login user[ ]}", but the same .sde file works outside of FME Flow. FMEFLOW-24789 |
Open the ArcGIS SDE Geodatabase connection in the FME Flow web UI and click OK to resave it. To avoid this error, create the connection via the FME Flow Web UI or upload it when publishing a workspace from FME Workbench. Do not upload from FME Form's Database Connections. |
2024.2.2 2024.2.1 2024.2 2024.1 2024.0 |
Resolved 2025.0 2024.2.3 |
| SQLCreator/SQLExecutor Transformers | FME Form | When reading an Esri Geodatabase using an SQLExecutor or SQLCreator, and ArcGIS Server 11+ is installed on the same machine, no features are read. The warning "Esri Geodatabase: ArcMap has limited SQL functionality and may not be able to process query" is logged, even if ArcMap is not installed FMEENGINE-84276 |
Use an Esri Geodatabase (SDE) reader or FeatureReader transformer |
2024.2 2024.1 2024.0 |
Resolved 2025.0 |
| FME Flow Apps | FME Flow | When an FME Flow workspace app requires authentication, and the app has Database Connection or Web Connection parameters, the authenticated app user is not able to view and select connections they have created. FMEFLOW-23997 |
Use a single, shared connection. If different connections must be available for selection, then an FME Flow administrator needs to grant the app's API token access to each connection. |
2025.x 2024.2 2024.1 |
Workaround |
| FME Flow Database | FME Flow | When using the encryptConfigSetting.ps1 power shell script to encrypt the FME Flow database password a NoClassDefFoundError exception is called. FOUNDATION-581 |
The database credentials were recently relocated to a new file, fmeDatabaseConfig.txt, but the script still references the old file, fmeCommonConfig.txt. As a workaround, the file path can be passed as a third parameter like so: .\encryptConfigSetting.ps1 DB_PASSWORD fmeflow 'C:\Program Files\FMEFlow\Server\fmeCommonConfig.txt' |
2024.2 2024.1 |
Resolved 2025.0 |
| Oracle Database Connection | FME Form | Warning at the bottom of job log: "Resetting a database that is still referenced. (serverType=`ORACLE8i', serverName=` <ServerName>', userName=`<UserName>', password=`***', dbname=`%4'" FMEENGINE-85247 |
This warning is written to the log when a workspace that connects to an Oracle database runs. It has no impact on the job and can be ignored. |
2025.0 2024.2 2024.1 |
Unresolved |
| Microsoft OAuth 2.0 | FME Form |
"401 Unauthorized" error when testing a Microsoft OAuth2.0 web service and the optional Client Secret contains a value (Microsoft OAuth2.0 web services) FMEFORM-32432 |
Even if the Client Secret has been set to 'Optional', you must also clear the contents of the field. |
2024.2 2024.1 |
Resolved 2025.0 |
| Backup and Restore | FME Flow | Unable to upload the encryption key file (.jceks) from a Linux client machine, regardless of the Linux distribution or web browser used. Error: "Invalid File Type" FMEFLOW-24291 |
Upload the key file from a Windows or MacOS client machine. |
2025.x 2024.2 |
Workaround |
| Web Connections | FME Flow | Web connections not appearing in published parameters FMEFLOW-24586 |
This may occur if you are using a derived web service, which is a web service that is created from a different web service. To fix this, in FME form, find the published parameter, go to supported services, and uncheck all services. Then, reupload the workspace to FME Flow. |
2024.2.2 2024.2.1 2024.2 |
Resolved 2025.0 2024.2.3 |
| Resources | FME Flow | Cannot write to a Resource connection on FME Flow using an FME Flow parameter (macro). For example: $(mySharedFolder). This occurs with the FeatureWriter and may occur with some native writers as well. FMEENGINE-85071 FMEFORM-32709 |
If possible, try to use a native writer, like the CSV writer, instead of the FeatureWriter. Save the FME Flow resource parameter (macro) to an attribute and reference the attribute in the FeatureWriter's dataset path. |
2025.x 2024.2 |
Workaround |
| AttributeExploder Transformer | FME Form | AttributeExploder: drops the last 2 characters of list name FMEENGINE-83608 |
Upgrade to FME 2024.1.2.1 |
2024.1.2.0 2024.1.1 2024.1 |
Resolved 2024.1.2.1 |
| SlackConnector Transformer | FME Form | SlackConnector: upload endpoint has been deprecated by Slack and new Slack apps will not be able to use the upload file functionality. FMEENGINE-82694 |
Upgrade to FME 2024.1.1 |
2024.1.0 2023.x 2022.x 2021.x |
Resolved 2024.1.1 |
| Automations | FME Flow | When submitting an HTTP request with the HTTP Request Automation action, the URL is not encoded correctly or, if already provided as URL-encoded, may be modified by FME Flow and cause the request to fail. FMEFLOW-23729 FMEFLOW-23739 |
Try to provide the Target URL without URL encoding. If the request still fails, use a workspace with an HTTPCaller instead |
2024.1 2024.0 2023.x |
Resolved 2024.2 |
| Automations | FME Flow | A job run by an Automation is stuck in a running status and cannot be canceled via the FME Flow Web UI or REST API. FMEFLOW-22721 |
See Known Issue: Job Submitted from Automation is Stuck Running and Cannot be Cancelled |
2024.1 2024.0 2023.x |
Resolved 2024.2 |
| Automations | FME Flow | When trying to view logs for an Automation, authors receive the error 'You do not have permission'. FMEFLOW-22658 |
Authors cannot view logs by default. Grant access to the Logs folder under Resources. |
2024.1 2024.0 2023.2 |
Resolved 2024.2 |
| Deployment Parameters | FME Flow | A workspace using a deployment parameter that is run via Automation fails with unexpected <opencurly></closecurly> XML tags around the parameter value FMEFLOW-23256 |
Confirm that any deployment parameters used in the Automation have also been shared. If an administrator adds a new deployment parameter after the Automation has been shared, and then updates the Automation to use it, the new deployment parameter must also be shared with anyone who needs to start the Automation. |
2024.1 2024.0 |
Resolved 2024.2 |
| Backup and Restore | FME Flow | After upgrading, the error "Item <workspace name>.fmw does not exist" is displayed on the Subscriptions page. No subscriptions are displayed. This occurs if a workspace used by an FME Workspace Subscription is removed. | Upgrade to FME Flow 2024.2+ or temporarily republish a workspace with the same name to the repository configured in the Subscription and reload the Subscriptions page. The FME Workspace Subscription item can then be updated or removed. |
2024.1 2024.0 |
Resolved 2024.2 |
| Backup and Restore | FME Flow | After upgrading, no publications or subscriptions are displayed and there is an Internal Server Error message. FMEFLOW-23758 |
Upgrade to FME Flow 2024.2+ or submit a ticket to support for assistance and reference Known Issue ID FMEFLOW-23758. |
2024.1 2024.0 |
Resolved 2024.2 |
| Microsoft Excel Writer | FME Form | Excel Writer: Field Names row not written FMEENGINE-82549 |
Set the Row Height to 0 on the Feature Type |
2024.1 2024.0 |
Resolved 2024.2 |
| EsriReprojector Transformer | FME Form | EsriReprojector is significantly slower than earlier versions of FME FMEENGINE-83720 |
If you can, use the Reprojector transformer instead. Otherwise, upgrade to FME 2024.2+ |
2024.1 2024.0 |
Resolved 2024.2 |
| FMEFlowJobSubmitter Transformer | FME Form | Download from Flow window and FMEFlowJobSubmitter only shows first page of Repository folders and the first page of workspaces in
2024.1 FMEFORM-31816 |
Upgrade to FME 2024.1.2 |
2024.1 |
Resolved 2024.1.2 |
| FME Flow Apps | FME Flow | Existing text in text fields for Flow Apps on the Editing Page disappears, but text is still visible from App itself FMEFLOW-22917 |
Use the web browser zoom settings to zoom out one step and text should reappear on App Editing page |
2024.0.1 2024.0 |
Resolved 2024.0.2 |
| PATH Environment Variable | FME Form | Starting In FME 2022.0, Windows installers does not add FME_HOME (FME install directory) to PATH environment variable on Windows. This change could affect users who access FME functionality through Python scripts as required .dll files cannot be located and loaded. DEVOPS-2856 |
Manually add FME install directory to PATH environment variable |
2024.0 2023.x 2022.x |
Resolved 2024.1 |
| Automations | FME Flow | An error is returned when attempting to stop an Automation: "Error: Could not find prepared statement with handle 1." FMEFLOW-22307 |
Restarting FME Flow temporarily resolves the issue. Replace the JDBC driver in the Utilities (<FME Flow Dir>/Utilities/jdbc) folder with version 11.2.1 (mssql-jdbc-11.2.1.jre17.jar) as a permanent solution. |
2024.0 2023.x |
Resolved 2024.1 |
| User Parameters | FME Flow | Conditional/Dependent Visibility user parameters that use operators >, <, <=, >= will be displayed regardless of the options picked. FMEFLOW-20647 |
Change the Conditional/Dependent parameters operators to Is or Is Not |
2024.0 2023.2 2023.1 |
Resolved 2024.1 |
| Encryption | FME Flow | Nothing happens when trying to import an encryption file. There is a 403 error in the web browser's developer tools. FMEFLOW-22786 |
Log in to the FME Flow server. Access FME Flow using localhost in the web browser and try the file upload. |
2024.0 2023.2 |
Resolved 2024.1 |
| Version Control | FME Flow | If a user enabled version control with a Remote Repository URL and then changes to use the local Git repository that comes with FME Flow, they cannot remove the URL from the Web UI. FMEFLOW-21835 |
Use the version control API “http://<hostname>/fmerest/v3/versioncontrol” to update outside of FME Flow (ex: Postman) and provide an empty remote repository URL. |
2024.0 2023.2 |
Resolved 2024.0.1 |
| Packages | FME Flow | A “Python Exception <ImportError>: cannot import name ‘WSCException’ from ‘modules’” error is returned when running workspaces that use older versions of the following packages: Google Cloud Storage (fpkg-google-cloud-storage) Google Cloud PubSub (fpkg-google-cloud-pubsub) Azure Storage (fpkg-azurestorage) EXPERTS-6678 FMEENGINE-80488 |
Upgrade the package in FME Workbench and re-publish the workspace and upgraded package to FME Flow. Run the workspace on the Run Workspace page. |
2024.0 |
Resolved Upgrade Package |
| Remote Engines | FME Flow | When submitting a job to a remote engine that contains a database connection with Conditional or Optional fields or with a SSL Options field, the job submission fails. For error message example see Known Issue: Job Containing Database Connections with Conditional or Optional Fields Fails on Remote Engines. FMEFLOW-22664 |
Have the database connection SSL Mode set to Disable and/or update the connection through the Flow UI. See Known Issue: Job Containing Database Connections with Conditional or Optional Fields Fails on Remote Engines. |
2024.0 |
Resolved 2024.0.1 |
| Automations | FME Flow | Feature counts are not displayed on the Automation canvas for Automation Writers. FMEFLOW-22606 |
None |
2024.0 |
Resolved 2024.1 |
| Web Connections | FME Flow | When trying to authorize an Airtable Web Connection on FME Flow, an error message pops up after entering the Airtable login details: “FME Flow OAuth Service FAILED Failed to complete” FMEFLOW-22682 |
Do not authorize Airtable connection via FME Flow Web UI. Authorize the connection in FME Form and publish to FME Flow. |
2024.0 |
Resolved 2024.0.1 |
| Security | FME Flow | Previously set password fields do not clear to a blank string by selecting the field and then saving it FMEFLOW-21285 |
After selecting the password field, type something into it, then erase it before saving to reset the field to a blank string |
2024.0 |
Resolved 2024.1 |
| Databricks Writer | FME Flow | Unable to locate SAFE.DATABRICKS.DATABRICKS_REST.fmf file for Databricks writer workspace when workspace is published and ran for the first time on FME Flow FMEFORM-30079 FMEFORM-39422 |
Restart FME Flow Engines, republish workspace a second time, manually upload the SAFE.DATABRICKS.DATABRICKS_REST.fmf file to <FMEFlowDir>\Server\fme\metafile\ |
2024.0 |
Resolved 2024.1 |
| WebsocketSender/WebsocketReciever Transformers | FME Flow | WebsocketSender and WebsocketReciever transformers have been depreciated and will display the following error if used: WebSocketSender: The WebSocketReceiver/Sender transformers are no longer supported FMEENGINE-81231 |
Update workflows to use FME Flow Automation WebSockets or the PythonCaller. |
2024.0 |
Deprecated 2024.0 |
| FME Flow Connections |
FME Form FME Flow |
When an FME Form version from 2024.0 to 2024.2.0 is installed on Windows Server 2016 or Windows Datacenter 2016, and an attempt is made to connect to FME Flow hosted on a different machine with a newer Windows Server version and configured with HTTPS, the connection fails with an error FMEFORM-31805 |
See Known Issue: FME Form HTTPS Connection Fails on Windows Server 2016 |
2024.2.0 2024.1 2024.0 |
Resolved 2024.2.1 |
| Slack Web Connection | FME Form | "this browser won't be supported" message appears when creating a Slack web connection FMEENGINE-81729 |
Create a new web connection in FME Workbench from the Slack template. Under Authorization Parameters > HTTP User Agent > and change the default value to 'FME Default' |
2023.x 2022.x 2021.x 2020.x |
Resolved 2024.0 |
| Webhooks | FME Flow | When a workspace webhook is created with a geometry parameter and then run, the translation fails due to a JSON syntax error. FMESERVER-19915 |
On the create webhook page, re-select the geometry parameter to update the webhook URL prior to saving. |
2023.x 2022.x |
Resolved 2024.0 |
| User Parameters | FME Flow | When running a workspace on FME Server with a geometry parameter or using the workspace in an FME Server app, the extent of the area shown is larger than the bounds defined in FME Workbench when the geometry parameter is viewed ‘inline’ | Use the pop-up map window instead of the inline map. |
2023.x 2022.2 2022.1.3 2022.1.2 |
Resolved 2024.0 |
| Esri ArcGIS Layer Reader | FME Form | The Esri ArcGIS Layer Reader fails to bring up an input dataset selection dialog when selecting the ellipsis button with the error message that "Selecting Esri layers is unavailable". FMEENGINE-80772 FMEENGINE-67049 |
Instead of selecting from the ellipsis button, provide a known dataset path to the layer file. |
2023.x 2022.2 |
Resolved 2024.0 |
| Esri Shapefile Writer | FME Form | When writing an Esri shapefile in FME Desktop 2022.1 through FME Form 2023.0, users whose machines are set to a Japanese system locale (OS Locale: ja_JP, for example) will notice the attribute names in the output shapefiles are prefixed with ‘Q_’ anytime the source attribute name begins with a Japanese character. FMEENGINE-76609 |
See Known Issue: SHAPEFILE Writer Adds 'Q_' Prefix to Attribute Names Beginning With Japanese Characters |
2023.0 2022.2 2022.1 |
Resolved 2023.1 |
| FME Workbench | FME Form | FME Form does not load successfully. When opening FME Workbench, it starts up with the splash-screen as normal, but after "Initializing main window" the application does not load. FMEFORM-28857 |
Upgrade to FME 2024.0, or see workaround. |
2023.x |
Resolved 2024.0 |
| FME Form Licensing Assistant | FME Form | Users that add new floating license seats to an existing serial number, or request a license file with multiple serial numbers are getting licenses in two or more line items. This creates two or more “FME Form” license pools in the Licensing Assistant when there should only be one. DEVOPS-3164 |
Requesting an FME 2023 license will give you a license file wherein all editions associated with the serial number(s) are consolidated into a single edition called “FME Form”. |
2023.x |
Resolved Other |
| FeatureWriter Transformer | FME Form | FeatureWriter: when there are multiple FeatureWriters in a workspace, performance is much slower than in prior FME versions. FMEENGINE-81646 |
Set the 'Features to Read' to 'Data Features'. If you require the schema as well, obtain it from a separate FeatureReader set to 'Schema Features' and initiate it with a single feature (for example, using a sampler) |
2023.x |
Resolved 2024.0 |
| FeatureJoiner Transformer | FME Form | FeatureJoiner crashes FMEENGINE-81599 |
Adding a Decelerator before the Left port might help. (set "Delay Per Feature (Seconds)" to 0) |
2023.x |
Resolved 2024.0 |
| REST API V4 | FME Flow | In REST API V4, the /permissions endpoint will now reference ids instead of names when setting permissions. This change will mainly affect users who this endpoint to set permissions for Flow Apps or Schedules. FMEFLOW-18384 |
Use ids instead of names in REST calls. Refer to the REST API V4 documentation for more details. |
2025.x 2024.x 2023.x |
Workaround |
| FME Workbench | FME Flow | When a workspace with an Overview (created in FME Workbench Navigator window > Description > Overview) is being configured to run with Run Workspace on FME Flow, the Overview does not appear beneath the selected workspace. FMEFLOW-21824 |
Upgrade to FME 2024.0 |
2023.x |
Resolved 2024.0 |
| Jobs | FME Flow | Non-admin users with applicable permissions (Jobs > Manage) cannot filter Jobs by User | Enable Manage permissions for Engines and Licensing for applicable users/roles |
2023.x |
Resolved 2024.0 |
| Automations | FME Flow | When copying/pasting the Run Workspace Action node in Automations, the Repository, and Workspace parameters are unavailable/missing. FMEFLOW-21623 |
Add a new Action node to the canvas instead of copying/pasting. |
2023.x |
Resolved 2024.0 |
| Backup and Restore | FME Flow | System Backup fails with the error "929029: unable to export" FMEFLOW-23068 |
Please see Known Issue: FME Flow System Backup Fails with Error “929029:Unable to export” |
2023.x |
Resolved 2024.0 |
| MapTextLabeller Transformer | FME Flow | Error when trying to use the MapTextLabeller on FME Flow: "Module 'LabelEZFactory' is unavailable for use with this FME edition" FMEDIST-829 |
Downgrade to FME Flow 2023.1.x or upgrade to 2023.2.5. Please note that 2023 is the last major FME version to include the MapTextLabeller. Please see MapTextLabeller Plugin Availability Changes |
2023.2.4 2023.2.3 2023.2.2 2023.2.1 2023.2.0 |
Resolved 2023.2.5 |
| Dyanmic Writer | FME Form | Dynamic Writers produce excessive warning messages about the renaming of format attributes when set to Dynamic Mode and there is a performance loss. FMEENGINE-80292 |
Upgrade to 2023.2.2 or turn off Log Warnings in FME Workbench (this will suppress all other warnings as well) |
2023.2.1 2023.2.0 2023.1 2023.0 |
Resolved 2023.2.2 |
| Automations | FME Flow | When passing JSON parameters to an email subscriber using an FME Flow Topic action in an Automation, the email body contains the full JSON instead of the subscriber content specified in the JSON. FMEFLOW-21252 |
This occurs when the topic message is passed as a JSON parameter in the FME Flow Topic action. Hardcode the topic message JSON in the Automation or use the FMEFlowNotifier transfomer in FME Workbench to pass the JSON as an attribute. |
2023.2 2023.1 2023.0.2 2023.0.1 |
Resolved 2024.0 |
| Projects | FME Flow | Project export fails when the destination default value path set in a Workspace app doesn't exist FMEFLOW-22570 |
Run the workspace with the Job Submitter service first to ensure the resource path is created before creating the project. Another option is to have the default path point to an existing data resource folder. |
2023.2 2023.1 |
Resolved 2024.0 |
| Backup and Restore | FME Flow | The FME Flow Backup and Restore does not restore Database and Web Connections on systems that use custom encryption. FMEFLOW-21709 |
Switch to the weak encryption mode before performing the backup and restore. Please contact support if you have questions. |
2023.1.2 2023.1.1 |
Resolved 2023.2 |
| Python | FME Form | If Anaconda3/ Miniconda3 Python 3.11 is installed on the same machine and Anaconda/ Miniconda is registered as the default Python 3.11, any FME package installation will fail with the error: ImportError: DLL load failed while importing _ctypes: The specified module could not be found. Error in running the Python command 'python %0' FMEENGINE-80576 |
Copy <anaconda InstallDir>/ Library/bin/ffi.dll to <anaconda InstallDir>/ DLLs *Requires administrative permissions if Anaconda/Miniconda is installed for all users (ie. installation path is in %programdata%) OR downgrade to Anaconda/ Miniconda Python 3.10 |
2023.1.1 2023.1.0 2023.0 |
Resolved 2023.1.2 |
| Python | FME Form | Users with a custom Python 3.7 to 3.9 interpreter set in FME Form will encounter this warning: FME supports Python 3.7 to 3.11. Ignoring the user-specified Python library version 3.0 from <pathToCustomInterpreter.dll> FMEENGINE-80724 |
Upgrade to 2023.1.2+ |
2023.1.1 2023.1.0 |
Resolved 2023.1.2 |
| Aggregator Transformer | FME Form | Aggregator doesn't respect Group By setting when receiving 10,000 features or more FMEENGINE-80344 |
Use a Decelerator before the Aggregator or use FME 2023.0 |
2023.1.0 |
Resolved 2023.1.1 |
| FME Workbench | FME Form | Transformer Order in the Navigation Panel - Not Alphabetical FMEFORM-29414 |
None. |
2023.1.0 |
Resolved 2023.1.1 |
| FME Workbench | FME Form | List of upgradeable, invalid or disabled transformers does not appear in the Navigator Pane for workspaces in FME 2023.1+ FMEFORM-29429 |
None. |
2023.1.0 |
Resolved 2023.1.1 |
| SAML | FME Flow | When the FME Flow web UI is accessed via FQDN, SAML login attempt [ after typing in the IDP credentials and submitting] takes us back/loops to the IDP login prompt webpage. SAML works well after replacing the flow host FQDN with IP address. FMEFLOW-21670 |
Reference the flow/server host with IP address instead of the FQDN [i.e. FME_SERVER _WEB_URL field in fmeServerConfig.txt and fmeServerWeb ApplicationConfig.txt] Setup the SAML configuration with the IP address instead of the FQDN. |
2023.1 2023.0 2022.2 |
Resolved 2023.2 |
| Deployment Parameters | FME Form | Replacing a deployment parameter in the database connection of a reader/writer with a connection from FME Workbench will leave an invalid deployment parameter entry in Navigator. The reader/writer will then continue to use the old connection associated with the deployment parameter instead of the newly chosen connection. FMEFORM-29101 |
Remove the reader/writer, restart FME Workbench, re-add the reader/writer |
2023.1 2023.0 |
Resolved 2023.2 |
| Oracle Writer | FME Form | Oracle Writer fails to create table with more than 100 attributes. Error: 'Too many values to bind'. FMEENGINE-79926 |
None. |
2023.1 2023.0 |
Resolved 2023.2 |
| AutodeskDocsConnector Transformer | FME Form | The AutodeskDocsConnector and web service stops working in existing workspaces and newly created web connections due to Autodesk's planned OAuth v1 deprecation. FMEENGINE-79894 |
Upgrade FME to 2023.2 and update the AutodeskDocs package to v1.1.0 or newer. See Known Issue: AutodeskDocsConnector OAuth API v1 Deprecation will Require an Upgrade to FME 2023.2 |
2023.1 2023.0 |
Resolved 2023.2 |
| FeatureWriter Transformer | FME Form | FeatureWriter: Workbench unresponsive after importing feature type FMEFORM-29677 |
None. |
2023.1 2023.0 |
Resolved 2023.2 |
| Active Directory | FME Form | Installing FME Form 2023.0 through 2023.1.x breaks Windows AD auth in other installed 32-bit applications, with one of the following generic error messages shown: Failure to access the DBMS Server unable to load adalsql.dll FMEENGINE-80806 |
Upgrade FME Form to at least FME Form 2023.2, or download and install the Microsoft OLE DB Driver for SQL Server v. 19.3.1+. The issue lay in a bug that was discovered with the OLE DB Driver v19.2. |
2023.1 2023.0 |
Resolved 2023.2 |
| FME Flow Apps | FME Flow | A file parameter placed in a parameter group doesn't allow uploads in an FME Flow app. FMEFLOW-21415 |
In FME Workbench, create a new workspace and create the file parameter(s) outside of the parameter group. |
2023.1 2023.0 |
Resolved 2023.2 |
| FME Flow Apps | FME Flow | Cannot save an FME Flow app that has required parameters in a parameter group unless default values are provided. FMEFLOW-21278 |
In FME Workbench, move the parameters outside of the group. Or, on the FME Flow Create/Edit App page, provide default values. |
2023.1 2023.0 |
Resolved 2023.2 |
| Users and Roles | FME Flow | Authorized users and roles do not save when 'Require Authentication' is enabled for a Flow app (any type). This affects installations with a large number of users and roles. FMEFLOW-21659 |
Access can be granted via user management > items > category > choose the type of app you want to grant access to > grant permissions. If the Flow app is saved after permissions are applied via user management, the permissions will need to be reapplied. |
2023.1 2023.0 |
Resolved 2023.2 |
| SQLExecutor Transformer | FME Flow | Job with SQL Executor completes successfully, but the SQL does not run. | This occurs when there is no transformer connected after the SQLExecutor. Connect a logger to the Result port. |
2023.1 2023.0 |
Resolved 2023.2 |
| Web Connections | FME Form | Remove JCEKS description keys from FME 2023.1 For the customers migrating from FME 2018 to FME 2023.1, all the database and web connections will not work. FMEFORM-13391 |
First upgrade from FME 2018.x to a build between FME 2019.0 to FME 2023.0, all the existing connections/web services will get migrated without any issue. |
2023.1 2019.x 2018.x |
Resolved 2023.1 |
| Users and Roles | FME Flow | Incorrect users and type listed when searching for roles in User Management FMEFLOW-21878 |
Scroll to the role you want to view details for. If you have a large number of roles, use the GET /security/roles/< role > REST API endpoint |
2023.1 |
Resolved 2023.2 |
| FME Flow Web UI | FME Flow | FME Flow web UI search results are inaccurate in the following places: User Management Roles: Users and Type Automations: Last Updated Flow Apps: Last Updated Automation Apps: Expiration’ Gallery Apps: Number of Links Resources: Date and Size System Cleanup: Max Age, Filter, and Enabled Broadcast Messages: Severity and Last Updated FMEFLOW-21879 |
Increase the number of visible items on the page and use your web browser's search feature instead. If there are too many items to display on one page and the web browser search cannot be used, then you may be able to access some item lists using the REST API and export the results to a file for searching. |
2023.1 |
Resolved 2023.2 |
| Security | FME Flow | Password reset email doesn't get sent to users when using "Forgot your password?" on the web UI login page FMEFLOW-21880 |
Login to FME Flow with an admin account and manually change the users password from the User Management page. |
2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | Automation Workspace Action: parameter selections do not persist if manual trigger parameters are provided as values for Date, Datetime, or Yes/No fields FMEFLOW-21896 |
Hardcode the parameter values in the automation action. |
2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | Automation Log Action not logging Manual Trigger parameter values | Use a Logger transformer in a workspace |
2023.1 |
Resolved 2023.2 |
| Automations | FME Flow | When passing an Automation parameter to a password parameter in a workspace action, the parameter's JSON name is passed to the workspace, not the value FMEFLOW-21897 |
Hardcode the password value in the automation action. |
2023.1 |
Resolved 2023.2 |
| Projects | FME Flow | Project import overwrites existing web service even when a web connection is excluded from the import FMEFLOW-21858 |
Update to 2023.2 |
2023.1 |
Resolved 2023.2 |
| Python | FME Flow | Python scripts using numpy fail on FME Flow when they worked on FME Form. FMEFLOW-21194 |
Please open a support case and provide which version of FME you are on and the operating system you are using and we can provide a workaround. |
2023.0.2.0 2023.0.1.x |
Resolved 2023.0.2.1 |
| Distributed Engines | FME Flow | When installing a Distributed Engine the engine service will not start because of a missing file. DEVOPS-4057 |
Use FME 2023.0.2 or later, or download and place the fmeserver.config into the following directory: <Install Directory> FMEFlow\ server\ security |
2023.0.1 |
Resolved 2023.0.2 |
| Schedules | FME Flow | Schedule fails to submit jobs after changing or transferring ownership to another user. In Resources>Logs>core>current>fmescheduler.log, you will see warning and error messages: WARN FMEServerQuartzScheduler_Worker-4 406427 : Job submission failed. Category: <category> Name: <ScheduleName> Error: <ScheduleName> WARN FMEServerQuartzScheduler_Worker-4 406411 : Job submission failed. Please ensure Transformation Manager is available. Category: <category> Name: <scheduleName> ERROR pool-2-thread-1 406439: An error occurred while triggering: QSInvalidRequest FMESERVER-18525 |
Open each schedule where the ownership has been changed and resave them. |
2023.0.0.2 2023.0.0.1 2023.0 2022.x 2021.x |
Resolved 2023.0.0.3 |
| Microsoft Excel Writer | FME Form | Excel Writer currently deletes the existing file, when 'overwrite existing' is enabled in the writer parameters. FMEENGINE-78316 |
Disable overwrite existing file. |
2023.0.0 2022.2.6 |
Resolved 2023.0.1 |
| Esri Licensing | FME Form | Esri Licensing not working with ArcServer if ArcServer and Pro are both installed. FMEENGINE-77154 |
Uninstall either ArcPro or ArcServer and restart FME. Please contact Safe Software Support if you require a different workaround. |
2023.0 2022.2.6 2022.2.5 2022.2.4 |
Resolved 2023.1 |
| Log Files | FME Flow | The DateTime format in the FME Server Log Files has changed from Mon-18-Jul-2022 01:48:26.085 PM to Mon.-18-Jul.-2022 01:48:26.085 p.m. FMEFLOW-18681 |
None. This is caused by upgrading FME Server from JDK 8 to JDK 17. This change is only present for certain locales. For example, on a system where the default locale is en_US the DateTime format will not be affected, but if the default locale is en_CA. |
2023.0 |
Unplanned Other |
| Floating License | FME Form | In FME Form 2023.0 licensed with a floating license server. Using existing or new FME workspaces with transformers/custom transformers configured to use parallel processing generates an error FMEENGINE-78741 |
See Known Issue: FME 2023 fails to invoke parallel processing when using a Floating License |
2023.0 |
Resolved 2023.0.1 |
| Automations | FME Flow | When trying to create a webhook trigger, the web UI reports that the webhook URL is required and won’t let you create the trigger. The webhook URL is generated by FME Flow after the automation is saved and shouldn’t require any user input. FMEFLOW-21011 |
Enter any text in the URL field to create the trigger. The automation then replaces the text on save with the generated webhook URL. |
2023.0 |
Resolved 2023.1 |
| Tokens | FME Flow | Token web service doesn't obtain a new token after expiry on FME Server FMESERVER-19419 |
This only impacts token web services that need to pass the Authorization in the HTTP Header. Use an HTTP Caller in a workspace to obtain the token through a REST API call |
2022.x 2021.x 2020.x |
Resolved 2023.0 |
| Queues | FME Flow | If you create a Queue Name that contains a special character (such as ^) engines will not be able to assign themselves to this queue. FMESERVER-17992 |
Create a Queue Name that contains spaces and alphanumeric characters only. Note: Underscore characters can be used as long as it is not the first character. |
2022.x 2021.x |
Resolved 2023.0 |
| Topic Monitoring | FME Flow | When stopping the topic monitoring there is a pop-up error message "There was an error connecting to monitoring service". FMESERVER-16202 |
The socket is being intentionally closed, but IE is reporting an error on closure. Despite the error shown everything still works as expected. Optionally ignore this error in IE or proceed using a different web browser such as Chrome, Firefox, Edge or Safari. |
2022.x 2021.x |
Workaround Other |
| FME Flow Apps | FME Flow | FME Server App won't save when an optional parameter does not have a default value (unhandled exception error) FMESERVER-18230 FMESERVER-19041 |
FME Server may let you save the parameter once or twice before the error occurs. Try recreating the parameter or providing a default value. |
2022.x 2021.2.6 2021.2.5 2021.2.4 2021.2.3 |
Resolved 2023.0 |
| FME Flow Installation | FME Flow | In a Fault-Tolerant installation when the Core with the 'Active Job Router' fails, the remaining engines do not connect with the second Core Job Router. They will appear available in the Web UI but will not detect jobs in the queue for processing. This issue resolves itself after two hours. FMESERVER-19159 |
In fmeEngineConfig.txt set the RECEIVE_TIMEOUT directive to 90000. Save the file and restart FME Server to apply the change. Setting this directive forces the Engine to terminate itself after it does not receive a translation request for the specified time, effectively breaking out of the hung state. |
2022.x 2021.2.5 |
Resolved 2023.0 |
| FME Workbench | FME Form | FME Workbench won’t start on MacOS FMEDESKTOP-10892 |
See Known Issue: FME Workbench Won’t Start on MacOS |
2022.x 2021.2 |
Resolved 2023.0 |
| Microsoft SQL Sever Non-Spatial Writer | FME Form | Microsoft SQL Server Non-Spatial (MSSQL_ADO): writing to an existing table with an attribute with type varbinary(max) or nvarchar(max) will result in the following warning: Microsoft SQL Server Non-Spatial Writer: Attribute `geometry_wkb' of feature type `dbo.osf_pois_polygon_NS' has specified type `nvarchar(max)', but existing database table field has type `nvarchar_max'. Information may be lost during conversion OR Microsoft SQL Server Non-Spatial Writer: Attribute `geometry_wkb' of feature type `dbo.osf_pois_polygon_NS' has specified type `varbinary(max)', but existing database table field has type `varbinary_max'. Information may be lost during conversion FMEENGINE-73455 |
Under the Writer parameters > Advanced > Set Bulk Inserts to "No" Use the Microsoft SQL Server Non-Spatial (JDBC) format |
2022.x |
Resolved 2023.0 |
| FME Flow Apps | FME Flow | When configuring an FME Server App, the Show In App checkbox is missing for all parameters that are within a group box. FMESERVER-18341 |
Move the File parameters outside of the group box. |
2022.x |
Resolved 2023.0 |
| User Parameters | FME Flow | When a reader has a source dataset published parameter that’s within a group box, the job will fail with an error such as “No CSV2 dataset name was specified (couldn't find a value for `CSV2_1_DATASET' or `CSV2_DATASET')”. This appears to occur regardless of the format. FMESERVER-18342 |
Move the File parameters outside of the group box. |
2022.x |
Resolved 2023.0 |
| Schedules | FME Flow | When creating a schedule, if a file parameter exists that has (1) “Items to Select” set to Geodatabase and (2) “Path Selection” set to Multiple Paths, the schedule will fail to be created and an error will be returned saying something like: “Unexpected value “[“\\\\mynetdir\\folder\\hello_world.gdb”]” for parameter “value,” expected scalar.” Automations and Server Apps are not affected. | Set the geodatabase source dataset parameter from Multiple Paths to Single Path in the Path Selection. Once this change is made in FME Form (Desktop), publish the workspace and test creating a schedule. |
2022.x |
Resolved 2023.0 |
| User Parameters | FME Flow | When running a workspace with a geometry parameter within a parameter group, the job fails with a JSON syntax error: Unexpected character: 't'. One of the following characters was expected: '"', '}' | Move the geometry parameter outside of the parameter group. |
2022.x |
Resolved 2023.0 |
| Schedules | FME Flow | Schedules repository selection and search is limited to first 100 repositories when creating or editing a schedule FMEFLOW-18574 |
Create schedules through REST API calls |
2022.x |
Resolved 2023.0 |
| Users and Roles | FME Flow | When trying to delete a user on a filtered list or very large list (where the list is spread out to multiple pages), the pop-up for selecting a user for transferring ownership of items is either empty or the complete list of users is not displaying. FMESERVER-19914 |
Use FME Server REST API call to remove the account from the FME Server instance. | 2022.2.x |
Resolved 2023.0 |
| Users and Roles | FME Flow | Deleting the “fmeauthor” role causes FME Server login page to load with no username or password prompt. Loading the login page returns the response “Specified SAML configuration does not exist” . When deleting the default fmeauthor role i.e. deleting the corresponding entry from fme_role table, it causes the child record in fme_samlconfig to be deleted as well, effectively removing the only entry in the table. “fmeauthor” role is the default role assigned to the pre-existing SAML record. FMEFLOW-19917 |
If upgrade is not possible, manually insert a new record in the “fme_samlconfig table” with values from another healthy FME server’s database [would be the same values]. Also, replace the deleted role “fmeauthor”. | 2022.2.x |
Resolved 2023.0 |
| Automations | FME Flow | Internal Server Error when looking at a job log that was run from an Automations, Automation Apps or a Streams that has been deleted. These endpoints are having issues: GET /fmeapiv4/jobs/<id> GET /fmeapiv4/jobs<id>/log FMESERVER-19869 |
You can access the job log via the FME Server System Share (File System) or download via the Web UI Files & Connections > Resources > Logs > engine > current|old > jobs |
2022.2.6 2022.2.5 2022.2.4 2022.2.3 |
Resolved 2023.0 |
| Oracle Database Connection | FME Flow | When connecting to an Oracle database with a connection that includes the string "G@" in the name, and using a tnsnames.ora file, FME Server tries to connect using the connection name instead of the server name from the tnsnames.ora file. | Do not use "G@" in the database connection name. |
2022.2.6 2022.2.5 2022.2.4 |
Resolved 2023.0 |
| ArcGIS Portal Service Web Connection | FME Form | When trying to create a web connection for ArcGIS Portal 11.1, the process fails with the error: Unable to retrieve access token FMEFORM-28714 |
To create an ArcGIS Portal 11.1 web connection, upgrade to at least FME 2022.2.7 b22801 or later. You must also define a new web service - ArcGIS Portal web services defined in prior versions of FME will not work. See Known Issue: FME fails to create a portal web connection to ArcGIS Enterprise 11.1 |
2023.0.0.1 2023.0.0.0 2022.2.6 |
Resolved 2023.0.1 2022.2.7 |
| Automations | FME Flow | Automation Keys no longer work when placed inside square or curly brackets. See the community post for more details. FMESERVER-19612 |
Remove brackets, do not place Automation Keys in brackets. |
2022.2.2 2022.2.1 2022.2.0 2022.1 2022.0 |
Resolved 2022.2.3 |
| ArcGIS Online Web Connections | FME Flow | ArcGIS Online Web Connections created from new ArcGIS Online Web Services do not work on FME Server. When trying to add the URI to the web service after publishing to FME Server, an error "Some of all of the input parameters are invalid" is displayed on the UI. This is due to URLs needed for oauth 2.0 that are missing on FME Server. FMEDESKTOP-13465 |
Upgrade to FME Server 2022.2.1 Upload AGOL webservice from FME Workbench 2020. |
2022.2.0 2022.1 2022.0 2021.2.6 |
Resolved 2022.2.1 |
| Automations FME Flow Apps |
FME Flow | When trying to set values for parameters within a parameter group box, the new values are not saved. This occurs in Automations and FME Server Apps. FMESERVER-19203 |
Set default parameter values in FME Workbench and publish to FME Server |
2022.2 2022.1.3 2022.1.2 2022.1.1 |
Resolved 2023.0 |
| Python | FME Form | If the workspace's Python Compatibility parameter is set to 'Esri ArcGIS Python 3.9', NTLM authentication for Python-based formats (eg. Microsoft SharePoint List, Esri ArcGIS Server Feature Service, Esri ArcGIS Portal Feature Service, OData) fails with the message: Python Exception <ValueError>: unsupported hash type md4 FMEENGINE-76915 |
Change the workspace's Python Compatibility parameter to any of the FME Python options. |
2022.2 2022.1 |
Resolved 2023.0 |
| User Parameters | FME Flow | What a choice parameter allows multiple selections, the values are not read as expected on FME Server. For example, [choice1, choice2] instead of choice1,choice2. FMEFLOW-19526 |
Move the parameter out of any parameter groups. |
2022.2 2022.1 |
Resolved 2023.0 |
| JSONValidator Transformer | FME Form | JSONValidator is rejecting \n FMEENGINE-74950 |
Update the JSON to \\n |
2022.1.3 2022.1.2 |
Resolved 2022.2 |
| User Parameters | FME Form | If a workspace was built in an older version of FME and opened in 2022.1, the initial bounds for map display values can be swapped in the Geometry Parameter. FMEDESKTOP-13160 |
Compare the values in the older version and 2022 to ensure they match. |
2022.1.2 2022.1.1 |
Resolved 2022.1.3 |
| FME Workbench | FME Form | FME Workbench crashes on startup - Qt6.Gui_fme.dll related error FMEDESKTOP-13325 |
See Known Issue: FME Workbench won't start because Qt6Gui_fme.dll crashes |
2022.1.2 |
Resolved 2022.1.3 |
| Microsoft Excel Writer | FME Form | Excel Writer performance is much slower in 2022.1 compared to previous versions of FME FMEENGINE-74327 |
No known workaround. |
2022.1.1 2022.1.0 |
Resolved 2022.1.2 |
| FME Workbench | FME Form | Error dialog pops-up on workbench startup that says "VCRUNTIME140D.dll is missing on your computer". The issue only occurs on Windows Server 2012. FMEENGINE-74482 |
No known workaround |
2022.1.1 |
Resolved 2022.1.2 |
| User Parameters | FME Flow | Geometry Parameter: 2022.1 is not backwards compatible with older versions FMESERVER-18903 |
Open the workspace in FME Desktop 2022.1 and publish it to FME Server. |
2022.1.1 |
Resolved 2022.1.2 |
| RCaller Transformer | FME Form | When using R 4.2 with FME the following error will occur. ERROR |RCaller (InlineQueryFactory): Failed with exit code 1 when executing R script. Output was: Loading required package: gsubfn Loading required package: proto Loading required package: RSQLite Error in if (fmeOutput != "") dbWriteTable(dbcon, "Output", fmeOutput, : the condition has length > 1 Execution halted 2022-05-20 23:28:11| 0.3| 0.0|ERROR |RCaller (InlineQueryFactory): Failed to execute scripted code. FMEENGINE-73477 |
Downgrade to R 4.1.3 or lower |
2022.1 2022.0 2021.x |
Resolved 2022.2 |
| Directory Watch | FME Flow | The Directory Watch trigger will pass an incorrect path when monitoring a network resource with a missing backslash "\" at the end of the UNC path. FMESERVER-17246 |
See Known Issue: Directory Watch truncates network resource paths |
2022.1 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.2 |
| FME Flow Apps | FME Flow | FME Server app doesn't allow uploading or browsing for a geodatabase resource folder when the file/URL parameter is configured as Geodatabase (only a textbox is shown) FMESERVER-18901 |
In FME Workbench, leave the file/URL parameter's "Items to Select" value as the default Files. Upload the geodatabase as a .zip file. |
2022.1 2022.0 2021.x |
Resolved 2022.2 |
| Schedules | FME Flow | If FME Server is hosted in a different time zone, when creating a Basic or CRON Schedule the start and end times are adjusted. For example, if my current Server time: Fri-02-Sep-2022 11:30:00 AM -0700 and I set my schedule to start at 2022-09-02 20:00. After saving the Schedule it becomes 2022-09-02 13:00. Note: In 2022.1+ this is only an issue for a Schedule created in an Automation, but in 2021.2.6 it occurs on the individual Schedules page as well. FMESERVER-18922 |
Build a Schedule using the 'Repeat on Interval' Schedule Type. |
2022.1 2022.0 2021.2.6 |
Resolved 2022.2 |
| Web Connections | FME Flow | Web Connections created from Web Services do not work on FME Server. When trying to add the URI to the web service after publishing to FME Server, an error is displayed on the UI. FMESERVER-19652 |
See Known Issue: Web Services on FME Server are Invalid |
2022.1 2022.0 2021.2.6 |
Resolved 2022.2 |
| FMEServerNotifier Transformer | FME Form FME Flow |
With the FMEServerNotifier, if you include \n in the JSON, the JSON will be Null on FME Server. This has been fixed by FMEENGINE-74950. Please upgrade to FME Server 2022.2 and create the workspace in 2022.2. FMESERVER-19220 |
Replace \n with <br> in a workspace before triggering the topic or use an HTTPCaller to push data to the topic. See /notifications/topics/< topic >/message in the API documentation. |
2022.1 2022.0 2021.2 2021.1.3 |
Resolved 2022.2 |
| FME Flow Apps | FME Flow | FME Server Apps do not show Azure AD groups. FMESERVER-18367 |
Add each user individually. |
2022.1 2022.0 2021.2 |
Resolved 2022.2 |
| Python | FME Form | Running Python in FME 2022.0 on Windows 10 and Windows Server 2019 version 1909 or older may cause a crash. FMEENGINE-71266 |
See Known Issue: Instability Running Python in FME 2022.0 on Windows 10 and Windows Server 2019 Version 1909 or Older |
2022.1 2022.0 |
Resolved 2022.2 |
| Oracle Reader | FME Form | Oracle 11g Database Incompatibility (Oracle Spatial Formats) Reader Message : (there may be some success reading if not using a spatial query): WARN |Execution of statement `SELECT table_name, column_name, d.dcount, SRID FROM USER_SDO_GEOM_METADATA OUTER APPLY(SELECT COUNT(*) AS dcount FROM TABLE(diminfo)) d' did not succeed; error was `ORA-00933: SQL command not properly ended'. OR if using Spatial Query may also see ORA-29902: error in executing ODCIIndexStart() routine ORA-13208: internal error while evaluating [window SRID does not match layer SRID] operator Writer Message WARN |Execution of statement `SELECT table_name, column_name, d.dcount, SRID FROM USER_SDO_GEOM_METADATA OUTER APPLY(SELECT COUNT(*) AS dcount FROM TABLE(diminfo)) d' did not succeed; error was `ORA-00933: SQL command not properly ended'. ERROR |Execution of statement `INSERT INTO "<table>" ( "<col1>", "<col2>", "<col3>", "<col4>", "GEOMETRY" ) VALUES ( :"<col1>", :"<col2>", :"<col3>", :"<col4>", :"GEOMETRY")' did not succeed; error was `ORA-29875: failed in the execution of the ODCIINDEXINSERT routine ORA-13365: layer SRID does not match geometry SRID ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 720 ORA-06512: at "MDSYS.SDO_INDEX_METHOD_10I", line 225'. FMEENGINE-75065 |
No Known workaround. |
2022.1 2022.0 |
Resolved 2022.2 |
| User Parameters | FME Flow | When an input File parameter is within a group box, files can't be uploaded. FMESERVER-18340 |
Move the File parameters outside of the group box. |
2022.1 2022.0 |
Resolved 2022.2 |
| French FME Flow | FME Flow | FME Server French System Locale failing to start on Windows Server after fresh install. DEVOPS-2470 |
See Known Issue: FME Server 2022.0 French System Locale failing to start on Windows Server |
2022.1 2022.0 |
Resolved 2022.2 |
| Backup and Restore | FME Flow | Web connections are not present after the restore process during the upgrade. FMESERVER-19601 |
See FME Server Upgrade Can Fail to Restore Web Connections if Web Service Are Broken |
2022.1 2022.0 |
Resolved 2022.2 |
| User Parameters | FME Flow | When running a workspace with an updated text file parameter that was uploaded as a temporary file, the job will not use the updated file. The old file is used and a org.apache.commons.io.FileExistsException is logged in the Catalina log. | Use a different type of file (for example, csv) or rename the text file prior to uploading it |
2022.1 2022.0 |
Resolved 2022.2 |
| Microsoft Excel Reader/Writer | FME Form | FME Workbench will crash while trying to access the parameter window in the Excel Reader/Writer after reading or importing from a XLSM dataset. FMEENGINE-75304 |
Add Readers/Writers to the canvas without opening the parameters. |
2022.1 |
Resolved 2022.2 |
| FME Flow Web UI | FME Flow | When logging into FME Server, the request does not correctly validate the referrer value, which may result in an unwanted redirection. FMESERVER-18288 |
See Known Issue: FME Server missing validation which may result in an unwanted redirect upon login |
2022.0.1.0 2022.0 2021.x |
Resolved 2022.0.1.1 2021.2.6 |
| Security | FME Flow | A security scan has reported vulnerabilities on FME Server with two stored Cross-Site Scripting (XSS). See article for CVEs. FMESERVER-14600 FMESERVER-18292 |
See Known Issue: FME Server Unauthenticated and Authenticated Stored Cross-Site Scripting (XSS) Vulnerabilities |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.1.1 2021.2.6 |
| Repositories | FME Flow | A user who has been granted access permissions on Repositories as well as Read and Publish permissions on any Repository is able to carry out an XML external entity (XXE) injection attack. FMESERVER-18289 |
See Known Issue: FME Server XXE vulnerability via adding a repository item |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.2 2021.2.6 |
| Automations | FME Flow | When running a workspace in an Automation that writes a file to a resource folder, if the resource path contains spaces, the file will fail to write since the path gets cut off. The job will succeed but the file will be written to the wrong location. FMESERVER-18366 |
Add one set of double quotes around the path per space. For example, ""$(FME_SHAREDRESOURCE_DATA)/My Output Data/"". Alternatively, write to a resource path that doesn’t have spaces. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1 |
| User Parameters | FME Form FME Flow |
Workspaces that use a File Published Parameter may fail when published to FME Server if the file parameter was created within the transformer and it is referencing an FME Server parameter. The error in the log will say something like “File cannot be found”. FMESERVER-18414 |
See Known Issue: FME Server Job Failure when Published Parameters reference FME Server Parameters |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| File Upload | FME Flow | FME Server is failing to use files uploaded by the temporary upload if they have a space in the file name. FMESERVER-18434 |
Either remove the space in the file name or switch the File Parameter to use Multiple Paths in FME Desktop and reupload the workspace on FME Server. This setting is found in the Parameter Configuration under File/ URL configuration > File Configuration > Path Selection. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| SAML | FME Flow | In the FME Server Web UI when SAML Configuration is enable the URLs listed under the SAML Identity Provider Settings are incorrect. FMESERVER-18418 |
Remove /fmeserver from the URLs when copying them over to your SAML provider. |
2022.0.0.x 2022.0 |
Resolved 2022.0.1.1 |
| ArcGIS Online | FME Flow Hosted | ArcGIS Online Workspaces running on FME Cloud will fail with the error "simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)" FMEENGINE-73399 |
No known workaround. |
2022.0.0.1 2022.0.0.0 |
Resolved 2022.0.0.2 |
| Automations | FME Flow | Building an Automation with an internal action (orange node) if I try and reference an event key from an upstream trigger/action the Automation cannot be saved. FMESERVER-18328 |
See Known Issue: Unable to save an Automation when referencing output keys in downstream action |
2022.0.0.1 |
Resolved 2022.0.0.2 |
| Automations | FME Flow | When creating an Automation, with a workspace that contains a password parameter. Once you save it, an error pops up that says "javax.crypto.IllegalBlockSizeException" FMESERVER-18267 |
If you create the automation again and reenter the password in the workspace parameter it will save. |
2022.0.0.0 |
Resolved 2022.0.0.1 |
| ArcGIS Online | FME Form | ArcGIS Online Workspaces running on a Ubuntu machine will fail with the error "simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)" FMEENGINE-73399 |
No known workaround. |
2022.0.0.0 |
Resolved 2022.0.0.1 |
| FME Form | FME Form | Non-ASCII path handling causes FME Desktop applications to crash on startup. Possible paths that could have non-ASCII characters that could cause a crash are: User App Data folder FME Resource folders FME temporary folder Windows font folder FMEENGINE-73388 |
Remove non-ASCII characters from paths or upgrade to FME 2022.0 build 22343 or newer |
2022.0.0.0 |
Resolved 2022.0.0.1 |
| RealDWG | FME Form | The loaded plugin's FMEPluginCapabilities 'realdwg/REALDWG' has changed the process locale to 'English_Canada.1252' which is incompatible with FME 'English_Canada.utf8' locale. FMEENGINE-73329 |
No known workaround. |
2022.0.0 |
Resolved 2022.0.1 |
| ArcGIS Online Web Connections | FME Flow | After publishing a workspace with an ArcGIS Online Web Connection to FME Server and then running it, the translation fails due to an authentication error from ArcGIS Online, for example 499 Token Required. | See Known Issue: Unable to Authenticate to ArcGIS Online on FME Server |
2022.x |
Workaround |
| FME Flow Web Connection | FME Flow | An FME Server transformer is failing with the error "Reason - credentials for user '<username>' are invalid". FMESERVER-18350 |
See Known Issue: FME Server Web Connection fails with Reason - credentials for user are invalid |
2022.0 2021.x |
Resolved 2022.1 |
| FME Flow Apps | FME Flow | In an FME Server App, you cannot click OK to run the App. FMESERVER-16186 |
This is likely because the workspace app contains a parameter that is required but is not visible and has no default value. Either set a default value or make the parameter visible. In the fixed versions of FME Server, users will be prompted to select a value for the parameter. |
2022.0 2021.x |
Resolved 2022.1 |
| File Upload | FME Flow | An administrator user can write files to any location on the server drive hosting the FMEServer, which could result in unintended or malicious file uploads. FMESERVER-18293 |
See Known Issue: FME Server vulnerability with arbitrary path traversal and file upload |
2022.0.1.0 2022.0 2021.x 2020.x 2019.x |
Resolved 2022.0.1 2021.2.6 |
| FME Flow Apps | FME Flow | A server app (workspace or gallery) has ‘Require Authentication’ enabled and the allowed user is a user imported from Azure AD. When this user navigates to the app URL they are prompted to log in. After selecting ‘Sign in with Microsoft’ they are redirected to the FME Server home page instead of the app. FMESERVER-17846 |
First, log into FME Server and then go to the server app URL. |
2022.0 2021.2 |
Resolved 2022.1 |
| Automations | FME Flow | In an Automation you configure a Schedule with a set End Time, then start the Automation. Once the End Time passes you cannot stop the Automation. The error is: Unable to disable '<AUTOMATIONNAME>': Schedule task (Category: <UUID> Name: <UUID>) must have an end time greater than the scheduler current time. FMESERVER-17998 |
Duplicate the Automation (this will copy it in a disabled state where it can now be edited) and then delete the original Automation. To duplicate the Automation go to 'Manage Automations'. Check the box next to the problem Automation and then select Actions > Duplicate. |
2022.0 2021.2 |
Resolved 2022.1 |
| Python | FME Form | Executing Python scripts that change locale will result in unexpected errors in FME
2022.0 FMEENGINE-72009 |
See Known Issue: Executing Python scripts that change locale will result in unexpected errors in FME 2022.0 |
2022.0 |
Resolved 2022.1 |
| Web Connections | FME Flow | Error message when trying to connect from Form to Flow through a Flow web connection: "Register client failed (Not Authorized) - Ensure that credentials are correct, and that user has sufficient privileges." FMEFLOW-24425 |
In FME Flow go to User Management > User/Roles. Grant Access permission for Deployment Parameters. |
2025.0 2024.2.3 2024.2.2 2024.2.1 |
Unresolved |
| FME Flow Installation | FME Flow | The FME Flow installer hangs and will not complete DEVOPS-4045 DEVOPS-3945 |
See Known Issue: PowerShell Execution Policy Prevents Installation of FME Flow |
2024.0 2023.x 2022.2 |
Resolved 2024.1 |
| Backup and Restore | FME Flow | System restore fails with key constraint error related to users, roles, or tenants, for example: "fme_useraccount_assigned_role_pkey" or "fme_azure_ad_user_tenant_id_id_key" FMEFLOW-24891 |
If you have configured a Windows or Azure AD authentication service before doing a system restore, disable synchronization and reattempt the restore If you are doing an upgrade and still have access to the old FME Flow instance, disable synchronization on the authentication service and then create a new backup. Reattampt the restore. If the restore continues to fail, please submit a ticket and include your fsconfig (backup file), if possible |
2024.2 |
Resolved 2025.0 |
| Remote Engines | FME Flow | When a connected remote engine host is rebooted, the remote engine connection on the core host continues to show “Not ready” or “Offline” even after the remote engine host comes back online. The jobs remain queued on the Flow host. FMEFLOW-23273 |
Deleting the current remote engine connection on the core host and recreating the same connection solves the issue. |
2024.0 |
Resolved 2024.1 |
| Active Directory | FME Flow | When configuring an Active Directory connection and selecting the SASL mechanism = GSS-SPNEGO , the user is not able to access the 'Authentication Services' web page. A message pops up stating “Internal Server error” [HAR log says 500 Internal error] and the screen stays greyed out with the “thinking” wheel. The fmedirectoryserver.log mentions error "Unsupported SASL mechanism 'GSS-SPNEGO'". FMEFLOW-22604 |
Please contact us for further assistance. |
2023.2 |
Resolved 2024.0 |
| Databricks Connection | FME Flow | When importing a project or restoring a backup that contains a Databricks connection created in FME 2023.1, the connection is not restored. There is no indication of that the Databricks connection has been skipped in the migration log. Note: this bug only affects FME Flow 2023.1 instances that have not previously had a Databricks connection published. FMEFLOW-21339 |
Publish a new Databricks connection to the FME Flow instance prior to importing a package or restoring a backup that contains Databricks connections. Or, manually recreate the Databricks connection. |
2023.1 |
Resolved 2023.2 |
| Users and Roles | FME Flow | Can no longer use the Guest account to provide unauthenticated web service access. FMEFLOW-18196 |
Please see FME Deprecations. Provide a token to run workspaces without providing user credentials. |
2023.0 |
Deprecated 2023.0 |
| FME Flow Apps | FME Flow | Automation Apps file parameter does not allow the end-user to access FME Server Resources folder due to lack of permissions on the app token. FMESERVER-19084 FMESERVER-19197 |
Grant the app token permissions to Access and List to Resources’ subfolders of choice. For example, the Data folder, a Network directory, etc |
2022.2 |
Resolved 2023.0 |
| WFS Reader | FME Form | Specifying a search envelope for the WFS Reader will cause translation failure in FME 2022.1. The following error will occur: Unknown coordinate system ' ' specified - aborting FMEENGINE-74427 |
Use a Creator transformer to create a bounding box polygon, and then use this bounding box as a spatial filter with the FeatureReader. Set the Spatial Filter parameter of the FeatureReader to Bounding Box OGC-Intersect. |
2022.1 |
Resolved 2022.2 |
| FMEFlowJobSubmitter Transformer | FME Form | FMEServerJobSubmitter (version 4) is submitting jobs incorrectly to FME Server, if the child job has a text parameter and the FMEServerJobSubmitter is using an attribute value to submit it. FMEDESKTOP-13280 |
Keep the FMEServerJobSubmitter on version 3 and don't modify it in 2022.1. |
2022.1 |
Resolved 2022.2 |
| Microsoft Excel Writer | FME Form | Writing Excel files with a template file selected outputs a corrupt Excel file. Opening the Excel file in Microsoft Excel causes a recovery error to appear. FMEENGINE-74240 |
No known workaround. |
2022.1 |
Resolved 2022.2 |
| Schedules | FME Flow | Schedules: The create category button is missing when building a schedule. FMESERVER-18947 |
To create a category, manually type the value into the field. Note this will only temporarily add the category for that particular schedule. Alternatively, click the down button on the right side of the dropdown menu and select an existing category. |
2022.1 |
Resolved 2022.2 |
| FME Workbench | FME Form | FME Workbench sometimes crashes when double-clicking the source file path in the navigator on macOS FMEDESKTOP-12415 |
No known workaround |
2022.0 |
Resolved 2022.1 |
| Python | FME Flow | A workspace that requires a custom python module may fail " Python Exception <ModuleNotFoundError>: No module named ' '" error, even though the module was uploaded to the Python folders on FME Server. DEVOPS-2156 |
Go to Resources > Engine > Plugins > Python. Create a python39 folder. Then, upload the module to that folder. |
2022.0 |
Resolved 2022.1 |
| Data Streaming | FME Flow | When sending a POST with a significant amount of content to the data streaming service, you receive a blank response and see that the parameter input is empty ""{}"" in the ""Request Data"" section of the job log on FME Flow. FMEFLOW-21390 |
See Known Issue: Data Streaming cannot submit a POST body larger than 2 MB |
2025.x 2024.x 2023.x 2022.x |
Workaround |
| User Parameters | FME Flow | No results are returned when attempting to search for a value in the Choice (Dropdown) parameter type. FMESERVER-18386 |
Change the Choice configuration in FME Desktop from Drop Down to List and set Allow Multiple Selection: No. Note, with this configuration the display cannot be different from the value. |
2022.0 |
Resolved 2022.1 |
| Workspaces | FME Form | When a workspace authored in FME Desktop pre-2021.0 is opened and saved in FME Workbench 2021.0 or newer, users may experience failed translations with the following translation log error messages: “The dataset ‘C:\Path\To\Dataset’ could not be located. Please check that it exists.” “<FormatName>: The encoded string is not a valid UTF-8 string: ‘\x83g\x83\x8A\x83A’” FMEENGINE-73094 |
See Known Issue: Older Workspaces Opened and Saved in FME 2021.0 or Newer May No Longer Run Due to Workspace Character Encoding Conflicts |
2025.x 2024.x 2023.x 2022.x 2021.x |
Workaround |
| Packages | FME Flow | FME Flow fails to extract the package into Resources > Engine > Packages after running a workspace that contains a linked custom transformer with an FME Package. You may find this error in your job log: Python Exception <ModuleNotFoundError>. FMESERVER-17744 |
See Known Issue: FME Flow Packages and Linked Custom Transformer |
2025.x 2024.x 2023.x 2022.x 2021.x |
Workaround |
| Text File Writer |
FME Form FME Flow |
When changing the MIME type on the Text File Writer, the changes are not when the workspace is published to FME Server FMESERVER-19489 |
Delete and re-add the Text File Writer to canvas and set the desired MIME type. Then save your workspace and publish to FME Server for the change to be included. See Known Issue: MIME type on Text File writer cannot be updated once writer is added to workspace |
2025.x 2024.x 2023.x 2022.x 2021.x |
Workaround |
| Backup and Restore | FME Flow | When attempting to run the backupConfiguration.fmw utility workspace, the workspace fails and the job log shows an HTTP 404 error. The error occurs both when trying to run the backup workspace manually or on a schedule. FMESERVER-16502 |
See Known Issue: Backup workspace fails with an HTTP 404 error |
2025.x 2024.x 2023.x 2022.x 2021.x 2020.x |
Workaround |
| Engines | FME Flow | FME Flow Starts Two Engines by Default FMEFLOW-13819 |
See Known Issue: FME Flow Starts Two Engines by Default |
2024.1 2024.0 2023.x 2022.x 2021.x 2020.x |
Resolved 2024.2 |
| Engines | FME Flow | The Engines are missing from the FME Flow (formerly Server) Web UI. In the fmeserver.log there are errors similar to: ERROR RequestHandler-Thread 402902 : Failed to connect to Job Queue. Please ensure Job Queue is started. ERROR RequestHandler-Thread Could not get a resource from the pool FMEFLOW-15761 |
See Known Issue: FME Flow Engines Missing Failed to Connect to Job Queue |
2025.x 2024.x 2023.x 2022.x 2021.x 2020.x |
Unplanned |
| FME Flow web connection | FME Flow FME Form |
FME Flow web connection doesn't work when connecting from FME Form. Users may experience failed translations with the following translation log in FME Form error messages: or Unable to retrieve public key From Flow. Unable to establish secure communication with Flow. Deployment parameter access failed (Connection Error) - Unable to connect to FME Flow
|
Restart FME Form |
2025.x |
Workaround |
Comments
0 comments
Please sign in to leave a comment.